Bug#938013: marked as done (python-peak.rules: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:18:43 +
with message-id 
and subject line Bug#948162: Removed package(s) from unstable
has caused the Debian Bug report #938013,
regarding python-peak.rules: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-peak.rules

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.5a1+r2713-1+rm

Dear submitter,

as the package python-peak.rules 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/948162

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:17:38 +
with message-id 
and subject line Bug#948162: Removed package(s) from unstable
has caused the Debian Bug report #938727,
regarding turbojson: 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.)


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

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  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:turbojson

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.3.2-2.1+rm

Dear submitter,

as the package turbojson 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/948162

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#948162: marked as done (RM: python-peak.util -- RoQA; python2-only; combination of modules most of which deprecated, no py3k available)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:17:35 +
with message-id 
and subject line Bug#948162: Removed package(s) from unstable
has caused the Debian Bug report #948162,
regarding RM: python-peak.util -- RoQA; python2-only; combination of modules 
most of which deprecated, no py3k available
to be marked as done.

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

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


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

Hello,
this package recently became a leaf pkg and it's currently python2-only; looking
at how it's made of, it appears it's a combination of modules:


Module Current  Latest py3k
   Version  Available  available?

addons 0.7  0.7some py3k support
bytecodeassembler  0.6  0.6.1  no
extremes   1.1.11.1.1  yes
proxies0.9  0.10.0 yes
symboltype 1.0  1.0yes

What are the plans for this package? they mostly leave at the new upstream
location on github https://github.com/PEAK-Legacy which says "Projects from the
Python Enterprise Application Kit that are not actively in development, or have
been discontinued. Most are Python 2-only."

Should we just go ahead and remove this package, since there are no more Debian
packages depending on it?

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

Versions of packages python-peak.util depends on:
ii  python   2.7.16-1
pn  python-peak.util.decorators  

python-peak.util recommends no packages.

python-peak.util suggests no packages.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

python-turbojson |  1.3.2-2.1 | all
 turbojson |  1.3.2-2.1 | source

--- Reason ---
RoQA; python2-only; needs python-peak.rules, which is being removed, no py3k 
available
--

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

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

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

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:06:43 +
with message-id 
and subject line Bug#948068: Removed package(s) from unstable
has caused the Debian Bug report #938712,
regarding trac-wikiprint: 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.)


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

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

Dear submitter,

as the package trac-wikiprint 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/948068

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:07:44 +
with message-id 
and subject line Bug#948070: Removed package(s) from unstable
has caused the Debian Bug report #938714,
regarding trac-wysiwyg: 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.)


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

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

Dear submitter,

as the package trac-wysiwyg 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/948070

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:07:09 +
with message-id 
and subject line Bug#948069: Removed package(s) from unstable
has caused the Debian Bug report #938713,
regarding trac-wikitablemacro: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:trac-wikitablemacro

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:0.3-1+rm

Dear submitter,

as the package trac-wikitablemacro 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/948069

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:03:56 +
with message-id 
and subject line Bug#948062: Removed package(s) from unstable
has caused the Debian Bug report #938701,
regarding trac-odtexport: 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.)


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

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.0+svn10787-2+rm

Dear submitter,

as the package trac-odtexport 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/948062

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#866487: marked as done (trac-odtexport: depends on obsolete python-imaging (replace with python3-pil or python-pil))

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:03:56 +
with message-id 
and subject line Bug#948062: Removed package(s) from unstable
has caused the Debian Bug report #866487,
regarding trac-odtexport: depends on obsolete python-imaging (replace with 
python3-pil or python-pil)
to be marked as done.

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

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


-- 
866487: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=866487
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trac-odtexport
Version: 0.6.0+svn10787-2
Severity: important
Tags: sid buster
User: d...@debian.org
Usertags: imaging-pillow

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

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

Dear submitter,

as the package trac-odtexport 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/948062

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:06:20 +
with message-id 
and subject line Bug#948067: Removed package(s) from unstable
has caused the Debian Bug report #938711,
regarding trac-virtualticketpermissions: 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.)


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

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

Dear submitter,

as the package trac-virtualticketpermissions 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/948067

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:05:20 +
with message-id 
and subject line Bug#948065: Removed package(s) from unstable
has caused the Debian Bug report #938707,
regarding trac-subcomponents: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:trac-subcomponents

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

Dear submitter,

as the package trac-subcomponents 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/948065

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:04:46 +
with message-id 
and subject line Bug#948064: Removed package(s) from unstable
has caused the Debian Bug report #938705,
regarding trac-sensitivetickets: 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.)


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

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

Dear submitter,

as the package trac-sensitivetickets 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/948064

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:05:48 +
with message-id 
and subject line Bug#948066: Removed package(s) from unstable
has caused the Debian Bug report #938710,
regarding trac-translatedpages: 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.)


-- 
938710: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938710
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trac-translatedpages
Version: 1.0~svn11919-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:trac-translatedpages

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.0~svn11919-2+rm

Dear submitter,

as the package trac-translatedpages 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/948066

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#889277: marked as done (trac-privatetickets is empty)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:04:21 +
with message-id 
and subject line Bug#948063: Removed package(s) from unstable
has caused the Debian Bug report #889277,
regarding trac-privatetickets is empty
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.)


-- 
889277: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889277
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trac-privatetickets
Version: 2.0.3-3.1
Severity: grave

$ dpkg -L trac-privatetickets
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/trac-privatetickets
/usr/share/doc/trac-privatetickets/changelog.Debian.gz
/usr/share/doc/trac-privatetickets/README
/usr/share/doc/trac-privatetickets/buildinfo_all.gz
/usr/share/doc/trac-privatetickets/copyright
/usr/share/doc/trac-privatetickets/README.Debian
$
--- End Message ---
--- Begin Message ---
Version: 2.0.3-3.1+rm

Dear submitter,

as the package trac-privateticketsplugin 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/948063

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:03:31 +
with message-id 
and subject line Bug#948061: Removed package(s) from unstable
has caused the Debian Bug report #938698,
regarding trac-mastertickets: 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.)


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

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  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:trac-mastertickets

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

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

Dear submitter,

as the package trac-mastertickets 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/948061

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:00:52 +
with message-id 
and subject line Bug#948055: Removed package(s) from unstable
has caused the Debian Bug report #938715,
regarding trac-xmlrpc: 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.)


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

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

Dear submitter,

as the package trac-xmlrpc 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/948055

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:00:06 +
with message-id 
and subject line Bug#948053: Removed package(s) from unstable
has caused the Debian Bug report #938709,
regarding trac-tags: 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.)


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

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

Dear submitter,

as the package trac-tags 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/948053

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:00:31 +
with message-id 
and subject line Bug#948054: Removed package(s) from unstable
has caused the Debian Bug report #938708,
regarding trac-subtickets: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:trac-subtickets

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

Dear submitter,

as the package trac-subtickets 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/948054

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:01:38 +
with message-id 
and subject line Bug#948057: Removed package(s) from unstable
has caused the Debian Bug report #938703,
regarding trac-privatewiki: 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.)


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

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

Dear submitter,

as the package trac-privatewiki 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/948057

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:01:16 +
with message-id 
and subject line Bug#948056: Removed package(s) from unstable
has caused the Debian Bug report #938704,
regarding trac-roadmap: 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.)


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

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

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

Dear submitter,

as the package trac-roadmap 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/948056

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:01:59 +
with message-id 
and subject line Bug#948058: Removed package(s) from unstable
has caused the Debian Bug report #938700,
regarding trac-navadd: 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.)


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

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

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

Dear submitter,

as the package trac-navadd 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/948058

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:03:00 +
with message-id 
and subject line Bug#948060: Removed package(s) from unstable
has caused the Debian Bug report #938697,
regarding trac-jsgantt: 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.)


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

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

Dear submitter,

as the package trac-jsgantt 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/948060

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:02:30 +
with message-id 
and subject line Bug#948059: Removed package(s) from unstable
has caused the Debian Bug report #938699,
regarding trac-mercurial: 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.)


-- 
938699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938699
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trac-mercurial
Version: 1.0.0.3+hg8df754d9b36a-1.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:trac-mercurial

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

Dear submitter,

as the package trac-mercurial 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/948059

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#787722: marked as done (trac-mercurial: Upstream Defect #11696 applies to Jessie, too)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 06:02:30 +
with message-id 
and subject line Bug#948059: Removed package(s) from unstable
has caused the Debian Bug report #787722,
regarding trac-mercurial: Upstream Defect #11696 applies to Jessie, too
to be marked as done.

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

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


-- 
787722: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787722
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trac-mercurial
Version: 1.0.0.3+hg8df754d9b36a-1.1
Severity: grave
Tags: upstream patch
Justification: renders package unusable

Dear Maintainer,

Jessie's trac-mercurial has this bug, which is upstream, and there is a
three line patch to fix it. You find everything (including the patch)
here:

http://trac.edgewall.org/ticket/11696

I tested the fixing patch, and it solves the problem.

Yours,
VB.

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

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

Versions of packages trac-mercurial depends on:
ii  mercurial  3.1.2-2+deb8u1
ii  python 2.7.9-1
ii  trac   1.0.2+dfsg-2

trac-mercurial recommends no packages.

trac-mercurial suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.0.0.3+hg8df754d9b36a-1.1+rm

Dear submitter,

as the package trac-mercurial 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/948059

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:57:51 +
with message-id 
and subject line Bug#948046: Removed package(s) from unstable
has caused the Debian Bug report #938695,
regarding trac-icalview: 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.)


-- 
938695: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938695
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trac-icalview
Version: 1:0.4+r7253-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:trac-icalview

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:0.4+r7253-1+rm

Dear submitter,

as the package trac-icalview 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/948046

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:57:09 +
with message-id 
and subject line Bug#948044: Removed package(s) from unstable
has caused the Debian Bug report #938694,
regarding trac-httpauth: 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.)


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

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

Your package either build-depends, depends on Python2, or uses Python2
in the autopkg tests.  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:trac-httpauth

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

Dear submitter,

as the package trac-httpauth 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/948044

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:58:55 +
with message-id 
and subject line Bug#948049: Removed package(s) from unstable
has caused the Debian Bug report #938688,
regarding trac-customfieldadmin: 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.)


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

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

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

Dear submitter,

as the package trac-customfieldadmin 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/948049

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:58:34 +
with message-id 
and subject line Bug#948048: Removed package(s) from unstable
has caused the Debian Bug report #938690,
regarding trac-diavisview: 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.)


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

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

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

Dear submitter,

as the package trac-diavisview 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/948048

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:58:13 +
with message-id 
and subject line Bug#948047: Removed package(s) from unstable
has caused the Debian Bug report #938689,
regarding trac-datefield: 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.)


-- 
938689: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938689
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trac-datefield
Version: 1:3.0.0+r16195-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:trac-datefield

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:3.0.0+r16195-1+rm

Dear submitter,

as the package trac-datefield 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/948047

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:59:43 +
with message-id 
and subject line Bug#948051: Removed package(s) from unstable
has caused the Debian Bug report #938683,
regarding trac-accountmanager: 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.)


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

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

Dear submitter,

as the package trac-accountmanager 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/948051

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:57:30 +
with message-id 
and subject line Bug#948045: Removed package(s) from unstable
has caused the Debian Bug report #938696,
regarding trac-includemacro: 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.)


-- 
938696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=938696
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:trac-includemacro
Version: 3.0.0~r12030-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:trac-includemacro

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

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

Dear submitter,

as the package trac-includemacro 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/948045

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:59:16 +
with message-id 
and subject line Bug#948050: Removed package(s) from unstable
has caused the Debian Bug report #938684,
regarding trac-announcer: 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.)


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

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

Dear submitter,

as the package trac-announcer 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/948050

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:56:17 +
with message-id 
and subject line Bug#948042: Removed package(s) from unstable
has caused the Debian Bug report #938685,
regarding trac-authopenid: 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.)


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

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

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

Dear submitter,

as the package trac-authopenid 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/948042

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:56:40 +
with message-id 
and subject line Bug#948043: Removed package(s) from unstable
has caused the Debian Bug report #938693,
regarding trac-graphviz: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:trac-graphviz

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

Dear submitter,

as the package trac-graphviz 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/948043

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#895282: marked as done (trac-authopenid: fails to work with trac 1.2 (get_db_cnx does not work))

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:56:17 +
with message-id 
and subject line Bug#948042: Removed package(s) from unstable
has caused the Debian Bug report #895282,
regarding trac-authopenid: fails to work with trac 1.2 (get_db_cnx does not 
work)
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.)


-- 
895282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: trac-authopenid
Version: 0.4.7-1
Severity: grave
Tags: patch
Justification: renders package unusable

on debian stretch and later, trac is version 1.2.  but trac-authopenid
0.4.7-1 uses get_db_cnx(), which was deprecated in trac 0.12 and
removed in trac 1.1.

As a result, if trac-authopenid is installed and configured for a trac
environment, that environment will fail to load at all.

see https://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1#DatabaseAPIChanges

the attached patch appears to fix the worst errors, but hasn't been
well-tested.

--dkg


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

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

Versions of packages trac-authopenid depends on:
ii  python 2.7.14-4
ii  python-openid  2.2.5-6
ii  trac   1.2.2+dfsg-1

trac-authopenid recommends no packages.

trac-authopenid suggests no packages.

-- no debconf information
From: Daniel Kahn Gillmor 
Date: Mon, 9 Apr 2018 07:30:15 -0400
Subject: move from get_db_cnx() to context manager

See
https://trac.edgewall.org/wiki/TracDev/ApiChanges/1.1#DatabaseAPIChanges
for more details about this migration.
---
 authopenid/authopenid.py | 660 +++
 1 file changed, 330 insertions(+), 330 deletions(-)

diff --git a/authopenid/authopenid.py b/authopenid/authopenid.py
index da98b19..112c175 100644
--- a/authopenid/authopenid.py
+++ b/authopenid/authopenid.py
@@ -227,7 +227,6 @@ class AuthOpenIdPlugin(Component):
 return generated_list
 
 def __init__(self):
-db = self.env.get_db_cnx()
 oidutil.log = OpenIdLogger(self.env)
 self.env.log.debug("Compiling white-list")
 self.re_white_list = self.generate_re_list(self.white_list)
@@ -264,9 +263,9 @@ class AuthOpenIdPlugin(Component):
 # IEnvironmentSetupParticipant methods
 
 def environment_created(self):
-db = self.env.get_db_cnx()
-self._initStore(db)
-db.commit()
+with self.env.db_transaction as db:
+self._initStore(db)
+db.commit()
 
 def environment_needs_upgrade(self, db):
 c = db.cursor()
@@ -414,36 +413,18 @@ class AuthOpenIdPlugin(Component):
 
 immediate = 'immediate' in req.args
 
-db = self.env.get_db_cnx()
-oidconsumer, oidsession = self._get_consumer(req, db)
-try:
-self.env.log.debug('beginning OpenID authentication.')
-request = oidconsumer.begin(openid_url)
-except consumer.DiscoveryFailure, exc:
-fetch_error_string = 'Error in discovery: %s' % (
-cgi.escape(str(exc[0])))
-return 'openidlogin.html', {
-'images': req.href.chrome('authopenid/images') + '/',
-'action': req.href.openidverify(),
-'message': fetch_error_string,
-'signup': self.signup_link,
-'whatis': self.whatis_link,
-'css_class': 'error',
-'providers_regexp': self.providers_regexp,
-'custom_provider_name': self.custom_provider_name,
-'custom_provider_label': self.custom_provider_label,
-'custom_provider_url': self.custom_provider_url,
-'custom_provider_image': self.custom_provider_image,
-'custom_provider_size': self.custom_provider_size,
-}, None
-else:
-if request is None:
-msg = 'No OpenID services found for %s' % (
-cgi.escape(openid_url),)
+with self.env.db_transaction as db:
+oidconsumer, oidsession = self._get_consumer(req, db)
+try:
+

Bug#855494: marked as done (mgltools-pmv: runPmv script does not work: ImportError: No module named oldnumeric)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:51:40 +
with message-id 
and subject line Bug#855701: Removed package(s) from unstable
has caused the Debian Bug report #855494,
regarding mgltools-pmv: runPmv script does not work: ImportError: No module 
named oldnumeric
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.)


-- 
855494: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855494
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mgltools-pmv
Version: 1.5.7-1
Severity: grave
Justification: renders package unusable

Hi,

I intended to reproduce #855485 but I was running into a different
problem:

$ runPmv
Run PMV from  /usr/lib/python2.7/dist-packages/Pmv
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/Pmv/__init__.py", line 378, in runPmv
from Pmv.moleculeViewer import MoleculeViewer
  File "/usr/lib/python2.7/dist-packages/Pmv/moleculeViewer.py", line 16, in 

from MolKit.molecule import Atom, AtomSet, BondSet, Molecule , MoleculeSet
  File "/usr/lib/python2.7/dist-packages/MolKit/molecule.py", line 26, in 

from numpy.oldnumeric import sum, array, less_equal, take, nonzero, argsort
ImportError: No module named oldnumeric
hit enter to continue

Some kind of splash screen was starting but than the program stopped.

Kind regards

  Andreas.

-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (501, 'testing'), (50, 'buildd-unstable'), (50, 'unstable'), (5, 
'experimental')
Architecture: amd64 (x86_64)

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

Versions of packages mgltools-pmv depends on:
ii  mgltools-dejavu   1.5.7-1
ii  mgltools-geomutils1.5.7-1
ii  mgltools-mglutil  1.5.7-2
ii  mgltools-molkit   1.5.7~rc1+cvs.20140424-1
ii  mgltools-opengltk 1.5.7-1
ii  mgltools-scenario21.5.7-1
ii  mgltools-support  1.5.7-1
ii  mgltools-utpackages   1.5.7-1
ii  mgltools-viewerframework  1.5.7-1
ii  python-pil.imagetk4.0.0-4
ii  python-zsi2.1~a1-4
pn  python:any

Versions of packages mgltools-pmv recommends:
ii  apbs   1.4-1
ii  autodocktools  1.5.7-1

Versions of packages mgltools-pmv suggests:
pn  mgltools-pmv-test  
pn  mgltools-qslimlib  

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.5.7-3+rm

Dear submitter,

as the package mgltools-pmv 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/855701

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:52:57 +
with message-id 
and subject line Bug#943872: Removed package(s) from unstable
has caused the Debian Bug report #936543,
regarding fontypython: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:fontypython

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

Dear submitter,

as the package fontypython 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/943872

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#855485: marked as done (mgltools-pmv: runPmv script does not work: TclError: cannot use geometry manager grid)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:51:40 +
with message-id 
and subject line Bug#855701: Removed package(s) from unstable
has caused the Debian Bug report #855485,
regarding mgltools-pmv: runPmv script does not work: TclError: cannot use 
geometry manager grid
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.)


-- 
855485: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855485
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: mgltools-pmv
Version: 1.5.7~rc1+cvs.20140424-1

When I try to invoke runPmv script I get an error which I think is about 
Tkinter library.
Here is a transcript:

$ runPmv
Run PMV from  /usr/lib/python2.7/dist-packages/Pmv
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/Pmv/__init__.py", line 381, in runPmv
title=title, withShell= not interactive, verbose=False, gui=gui)
  File "/usr/lib/python2.7/dist-packages/Pmv/moleculeViewer.py", line 1026, in 
__init__
trapExceptions=trapExceptions)
  File "/usr/lib/python2.7/dist-packages/ViewerFramework/VF.py", line 387, in 
__init__
verbose=verbose)
  File "/usr/lib/python2.7/dist-packages/ViewerFramework/VFGUI.py", line 444, 
in __init__
verbose=verbose,guiMaster=VIEWER_root,)
  File "/usr/lib/python2.7/dist-packages/DejaVu/Viewer.py", line 586, in 
__init__
cnf=cnf, **kw)
  File "/usr/lib/python2.7/dist-packages/DejaVu/Viewer.py", line 285, in 
AddCamera
c = classCamera(master, screenName, self, num, cnf=cnf, **kw)
  File "/usr/lib/python2.7/dist-packages/DejaVu/Camera.py", line 2189, in 
__init__
self.AddTrackball()
  File "/usr/lib/python2.7/dist-packages/DejaVu/Camera.py", line 2583, in 
AddTrackball
self.trackball = Trackball(self, size, rscale, tscale, sscale, renorm )
  File "/usr/lib/python2.7/dist-packages/DejaVu/Trackball.py", line 88, in 
__init__
self.createSpinGui()
  File "/usr/lib/python2.7/dist-packages/DejaVu/Trackball.py", line 726, in 
createSpinGui
callback=self.setWithSpinGui,
  File 
"/usr/lib/python2.7/dist-packages/mglutil/gui/BasicWidgets/Tk/vector3DGUI.py", 
line 90, in __init__
self.createEntries(self.frame)
  File 
"/usr/lib/python2.7/dist-packages/mglutil/gui/BasicWidgets/Tk/vector3DGUI.py", 
line 360, in createEntries
self.f.grid(column=3, rowspan=3)
  File "/usr/lib/python2.7/lib-tk/Tkinter.py", line 2022, in grid_configure
+ self._options(cnf, kw))
TclError: cannot use geometry manager grid inside 
.139781089293520.139781089294024.139781017157144.139781017220880 which already 
has slaves managed by pack


I am using Debian GNU/Linux 8.7, kernel 3.16.0-4-amd64
and python 2.7.9-1

--- End Message ---
--- Begin Message ---
Version: 1.5.7-3+rm

Dear submitter,

as the package mgltools-pmv 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/855701

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#798738: marked as done (fontypython: Fonty Python doesn't start, throws wx._core.PyAssertionError)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:52:57 +
with message-id 
and subject line Bug#943872: Removed package(s) from unstable
has caused the Debian Bug report #798738,
regarding fontypython: Fonty Python doesn't start, throws 
wx._core.PyAssertionError
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.)


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

Dear Maintainer,

Fonty Python cannot start due to:

andreas@machine:~$ fontypython
Traceback (most recent call last):
  File "/usr/bin/start_fontypython", line 24, in 
import fontypythonmodules.start
  File "/usr/lib/python2.7/dist-packages/fontypythonmodules/start.py", line 25,
in 
import fontypythonmodules.wxgui
  File "/usr/lib/python2.7/dist-packages/fontypythonmodules/wxgui.py", line
404, in 
app = App(0)
  File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py", line 8628,
in __init__
self._BootstrapApp()
  File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_core.py", line 8196,
in _BootstrapApp
return _core_.PyApp__BootstrapApp(*args, **kwargs)
  File "/usr/lib/python2.7/dist-packages/fontypythonmodules/wxgui.py", line
396, in OnInit
frame = MainFrame(None, _("Fonty Python: bring out your fonts!"))
  File "/usr/lib/python2.7/dist-packages/fontypythonmodules/wxgui.py", line
162, in __init__
self.nb = NoteBook(self.panelNotebook)
  File "/usr/lib/python2.7/dist-packages/fontypythonmodules/gui_Left.py", line
95, in __init__
self.dircontrol = DirControl(pan1)
  File "/usr/lib/python2.7/dist-packages/fontypythonmodules/gui_Left.py", line
46, in __init__
wx.GenericDirCtrl.__init__(self, parent, -1, dir = startdir,
style=wx.DIRCTRL_DIR_ONLY)
  File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk2/wx/_controls.py", line
5652, in __init__
_controls_.GenericDirCtrl_swiginit(self,_controls_.new_GenericDirCtrl(*args,
**kwargs))
wx._core.PyAssertionError: C++ assertion "!empty()" failed at
.../include/wx/string.h(1536) in Last(): wxString: index out of bounds

Regards

Andreas




-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

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

Versions of packages fontypython depends on:
ii  python   2.7.9-1
ii  python-imaging   2.9.0-1
ii  python-wxgtk3.0  3.0.2.0+dfsg-1

fontypython recommends no packages.

fontypython suggests no packages.

-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.5-1+rm

Dear submitter,

as the package fontypython 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/943872

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#914884: marked as done (Crashes with wx._core.PyAssertionError: C++ assertion "isOpaque" failed..)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:52:57 +
with message-id 
and subject line Bug#943872: Removed package(s) from unstable
has caused the Debian Bug report #798738,
regarding Crashes with wx._core.PyAssertionError: C++ assertion "isOpaque" 
failed..
to be marked as done.

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

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


-- 
798738: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=798738
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: fontypython
Version: 0.5-1
Severity: grave

Fontypython crashing with following output.

$ fontypython
Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk3/wx/_misc.py", line 1367, 
in Notify
self.notify()
  File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk3/wx/_core.py", line 16868, 
in Notify
self.result = self.callable(*self.args, **self.kwargs)
  File "/usr/lib/python2.7/dist-packages/fontypythonmodules/wxgui.py", line 
908, in showMain
fpwx.setup_fonts_and_colours()
  File "/usr/lib/python2.7/dist-packages/fontypythonmodules/fpwx.py", line 53, 
in setup_fonts_and_colours
HTMLCOLS[k] = v.GetAsString(flags=wx.C2S_HTML_SYNTAX)
  File "/usr/lib/python2.7/dist-packages/wx-3.0-gtk3/wx/_gdi.py", line 205, in 
GetAsString
return _gdi_.Colour_GetAsString(*args, **kwargs)
wx._core.PyAssertionError: C++ assertion "isOpaque" failed at 
../src/common/colourcmn.cpp(228) in GetAsString(): alpha is lost in HTML syntax

Upstream is aware about bug and working on it.

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

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

Versions of packages fontypython depends on:
ii  python   2.7.15-3
ii  python-pil   5.3.0-1
ii  python-wxgtk3.0  3.0.2.0+dfsg-8

fontypython recommends no packages.

fontypython suggests no packages.

-- no debconf information

-- 
Kartik Mistry | IRC: kart_
https://kartikm.wordpress.com


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Version: 0.5-1+rm

Dear submitter,

as the package fontypython 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/943872

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:52:08 +
with message-id 
and subject line Bug#938827: Removed package(s) from unstable
has caused the Debian Bug report #938827,
regarding RM: winpdb -- RoQA; semi-dead upstream; unmaintained; low popcon; 
blocking py2 removal
to be marked as done.

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

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


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

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

If there are questions, please refer to the wiki page for the removal:
https://wiki.debian.org/Python/2Removal, or ask for help on IRC
#debian-python, or the debian-pyt...@lists.debian.org mailing list.
--- End Message ---
--- Begin Message ---
We believe that the bug you reported is now fixed; the following
package(s) have been removed from unstable:

winpdb |1.4.8-3 | source, all

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

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

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

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

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

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

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 

Bug#948452: closing 948452

[Salvatore Bonaccorso]

close 948452 72.0.1-1
thanks

Processed: closing 948452

[Debian Bug Tracking System]

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

> close 948452 72.0.1-1
Bug #948452 {Done: Mike Hommey } [firefox] firefox: Please 
update to 72.0.1 (and firefox-esr to 68.4.1) because of CVE-2019-17026
Marked as fixed in versions firefox/72.0.1-1; no longer marked as fixed in 
versions 72.0.1-1.
Bug #948452 {Done: Mike Hommey } [firefox] firefox: Please 
update to 72.0.1 (and firefox-esr to 68.4.1) because of CVE-2019-17026
Bug 948452 is already marked as done; not doing anything.
> thanks
Stopping processing here.

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

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

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 05:49:48 +
with message-id 
and subject line Bug#948431: Removed package(s) from unstable
has caused the Debian Bug report #937944,
regarding python-networkx: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-networkx

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.2-5+rm

Dear submitter,

as the package python-networkx 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/948431

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: Re: Bug#948473: cain: should this package be removed?

[Debian Bug Tracking System]

Processing control commands:

> retitle -1 keep cain out of testing
Bug #948473 [src:cain] cain: should this package be removed?
Changed Bug title to 'keep cain out of testing' from 'cain: should this package 
be removed?'.

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

Bug#948473: cain: should this package be removed?

[Sandro Tosi]

control: retitle -1 keep cain out of testing

On Thu, Jan 9, 2020 at 12:12 AM Andreas Tille  wrote:
>
> Hi Sandro,
>
> On Wed, Jan 08, 2020 at 09:28:16PM -0500, Sandro Tosi wrote:
> >
> > * 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)
>
> I once gave it a try with 2to3 but failed.  I intend to give
> it another try later.
>
> > * one of the only 2 reverse-dependency for python-scipy
>
> For the moment I think removing cain from testing and remove
> Python2 version of python-scipy is OK.  Cain definitely should
> not block progress in scipy.

i'll ask the RT to remove it from testing from the time being, this RC
bug will prevent it from re-entering.

> > 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.
>
> If you do not agree with the method above I'm fine with the
> removal.

i mean, it's fine, but is it maintainable? this is a big piece of code
that no upstream developer has supported in 7 and a half years. you're
gonna end up with a gigantic 2to3 patch and then what? what if 3.8
breaks it, or 3.9? or the next numpy, etc: whos gonna maintain it?

are there any unittests to guarantee the 2to3 conversion is ok? from a
quick look at the package it looks like there are exactly 0 tests, not
comforting :( 
https://salsa.debian.org/med-team/cain/blob/master/debian/rules#L41

the ultimate question is: is it worth to keep this software in debian
since there's nobody outside willing to commit time and effort to
maintain and evolve it? are you, alone, gonna do it?

i dont think it's a sustainable approach to just 2to3 and live to see
another day: this py2removal is also a good opportunity to get rid of
old/unused/unmaintained packages; to my eyes src:cain look like one of
them

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

Bug#948473: cain: should this package be removed?

[Andreas Tille]

Hi Sandro,

On Wed, Jan 08, 2020 at 09:28:16PM -0500, Sandro Tosi wrote:
> 
> * 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)

I once gave it a try with 2to3 but failed.  I intend to give
it another try later.

> * one of the only 2 reverse-dependency for python-scipy

For the moment I think removing cain from testing and remove
Python2 version of python-scipy is OK.  Cain definitely should
not block progress in 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.

If you do not agree with the method above I'm fine with the
removal.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#948404: glances crashes on startup

[Daniel Echeverry]

tags 948404 + moreinfo unreproducible
thanks

Hi!

Thanks for your report! Unfortunately I can't reproduce this bug, I install 
glances via ap-get install and works fine, However, I think that bug is related 
with this other bug[1], One Question, Do you have network interfaces?

Regards.

[1]: https://github.com/nicolargo/glances/issues/1535


signature.asc
Description: PGP signature

Processed: Re: Bug#948404: glances crashes on startup

[Debian Bug Tracking System]

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

> tags 948404 + moreinfo unreproducible
Bug #948404 [glances] glances crashes on startup
Added tag(s) unreproducible and moreinfo.
> thanks
Stopping processing here.

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

Bug#943052: marked as done (distro-info: Python2 removal in sid/bullseye)

[Debian Bug Tracking System]

Your message dated Thu, 09 Jan 2020 04:19:16 +
with message-id 
and subject line Bug#943052: fixed in distro-info 0.23
has caused the Debian Bug report #943052,
regarding distro-info: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Wed, 08 Jan 2020 23:06:26 -0500
Source: distro-info
Architecture: source
Version: 0.23
Distribution: unstable
Urgency: medium
Maintainer: Benjamin Drung 
Changed-By: Sandro Tosi 
Closes: 936408 943052
Changes:
 distro-info (0.23) unstable; urgency=medium
 .
   * Drop python2 support; Closes: #943052, #936408
Checksums-Sha1:
 a770b99a8739e1c27a6923f5ecab5a9d8d346d5b 1948 distro-info_0.23.dsc
 5b775ce4c92ef5313419e3d3db95e7a416ccdbf7 28832 distro-info_0.23.tar.xz
 f2f6b8ac818c307ff5bb7b3689292977e665051f 6752 distro-info_0.23_source.buildinfo
Checksums-Sha256:
 9e3d68a5d6b87877855bfd996a87196fd465d494d4625cf3e237ca2f79edea6e 1948 
distro-info_0.23.dsc
 38572fab05cb6a309240a10f9b004e202f3362a53f0684257e5e84036491c473 28832 
distro-info_0.23.tar.xz
 acfc319738b10540184a7903ce8f0e9f0b702961501750e9f6cee6dea47ab5ff 6752 
distro-info_0.23_source.buildinfo
Files:
 e6d951f6276cd639830e5289152d7aba 1948 devel optional distro-info_0.23.dsc
 8fe1bffdd559e66e6e9d4de961b6a206 28832 devel optional distro-info_0.23.tar.xz
 ac8e9fa881b497da557705f44609fdc0 6752 devel optional 
distro-info_0.23_source.buildinfo

-BEGIN PGP 

Bug#943052: marked as pending in distro-info

[Sandro Tosi]

Control: tag -1 pending

Hello,

Bug #943052 in distro-info 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/debian/distro-info/commit/723f1a6ca4f386c371dea4e15f6da1d7b021cb5d


Drop python2 support; Closes: #943052, #936408


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/943052

Processed: Bug#943052 marked as pending in distro-info

[Debian Bug Tracking System]

Processing control commands:

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

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

Processed: py2removal bugs severity updates - 2020-01-09 03:36:13.627321+00:00

[Debian Bug Tracking System]

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

> # This is an automated script, part of the effort for the removal of Python 2 
> from bullseye
> #  * https://wiki.debian.org/Python/2Removal
> #  * http://sandrotosi.me/debian/py2removal/index.html
> # See https://lists.debian.org/debian-devel-announce/2019/11/msg0.html
> # and https://lists.debian.org/debian-python/2019/12/msg00076.html
> # mail threads for more details on this severity update
> # python-lzma is a module and has 0 external rdeps or not in testing
> severity 937902 serious
Bug #937902 [src:python-lzma] python-lzma: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-rpy2 is a module and has 0 external rdeps or not in testing
> severity 938412 serious
Bug #938412 [src:rpy2-2.8] rpy2-2.8: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> # python-distro-info is a module and has 0 external rdeps or not in testing
> severity 943052 serious
Bug #943052 [src:distro-info] distro-info: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
>
End of message, stopping processing here.

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

Bug#948473: cain: should this package be removed?

[Sandro Tosi]

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

Processed: Re: /usr/bin/tifffile doesn't work

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #939511 {Done: Andreas Tille } [tifffile] 
/usr/bin/tifffile doesn't work
Added tag(s) pending.

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

Bug#939511: /usr/bin/tifffile doesn't work

[Andreas Beckmann]

Followup-For: Bug #939511
Control: tag -1 pending

buster-pu request: https://bugs.debian.org/948472


Andreas

Bug#948452: marked as done (firefox: Please update to 72.0.1 (and firefox-esr to 68.4.1) because of CVE-2019-17026)

[Debian Bug Tracking System]

Your message dated Thu, 9 Jan 2020 09:26:57 +0900
with message-id <20200109002657.nglycrd6zctvo...@glandium.org>
and subject line Re: Bug#948452: firefox: Please update to 72.0.1 (and 
firefox-esr to 68.4.1) because of CVE-2019-17026
has caused the Debian Bug report #948452,
regarding firefox: Please update to 72.0.1 (and firefox-esr to 68.4.1) because 
of CVE-2019-17026
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.)


-- 
948452: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948452
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: firefox
Version: 72.0-1
Severity: important
Tags: upstream

Dear Maintainer,

As I mention in the title, firefox was updated to 72.0.1 today, just 1 day
after the release of 72.0, in order to close cve-2019-17026.
Here is the relevant post from mozilla
https://www.mozilla.org/en-US/security/advisories/mfsa2020-03/



-- Package-specific info:

-- Extensions information
Name: Amazon.com
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled

Name: Bing
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled

Name: Dark theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled

Name: Default theme
Location: /usr/lib/firefox/omni.ja
Package: firefox
Status: enabled

Name: DoH Roll-Out
Location: /usr/lib/firefox/browser/features/doh-roll...@mozilla.org.xpi
Package: firefox
Status: enabled

Name: DuckDuckGo
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled

Name: Firefox Screenshots
Location: /usr/lib/firefox/browser/features/screensh...@mozilla.org.xpi
Package: firefox
Status: enabled

Name: Form Autofill
Location: /usr/lib/firefox/browser/features/formautof...@mozilla.org.xpi
Package: firefox
Status: enabled

Name: Google
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled

Name: Light theme
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: user-disabled

Name: PlayThis
Location: ${PROFILE_EXTENSIONS}/playt...@anxdpanic.xpi
Status: enabled

Name: Twitter
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled

Name: uBlock Origin
Location: ${PROFILE_EXTENSIONS}/ublo...@raymondhill.net.xpi
Status: enabled

Name: Video DownloadHelper
Location: ${PROFILE_EXTENSIONS}/{b9db16a4-6edc-47ec-a1f4-b86292ed211d}.xpi
Status: enabled

Name: Web Compat
Location: /usr/lib/firefox/browser/features/webcom...@mozilla.org.xpi
Package: firefox
Status: enabled

Name: WebCompat Reporter
Location: /usr/lib/firefox/browser/features/webcompat-repor...@mozilla.org.xpi
Package: firefox
Status: user-disabled

Name: Wikipedia (en)
Location: /usr/lib/firefox/browser/omni.ja
Package: firefox
Status: enabled

-- Plugins information
Name: Shockwave Flash (32.0.0.293)
Location: /usr/lib/flashplayer-mozilla/libflashplayer.so
Package: flashplayer-mozilla
Status: disabled


-- Addons package information
ii  firefox 72.0-1amd64Mozilla Firefox web 
browser
ii  flashplayer-mozilla 3:32.0.0.293-dmo1 amd64Adobe Flash Player

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

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

Versions of packages firefox depends on:
ii  debianutils   4.9.1
ii  fontconfig2.13.1-2+b1
ii  libatk1.0-0   2.34.1-1
ii  libc6 2.29-7
ii  libcairo-gobject2 1.16.0-4
ii  libcairo2 1.16.0-4
ii  libdbus-1-3   1.12.16-2
ii  libdbus-glib-1-2  0.110-5
ii  libevent-2.1-72.1.11-stable-1
ii  libffi6   3.2.1-9
ii  libfontconfig12.13.1-2+b1
ii  libfreetype6  2.10.1-2
ii  libgcc1   1:9.2.1-22
ii  libgdk-pixbuf2.0-02.40.0+dfsg-2
ii  libglib2.0-0  2.62.4-1
ii  libgtk-3-03.24.13-1
ii  libnspr4  2:4.24-1
ii  libnss3   2:3.48-1
ii  libpango-1.0-01.42.4-7
ii  libsqlite3-0  3.30.1+fossil191229-1
ii  libstartup-notification0  0.12-6
ii  libstdc++69.2.1-22
ii  libx11-6  2:1.6.8-1
ii  libx11-xcb1   2:1.6.8-1
ii  

Bug#947865: marked as done (pyopencl: FTBFS in sid)

[Debian Bug Tracking System]

Your message dated Thu, 9 Jan 2020 00:38:32 +0100
with message-id 
and subject line Re: [Pkg-opencl-devel] Bug#947865: pyopencl: FTBFS in sid
has caused the Debian Bug report #947865,
regarding pyopencl: FTBFS in sid
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.)


-- 
947865: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947865
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: pyopencl
Version: 2019.1.1-1
Severity: serious
Tags: patch
Justification: FTBFS

Hello,

pyopencl currently FTBFS in sid because  apparently moved to
libgl-dev. The attached patch fixes that.

Samuel

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

Kernel: Linux 5.4.0 (SMP w/8 CPU cores)
Kernel taint flags: TAINT_OOT_MODULE
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 /bin/dash
Init: systemd (via /run/systemd/system)

-- 
Samuel
Linux, c'est simple : ça s'adresse à une machine qui est parfois un peu
maraboutée mais qui d'habitude n'a pas d'états d'âme. Sur Usenet y'a
plein d'humains et de primates, et ça devient vraiment gore par moment.
-+- TP in : Guide du linuxien pervers - "Le linuxien a-t-il une âme ?" -+-
--- debian/control.original 2020-01-01 02:25:30.482219682 +0100
+++ debian/control  2020-01-01 02:25:33.052221180 +0100
@@ -15,7 +15,7 @@
  python3-setuptools,
  opencl-c-headers,
  ocl-icd-opencl-dev | opencl-dev,
- mesa-common-dev,
+ mesa-common-dev, libgl-dev,
  python3-numpy,
  python3-sphinx (>= 1.0.7+dfsg) ,
  python3-mako,
--- End Message ---
--- Begin Message ---
On 01/01/2020 02.35, Samuel Thibault wrote:
> pyopencl currently FTBFS in sid because  apparently moved to
> libgl-dev. The attached patch fixes that.

It was a bug in src:mesa not to have proper dependencies for the headers
being moved to src:libglvnd. #947392

In case you filed more similar bugs, please check whether they could be
closed now, too.

Andreas--- End Message ---

Bug#947712: autopkgtest regressions in python-dbusmock with newer network-manager 1.22.2-1

[Martin Pitt]

Hello Michael and Thomas,

Michael Biebl [2020-01-08 19:42 +0100]:
> > The latest update of network-manager causes an autopkgtest regression in
> > python-dbusmock.
> > 
> > https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/3793816/log.gz
> > 
> > ==
> > FAIL: test_eth_and_wifi (__main__.TestNetworkManager)
> > --
> > Traceback (most recent call last):
> >   File "test_networkmanager.py", line 138, in test_eth_and_wifi
> > self.assertRegex(out, r'eth0.*\sdisconnected')
> > AssertionError: Regex didn't match: 'eth0.*\\sdisconnected' not found in 
> > 'DEVICE  TYPE  STATECONNECTION \neth0ethernet  unknown  --  
> >\nwlan0   wifi  unknown  -- \n'

Note that this may look similar to the recent StateReason issue fixed in
https://github.com/martinpitt/python-dbusmock/commit/bd51d9108e08
but it's different.

python-dbusmock upstream runs tests against Fedora rawhide as well, and I just
restarted a run against latest rawhide:
https://travis-ci.org/martinpitt/python-dbusmock/jobs/628460969
this succeeds against NetworkManager-1:1.22.2-1.fc32.x86_64, i. e. the same NM
upstream version that up uploaded into Debian.

As per https://ci.debian.net/packages/p/python-dbusmock/unstable/amd64/ the
first failure happened in
https://ci.debian.net/data/packages/unstable/amd64/p/python-dbusmock/3694572.log
against NM 1.22.0, while the last successful run was against 1.20.8.

I'll investigate this more closely tomorrow. Right now my sid schroot is rather
broken due to some weirdness with gnupg disappearing from the archive.

Thanks,

Martin

Processed: Re: pykaraoke: Pykaraoke doesn't work because it needs packages "ttf-dejavu ttf-dejavu-extra"

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #948385 [src:pykaraoke] pykaraoke: Pykaraoke doesn't work because it needs 
packages "ttf-dejavu ttf-dejavu-extra"
Added tag(s) pending.
> found -1 0.7.5-1.2
Bug #948385 [src:pykaraoke] pykaraoke: Pykaraoke doesn't work because it needs 
packages "ttf-dejavu ttf-dejavu-extra"
Marked as found in versions pykaraoke/0.7.5-1.2.

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

Bug#948385: pykaraoke: Pykaraoke doesn't work because it needs packages "ttf-dejavu ttf-dejavu-extra"

[Andreas Beckmann]

Followup-For: Bug #948385
Control: tag -1 pending
Control: found -1 0.7.5-1.2

No need for the transitional ttf-* packages, just fix the symlinks:
s/ttf-//.

buster-pu:  https://bugs.debian.org/948464
stretch-pu: https://bugs.debian.org/948465

Andreas

Bug#947613: [Pkg-utopia-maintainers] Bug#947613: network-manager: Wi-Fi not working (does not get IPv4 address) with 1.22.2-1

[Eugen Dedu]

On 08/01/2020 16:07, Michael Biebl wrote:

Anyone willing to check the proposed fix
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/848b869c6ede3a796872a0b5cd8b2398804c3697


Hi,

I tested the proposed patch on top of debian's 1.22.2-1 version.  This 
patch does NOT fix the issue.


I would say it is even worse.  The network-manager-gnome icon in the 
task bar (I use awesome window manager) turns around and restarts 
several times, each time with a different MAC address (as shown by 
ifconfig) and getting and losing an inet6 address.  After around 10 
restarts, it finally stops and shows "NetworkManager is not running".


I could provide a small video if it helps.

Cheers.
Eugen

Bug#948417: marked as done (python-astor ftbfs with Python 3.8)

[Debian Bug Tracking System]

Your message dated Wed, 08 Jan 2020 22:08:53 +
with message-id 
and subject line Bug#948417: fixed in python-astor 0.8.1-1
has caused the Debian Bug report #948417,
regarding python-astor 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.)


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

There's a new upstream, which I didn't check.

[...]
pkg-buildpackage
-

dpkg-buildpackage: info: source package python-astor
dpkg-buildpackage: info: source version 0.8.0-2build1
dpkg-buildpackage: info: source distribution focal
 dpkg-source --before-build .
dpkg-buildpackage: info: host architecture amd64
 fakeroot debian/rules clean
dh clean --with python3 --buildsystem pybuild
   dh_auto_clean -O--buildsystem=pybuild
I: pybuild base:217: python3.8 setup.py clean
Traceback (most recent call last):
  File "setup.py", line 17, in 
setup(**config['options'])
  File "/usr/lib/python3/dist-packages/setuptools/__init__.py", line 145, in 
setup
return distutils.core.setup(**attrs)
  File "/usr/lib/python3.8/distutils/core.py", line 108, in setup
_setup_distribution = dist = klass(attrs)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 446, in 
__init__
_Distribution.__init__(self, {
  File "/usr/lib/python3.8/distutils/dist.py", line 292, in __init__
self.finalize_options()
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 735, in
finalize_options
ep.load()(self, ep.name, value)
  File "/usr/lib/python3/dist-packages/setuptools/dist.py", line 291, in
check_specifier
packaging.specifiers.SpecifierSet(value)
  File
"/usr/lib/python3/dist-packages/setuptools/_vendor/packaging/specifiers.py",
line 594, in __init__
specifiers = [s.strip() for s in specifiers.split(",") if s.strip()]
AttributeError: 'SpecifierSet' object has no attribute 'split'
E: pybuild pybuild:341: clean: plugin distutils failed with: exit code=1:
python3.8 setup.py clean
dh_auto_clean: pybuild --clean --test-pytest -i python{version} -p "3.8 3.7"
returned exit code 13
make: *** [debian/rules:9: clean] Error 255
--- End Message ---
--- Begin Message ---
Source: python-astor
Source-Version: 0.8.1-1

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

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

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

Debian distribution maintenance software
pp.
Tianon Gravi  (supplier of updated python-astor package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 08 Jan 2020 13:48:12 -0800
Source: python-astor
Architecture: source
Version: 0.8.1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Python Modules Team 

Changed-By: Tianon Gravi 
Closes: 948417
Changes:
 python-astor (0.8.1-1) unstable; urgency=medium
 .
   * Update to 0.8.1 upstream release
 - https://github.com/berkerpeksag/astor/pull/163 (Closes: #948417)
Checksums-Sha1:
 a365c0db4812664423746ec7a9247465fe26ffad 2131 python-astor_0.8.1-1.dsc
 b69d52ff16b1bcde5b089ba4708b8ba69ec686d8 35090 python-astor_0.8.1.orig.tar.gz
 5cf3cf9b383122d8c3b1e45c6ca4d05ebfcef8a2 3216 
python-astor_0.8.1-1.debian.tar.xz
 c66a33dc8b23eefba86b23e72020ae25c69796f4 6453 
python-astor_0.8.1-1_source.buildinfo
Checksums-Sha256:
 9fb95562bcce188476fbeecfe86dc04ad5637b50f0f1a12dd12e606f93b8c486 2131 
python-astor_0.8.1-1.dsc
 6a6effda93f4e1ce9f618779b2dd1d9d84f1e32812c23a29b3fff6fd7f63fa5e 35090 
python-astor_0.8.1.orig.tar.gz
 451547d714362174577f46ad01c17403eec3dd9f6441ff5bc2f241ffe4db98ae 3216 
python-astor_0.8.1-1.debian.tar.xz
 ac7515d11fa55b2bc533c566d31f11831c4d81a8d64d01b809c3eec186c1edb8 6453 
python-astor_0.8.1-1_source.buildinfo
Files:
 61f1a356c208a05bbe6b080cb0534d4e 2131 python optional python-astor_0.8.1-1.dsc
 83ab4ee6598f0381d94ed6949a6d6da2 35090 python optional 
python-astor_0.8.1.orig.tar.gz
 d9fad07496ed7c4ae72996079a40a0bf 3216 python optional 
python-astor_0.8.1-1.debian.tar.xz
 ec3be4f243fb93d26c5700ed1af71610 

Bug#948460: xserver-xorg-video-nvidia-legacy-340xx: Xorg won't start with xserver-xorg-video-nvidia-legacy-340xx on testing/Bullseye

[Andreas Beckmann]

On 08/01/2020 21.53, Alexis wrote:
> So I installed packages to use the nvidia proprietary drivers (xserver-xorg-
> video-nvidia-legacy-340xx and related packages).

You didn't install the metapackage nvidia-legacy-340xx-driver, did you?

> pn  nvidia-legacy-340xx-driver  
> ii  nvidia-legacy-340xx-kernel-dkms 340.108-2
> pn  nvidia-legacy-340xx-kernel-source   
> hi  nvidia-legacy-340xx-kernel-support [nvidia-kernel-support-any]  340.108-2

And the glx alternative still points to mesa:

> lrwxrwxrwx 1 root root   22 Jan  7 23:11 /etc/alternatives/glx -> 
> /usr/lib/mesa-diverted

which effectively disables the nvidia driver.

I cannot reproduce this by just installing
xserver-xorg-video-nvidia-legacy-340xx (without Recommends)
in a minimal buster chroot - the glx alternative is nvidia as it should
be.

You should undo all manual filesystem manipulations
(moving nvidia_drv.so, creating Xorg.conf, ...) and purge all nvidia
packages. Thereafter install nvidia-legacy-340xx-driver again.


Andreas

Bug#930764: marked as done (Fails to configure package due to "unknown type of DB: BACKUP" on upgrade-db)

[Debian Bug Tracking System]

Your message dated Wed, 08 Jan 2020 21:47:08 +
with message-id 
and subject line Bug#930764: fixed in cyrus-imapd 3.0.8-6+deb10u4
has caused the Debian Bug report #930764,
regarding Fails to configure package due to "unknown type of DB: BACKUP" on 
upgrade-db
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.)


-- 
930764: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930764
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cyrus-common
Version: 3.0.8-6
Severity: important

Dear Maintainer,

I'm getting this error after upgrading to 3.0.8-6

  $ dpkg --configure --pending
  Setting up cyrus-common (3.0.8-6) ...
  Creating/updating cyrus user account...
  The user `cyrus' is already a member of `sasl'.
  /usr/lib/cyrus/bin/upgrade-db: Unknown type of DB: BACKUP
  dpkg: error processing package cyrus-common (--configure):
   installed cyrus-common package post-installation script subprocess returned 
error exit status 1

I previously had 3.0.8-5 installed. There are 2 files that the upgrade-db
script looks at. They look like this:

  /usr/lib/cyrus/cyrus-db-types.txt:

ANNOTATION twoskip
BACKUP twoskip
CONVERSATIONS skiplist
DBENGINE BerkeleyDB5.3
DUPLICATE twoskip
MBOX twoskip
PTS twoskip
QUOTA quotalegacy
SEARCH_INDEXED twoskip
SEEN twoskip
SORTCACHE twoskip
STATUSCACHE twoskip
SUBS flat
TLS twoskip
USERDENY flat
ZONEINFO twoskip

  /usr/lib/cyrus/cyrus-db-types.active:

ANNOTATION twoskip
BACKUP twoskip
CONVERSATIONS skiplist
DBENGINE BerkeleyDB5.3
DUPLICATE twoskip
MBOX twoskip
PTS twoskip
QUOTA quotalegacy
SEARCH_INDEXED twoskip
SEEN twoskip
SORTCACHE twoskip
STATUSCACHE twoskip
SUBS flat
TLS twoskip
USERDENY flat
ZONEINFO twoskip

It looks like "BACKUP" is missing from the case statement which is causing
the error I'm seeing. Additionally, it looks like "CONVERSATIONS",
"SEARCH_INDEXED", and "SORTCACHE" are also missing.

Thanks,
  David


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

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

Versions of packages cyrus-common depends on:
ii  adduser  3.118
ii  db-upgrade-util  5.3.1+nmu1
ii  db-util  5.3.1+nmu1
ii  debconf [debconf-2.0]1.5.71
ii  dpkg 1.19.7
ii  e2fsprogs1.44.5-1
ii  gawk 1:4.2.1+dfsg-1
ii  init-system-helpers  1.56+nmu1
ii  libc62.28-10
ii  libclamav9   0.101.2+dfsg-1
ii  libcom-err2  1.44.5-1
ii  libgcc1  1:8.3.0-2
ii  libgssapi-krb5-2 1.17-2
ii  libical3 3.0.4-3
ii  libicu63 63.1-6
ii  libjansson4  2.12-1
ii  libk5crypto3 1.17-2
ii  libkrb5-31.17-2
ii  libkrb5support0  1.17-2
ii  libldap-2.4-22.4.47+dfsg-3
ii  libpcre3 2:8.39-12
ii  libsasl2-2   2.1.27+dfsg-1
ii  libsasl2-modules 2.1.27+dfsg-1
ii  libsnmp305.7.3+dfsg-5
ii  libsqlite3-0 3.27.2-3
ii  libssl1.11.1.1c-1
ii  libstdc++6   8.3.0-2
ii  libwrap0 7.6.q-28
ii  libxapian30  1.4.11-1
ii  libxml2  2.9.4+dfsg1-7+b3
ii  libzephyr4   3.1.2-1+b3
ii  lsb-base 10.2019051400
ii  netbase  5.6
ii  perl 5.28.1-6
ii  sendmail-bin [mail-transport-agent]  8.15.2-12
ii  zlib1g   1:1.2.11.dfsg-1

Versions of packages cyrus-common recommends:
iu  cyrus-admin  3.0.8-6
iu  cyrus-imapd  3.0.8-6

Versions of packages cyrus-common suggests:
ii  apt-listchanges3.19
iu  cyrus-admin3.0.8-6
pn  cyrus-caldav   
iu  cyrus-clients  3.0.8-6
ii  cyrus-doc  

Bug#946937: marked as done (python-django: CVE-2019-19844: Potential account hijack via password reset form)

[Debian Bug Tracking System]

Your message dated Wed, 08 Jan 2020 21:47:38 +
with message-id 
and subject line Bug#946937: fixed in python-django 1:1.10.7-2+deb9u7
has caused the Debian Bug report #946937,
regarding python-django: CVE-2019-19844: Potential account hijack via password 
reset form
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.)


-- 
946937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1:1.10.7-2+deb9u6
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django.

CVE-2019-19844[0][1]: Potential account hijack via password
reset form

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-19844
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19844
[1] https://www.djangoproject.com/weblog/2019/dec/18/security-releases/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 1:1.10.7-2+deb9u7

We believe that the bug you reported is fixed in the latest version of
python-django, 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.
Chris Lamb  (supplier of updated python-django 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, 06 Jan 2020 17:52:10 +
Source: python-django
Binary: python-django python3-django python-django-common python-django-doc
Architecture: source all
Version: 1:1.10.7-2+deb9u7
Distribution: stretch-security
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Description:
 python-django - High-level Python web development framework (Python 2 version)
 python-django-common - High-level Python web development framework (common)
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework (Python 3 version)
Closes: 946937
Changes:
 python-django (1:1.10.7-2+deb9u7) stretch-security; urgency=high
 .
   * CVE-2019-19844: Prevent a potential account hijack via the password reset
 form. (Closes: #946937)
Checksums-Sha1:
 5d7572b2d103d2e38351251a55203a354d9ebbf4 2804 python-django_1.10.7-2+deb9u7.dsc
 5edd13a642460c33cdaf8e8166eccf6b2a2555df 7737654 
python-django_1.10.7.orig.tar.gz
 ec405d3ab180b33cf78449eb12af94dca4b80ddc 44024 
python-django_1.10.7-2+deb9u7.debian.tar.xz
 c4c293e6b8261d1857fa13353a0f4cf46109321f 1515080 
python-django-common_1.10.7-2+deb9u7_all.deb
 8b9ddfc21fb812d75e5961f028ca5b007b0a20c1 2536484 
python-django-doc_1.10.7-2+deb9u7_all.deb
 a7e7294eee602d7bf87cc41c78ca585d0e49f5d1 905080 
python-django_1.10.7-2+deb9u7_all.deb
 a70974a395b89996c1b1e1d42ba5a8a7e4c0641d 9386 
python-django_1.10.7-2+deb9u7_amd64.buildinfo
 8e78dc8699f240af25e93c43257e276c825aaec4 886618 
python3-django_1.10.7-2+deb9u7_all.deb
Checksums-Sha256:
 0b0bb55549574e2a65ffa79669757f4eb409dea8a124a759c3b7e331dac4214a 2804 
python-django_1.10.7-2+deb9u7.dsc
 593d779dbc2350a245c4f76d26bdcad58a39895e87304fe6d725bbdf84b5b0b8 7737654 
python-django_1.10.7.orig.tar.gz
 9325cadba0cb6b8f318a95e482deb71a271d87df1643fc7bea30fc571107c62c 44024 
python-django_1.10.7-2+deb9u7.debian.tar.xz
 0a174b5d64d6475dd2ccaef9f762fe2d538b4f1c02b381d0ed2a6a958fc84bc8 1515080 
python-django-common_1.10.7-2+deb9u7_all.deb
 168b275c555b91d42f156e71a4042832ac854877cd3efdfcbf56667ac163de2c 2536484 
python-django-doc_1.10.7-2+deb9u7_all.deb
 cf0cc4006230c8f7e37f6eca9ff31e644ef6fb979d42cfe355f494b54a819d39 905080 
python-django_1.10.7-2+deb9u7_all.deb
 c627110d9dfc4439ce57441c13858239f082ae4d4486fc780fa62bcbff337387 9386 
python-django_1.10.7-2+deb9u7_amd64.buildinfo
 831e7d7b3089d6b72d490cf343c03a29b9a690563cda53ae7d02b35f04669722 886618 
python3-django_1.10.7-2+deb9u7_all.deb
Files:
 

Bug#946937: marked as done (python-django: CVE-2019-19844: Potential account hijack via password reset form)

[Debian Bug Tracking System]

Your message dated Wed, 08 Jan 2020 21:47:11 +
with message-id 
and subject line Bug#946937: fixed in python-django 1:1.11.27-1~deb10u1
has caused the Debian Bug report #946937,
regarding python-django: CVE-2019-19844: Potential account hijack via password 
reset form
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.)


-- 
946937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946937
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-django
Version: 1:1.10.7-2+deb9u6
X-Debbugs-CC: t...@security.debian.org
Severity: grave
Tags: security

Hi,

The following vulnerability was published for python-django.

CVE-2019-19844[0][1]: Potential account hijack via password
reset form

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-19844
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-19844
[1] https://www.djangoproject.com/weblog/2019/dec/18/security-releases/


Regards,

-- 
  ,''`.
 : :'  : Chris Lamb
 `. `'`  la...@debian.org / chris-lamb.co.uk
   `-
--- End Message ---
--- Begin Message ---
Source: python-django
Source-Version: 1:1.11.27-1~deb10u1

We believe that the bug you reported is fixed in the latest version of
python-django, 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.
Chris Lamb  (supplier of updated python-django 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, 06 Jan 2020 15:35:55 +
Source: python-django
Binary: python-django python-django-common python-django-doc python3-django
Architecture: source all
Version: 1:1.11.27-1~deb10u1
Distribution: buster-security
Urgency: high
Maintainer: Debian Python Modules Team 

Changed-By: Chris Lamb 
Description:
 python-django - High-level Python web development framework (Python 2 version)
 python-django-common - High-level Python web development framework (common)
 python-django-doc - High-level Python web development framework (documentation)
 python3-django - High-level Python web development framework (Python 3 version)
Closes: 946937
Changes:
 python-django (1:1.11.27-1~deb10u1) buster-security; urgency=high
 .
   * New upstream security release. (Closes: #946937)
 
 .
 - CVE-2019-19844: Potential account hijack via password reset form.
 .
   By submitting a suitably crafted email address making use of Unicode
   characters, that compared equal to an existing user email when
   lower-cased for comparison, an attacker could be sent a password reset
   token for the matched account.
 .
   In order to avoid this vulnerability, password reset requests now compare
   the submitted email using the stricter, recommended algorithm for
   case-insensitive comparison of two identifiers from Unicode Technical
   Report 36, section 2.11.2(B)(2). Upon a match, the email containing the
   reset token will be sent to the email address on record rather than the
   submitted address.
Checksums-Sha1:
 dbd523d34605a28fb3880e870aab6809b230cb68 3267 
python-django_1.11.27-1~deb10u1.dsc
 8f0ad184cbae6e69dbe2a1f4d7ec32d842657001 7976980 
python-django_1.11.27.orig.tar.gz
 c8fbb06f8c6368f596d80e332c7518a537e7697f 27276 
python-django_1.11.27-1~deb10u1.debian.tar.xz
 4e7b6cb564fcbc0cadf3d8de400d39c9282c3654 1538076 
python-django-common_1.11.27-1~deb10u1_all.deb
 a054fee1e86f82030397bd841dfa5c78e968dc6a 2689580 
python-django-doc_1.11.27-1~deb10u1_all.deb
 bc8a14f1b1b3569da28028f4ec01806e7352dd77 917320 
python-django_1.11.27-1~deb10u1_all.deb
 9ac9abed0738fed7e8d951c7fa98cd43ae4a2298 14208 
python-django_1.11.27-1~deb10u1_amd64.buildinfo
 565b60900064d136e3d1a2b0b436cdf5c017c453 917472 
python3-django_1.11.27-1~deb10u1_all.deb
Checksums-Sha256:
 d8db6a86b018830d089524a77c5dbe35e2e5ee86fd7f66bbf6061e28a0f740cb 3267 
python-django_1.11.27-1~deb10u1.dsc
 

Bug#941266: marked as done (netty: CVE-2019-16869)

[Debian Bug Tracking System]

Your message dated Wed, 08 Jan 2020 21:47:37 +
with message-id 
and subject line Bug#941266: fixed in netty 1:4.1.7-2+deb9u1
has caused the Debian Bug report #941266,
regarding netty: CVE-2019-16869
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.)


-- 
941266: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941266
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: netty
Version: 1:4.1.33-1
Severity: important
Tags: security upstream
Forwarded: https://github.com/netty/netty/issues/9571

Hi,

The following vulnerability was published for netty.

CVE-2019-16869[0]:
| Netty before 4.1.42.Final mishandles whitespace before the colon in
| HTTP headers (such as a "Transfer-Encoding : chunked" line), which
| leads to HTTP request smuggling.


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-16869
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16869
[1] https://github.com/netty/netty/issues/9571

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: netty
Source-Version: 1:4.1.7-2+deb9u1

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

Debian distribution maintenance software
pp.
Salvatore Bonaccorso  (supplier of updated netty 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: Thu, 02 Jan 2020 23:46:59 +0100
Source: netty
Architecture: source
Version: 1:4.1.7-2+deb9u1
Distribution: stretch-security
Urgency: high
Maintainer: Debian Java Maintainers 

Changed-By: Salvatore Bonaccorso 
Closes: 941266
Changes:
 netty (1:4.1.7-2+deb9u1) stretch-security; urgency=high
 .
   * Non-maintainer upload by the Security Team.
   * Correctly handle whitespaces in HTTP header names as defined by
 RFC7230#section-3.2.4 (CVE-2019-16869) (Closes: #941266)
Checksums-Sha1: 
 a8683ab5dcba62dcd7f472c921e7ba8c6ce1691e 2709 netty_4.1.7-2+deb9u1.dsc
 504243f34ec66a82c068b22977dd712ac90b1d19 1358608 netty_4.1.7.orig.tar.xz
 c0f9acbdafbdd95e1fa422e6f30acf4b52e45a1e 10572 
netty_4.1.7-2+deb9u1.debian.tar.xz
Checksums-Sha256: 
 f29164833368fbf29bcb52a24922e8f3a3dd175ae68d4532835db6a0b19573f6 2709 
netty_4.1.7-2+deb9u1.dsc
 a4cb7f759dc00bfdbe0d1c3578f35361b3c0a48176e564ee621fae64e90ce4a3 1358608 
netty_4.1.7.orig.tar.xz
 e9a9569c51ab39b3e07bfa30801282b2ccdf8479f2e8b1837ffdd8ed6a7728ef 10572 
netty_4.1.7-2+deb9u1.debian.tar.xz
Files: 
 1ed6844fb896c3a30afd9b7fad2a008f 2709 java optional netty_4.1.7-2+deb9u1.dsc
 fb52f7379836392680cbaf3e3a83247a 1358608 java optional netty_4.1.7.orig.tar.xz
 430c35f329e7f26c6f6c06d96166dc79 10572 java optional 
netty_4.1.7-2+deb9u1.debian.tar.xz

-BEGIN PGP SIGNATURE-

iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAl4OdTNfFIAALgAo
aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2
NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk
ZWJpYW4ub3JnAAoJEAVMuPMTQ89EybkP/3/RvgFF4YSqf2UHvYg78GX6mcrRGsLw
lWD6/1KQUxTCjCbKSp4bChlRDV4jvtAASvwHnQT4SEcOHfCL8yxCSnCMhtHMFTNh
sE+nHpZGDRxpSui8mkrzc4kiek71TYvEwH9LzqBetxhk7S+zljQ2Tvf9Z4G2r4NK
iTBtghiIKzW10hSVwzFX8gw4gEeYD6PbAd7vPtUTP2nmq7CoQQDmhHO0XeW7X2pX
s96Mev+wiNNy3WeWEyQeeesORWxPK8vrJezvlPnWU6YRog8T8GK4GIcP5ucjXPdD
qLjeXaR+GTbl98lENCq+tzpUDufP4XU6ZANri6FKDrkAW+Wj5auss0YP5OJjHXJK
QRDeXIBgjU7lBqM3+BcjeULmWDCJ/s+lFrzJt9ofNg3aDxe3ZAp3EmSZb/GCZrBt
kl33giCR6VlH5FrQmSNC8CPdoghEFZk32CreI+7i6LvFt4G0hgepLcg0uQqWz2mi
X6Gg8QQhxsZmpSUv81fPK9P6aF5mXn1ttej5+I+YrHg+ZqH3jIYWqO8HhmU2dlKP
Iw4qODekd7EPgis/zhE2VNcj+Sfliowqv4ItJWnl/k2gjyjnGuuv/qzSgKrNlRtg
sIvgbHEfT0kUc1hkJgaaTxrXcglgaqt9C1sug+sLJlHBcVhPrg5fLoQBOCt9wskc
cHGRCXzx/8nV
=nYnr
-END PGP SIGNATURE End Message ---

Bug#930774: marked as done (guile-2.2: FTBFS when built with dpkg-buildpackage -A)

[Debian Bug Tracking System]

Your message dated Wed, 08 Jan 2020 21:47:09 +
with message-id 
and subject line Bug#930774: fixed in guile-2.2 2.2.4+1-2+deb10u1
has caused the Debian Bug report #930774,
regarding guile-2.2: FTBFS when built with dpkg-buildpackage -A
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.)


-- 
930774: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930774
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:guile-2.2
Version: 2.2.4+1-2
Severity: serious
Tags: ftbfs

Dear maintainer:

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


[...]
 debian/rules build-indep
dh build-indep --parallel --with autoreconf
   debian/rules override_dh_testdir
make[1]: Entering directory '/<>/guile-2.2-2.2.4+1'
dh_testdir debian/guile.postinst
make[1]: Leaving directory '/<>/guile-2.2-2.2.4+1'
   dh_update_autotools_config -i -O--parallel
   debian/rules override_dh_autoreconf
make[1]: Entering directory '/<>/guile-2.2-2.2.4+1'
echo '2.2.4' > .version
cp -a .version .tarball-version
dh_autoreconf ./autogen.sh

autoconf (GNU Autoconf) 2.69

[... snipped ...]

make[6]: Entering directory '/<>/guile-2.2-2.2.4+1/guile-readline'
make[6]: Nothing to be done for 'install-exec-am'.
 /bin/mkdir -p 
'/<>/guile-2.2-2.2.4+1/debian/tmp/usr/lib/x86_64-linux-gnu/guile/2.2/extensions'
 /bin/bash ../libtool   --mode=install install -p   guile-readline.la 
'/<>/guile-2.2-2.2.4+1/debian/tmp/usr/lib/x86_64-linux-gnu/guile/2.2/extensions'
libtool: warning: relinking 'guile-readline.la'
libtool: install: (cd /<>/guile-2.2-2.2.4+1/guile-readline; /bin/bash 
"/<>/guile-2.2-2.2.4+1/libtool"  --tag CC --mode=relink gcc 
-std=gnu11 -Wall -Wmissing-prototypes -Wdeclaration-after-statement 
-Wpointer-arith -Wswitch-enum -fno-strict-aliasing -fwrapv -g -O2 
-fdebug-prefix-map=/<>/guile-2.2-2.2.4+1=. -fstack-protector-strong 
-Wformat -Werror=format-security -DPACKAGE_PACKAGER=\"Debian\" 
-DPACKAGE_PACKAGER_VERSION=\"2.2.4-deb+1-2\" 
-DPACKAGE_PACKAGER_BUG_REPORTS=\"http://www.debian.org/Bugs/Reporting\; 
-fno-stack-protector -export-dynamic -no-undefined -module -Wl,-z,relro -o 
guile-readline.la -rpath /usr/lib/x86_64-linux-gnu/guile/2.2/extensions 
readline.lo -L/usr/lib/x86_64-linux-gnu -lreadline -lncurses 
../libguile/libguile-2.2.la ../lib/libgnu.la -lcrypt -lm -inst-prefix-dir 
/<>/guile-2.2-2.2.4+1/debian/tmp)
libtool: relink: gcc -std=gnu11 -shared  -fPIC -DPIC  .libs/readline.o  
-Wl,--whole-archive ../lib/.libs/libgnu.a -Wl,--no-whole-archive  
-L/usr/lib/x86_64-linux-gnu -lreadline -lncurses 
-L/<>/guile-2.2-2.2.4+1/debian/tmp/usr/lib/x86_64-linux-gnu 
-lguile-2.2 -lunistring -lcrypt -lm  -g -O2 -fstack-protector-strong -Wl,-z 
-Wl,relro   -pthread -Wl,-soname -Wl,guile-readline.so.0 -o 
.libs/guile-readline.so.0.0.0
libtool: install: install -p .libs/guile-readline.so.0.0.0T 
/<>/guile-2.2-2.2.4+1/debian/tmp/usr/lib/x86_64-linux-gnu/guile/2.2/extensions/guile-readline.so.0.0.0
libtool: install: (cd 
/<>/guile-2.2-2.2.4+1/debian/tmp/usr/lib/x86_64-linux-gnu/guile/2.2/extensions
 && { ln -s -f guile-readline.so.0.0.0 guile-readline.so.0 || { rm -f 
guile-readline.so.0 && ln -s guile-readline.so.0.0.0 guile-readline.so.0; }; })
libtool: install: (cd 
/<>/guile-2.2-2.2.4+1/debian/tmp/usr/lib/x86_64-linux-gnu/guile/2.2/extensions
 && { ln -s -f guile-readline.so.0.0.0 guile-readline.so || { rm -f 
guile-readline.so && ln -s guile-readline.so.0.0.0 guile-readline.so; }; })
libtool: install: install -p .libs/guile-readline.lai 
/<>/guile-2.2-2.2.4+1/debian/tmp/usr/lib/x86_64-linux-gnu/guile/2.2/extensions/guile-readline.la
libtool: install: install -p .libs/guile-readline.a 
/<>/guile-2.2-2.2.4+1/debian/tmp/usr/lib/x86_64-linux-gnu/guile/2.2/extensions/guile-readline.a
libtool: install: chmod 644 
/<>/guile-2.2-2.2.4+1/debian/tmp/usr/lib/x86_64-linux-gnu/guile/2.2/extensions/guile-readline.a
libtool: install: ranlib 
/<>/guile-2.2-2.2.4+1/debian/tmp/usr/lib/x86_64-linux-gnu/guile/2.2/extensions/guile-readline.a
libtool: warning: remember to run 'libtool --finish 
/usr/lib/x86_64-linux-gnu/guile/2.2/extensions'
 /bin/mkdir -p 
'/<>/guile-2.2-2.2.4+1/debian/tmp/usr/include/guile/2.2'
 install -p -m 644 readline.h 
'/<>/guile-2.2-2.2.4+1/debian/tmp/usr/include/guile/2.2'
 /bin/mkdir -p '/<>/guile-2.2-2.2.4+1/debian/tmp/usr/share/guile/2.2/'
 /bin/mkdir -p 
'/<>/guile-2.2-2.2.4+1/debian/tmp/usr/share/guile/2.2//ice-9'
 install -p -m 644  ice-9/readline.scm 
'/<>/guile-2.2-2.2.4+1/debian/tmp/usr/share/guile/2.2//ice-9'
 /bin/mkdir -p 

Bug#944820: marked as done (SimpleSAMLphp fails when consuming assertion)

[Debian Bug Tracking System]

Your message dated Wed, 08 Jan 2020 21:47:13 +
with message-id 
and subject line Bug#944820: fixed in simplesamlphp 1.16.3-1+deb10u2
has caused the Debian Bug report #944820,
regarding SimpleSAMLphp fails when consuming assertion
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.)


-- 
944820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: simplesamlphp
Version: 1.16.3-1+deb10u1

When SimpleSAMLphp consumes an assertion, it will fail and log the
following:

> PHP Warning:  preg_replace(): Compilation failed: invalid range in character 
> class at offset 8 in 
> /usr/share/simplesamlphp/vendor/robrichards/xmlseclibs/src/Utils/XPath.php on 
> line 42
> PHP Warning:  DOMXPath::query(): Invalid expression in 
> /usr/share/simplesamlphp/vendor/robrichards/xmlseclibs/src/XMLSecurityDSig.php
>  on line 509
> PHP Warning:  DOMXPath::query(): Invalid expression in 
> /usr/share/simplesamlphp/vendor/robrichards/xmlseclibs/src/XMLSecurityDSig.php
>  on line 509

The problem is that a year-old patch has not yet made it into the Debian
package.  Applying this patch manually solves the problem:

https://github.com/robrichards/xmlseclibs/commit/7b35c14f3659eefa2ac194965aee541d2b2400ef

I suggest applying this patch in the package so that I don't have to
maintain this patch locally on my system.

I am using Debian GNU/Linux 10.1, php 7.3


-- 
Vennlig hilsen/Best regardsJørn Åne de Jong
Systemutvikler/Systems Developer
Uninett AS
jorn.dej...@uninett.no
+47 95 36 10 17
www.uninett.no
Abonner på vårt nyhetsbrev www.uninett.no/nyhetsbrev




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Source: simplesamlphp
Source-Version: 1.16.3-1+deb10u2

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

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

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

Debian distribution maintenance software
pp.
Thijs Kinkhorst  (supplier of updated simplesamlphp 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, 16 Dec 2019 14:15:00 +0100
Source: simplesamlphp
Binary: simplesamlphp
Architecture: source all
Version: 1.16.3-1+deb10u2
Distribution: buster
Urgency: medium
Maintainer: Thijs Kinkhorst 
Changed-By: Thijs Kinkhorst 
Description:
 simplesamlphp - Authentication and federation application supporting several 
prot
Closes: 944820
Changes:
 simplesamlphp (1.16.3-1+deb10u2) buster; urgency=medium
 .
   * Fix incompatibility with PHP 7.3 (closes: #944820).
Checksums-Sha1:
 b464d63a3611e8be8cde6ef58d51e58da53cf49d 1592 
simplesamlphp_1.16.3-1+deb10u2.dsc
 064dd622061b517c6f040044d8e1f384b7398b1b 2309260 
simplesamlphp_1.16.3-1+deb10u2.debian.tar.xz
 1a7ad9ad8d62d6dcfb25173cd2a32c3e932320b3 1909292 
simplesamlphp_1.16.3-1+deb10u2_all.deb
 5a90c3653a7c460b5e9ee3047afd930853aec23f 6241 
simplesamlphp_1.16.3-1+deb10u2_amd64.buildinfo
Checksums-Sha256:
 40e65c76f2da100e3fd4944badaa64381b0a9de5506404f137ecea3079aa1d5f 1592 
simplesamlphp_1.16.3-1+deb10u2.dsc
 eb221688ffea6ec4be9e03ce9af152ed1f533eaf87a19e356d71213e1152e039 2309260 
simplesamlphp_1.16.3-1+deb10u2.debian.tar.xz
 67981c2cc315ef607fc471a58d90aa511da6d9ec0d7e1a689306f64bcbb46813 1909292 
simplesamlphp_1.16.3-1+deb10u2_all.deb
 e3910bbe66cfc66a236c250d534da7829b662628889b96c207c2254389a8c7f5 6241 
simplesamlphp_1.16.3-1+deb10u2_amd64.buildinfo
Files:
 c421fae0d73a841b162a530c4b49fa7d 1592 web optional 
simplesamlphp_1.16.3-1+deb10u2.dsc
 0ed29f413c49e34c77bde27a54829398 2309260 web optional 
simplesamlphp_1.16.3-1+deb10u2.debian.tar.xz
 58b9eec7c271eb67ce3a96b34578c145 1909292 web optional 
simplesamlphp_1.16.3-1+deb10u2_all.deb
 b24c542391764732355afeb7bd897115 6241 web optional 
simplesamlphp_1.16.3-1+deb10u2_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQFFBAEBCAAvFiEEeANVtepr/II1qZxLVvYaeUAdrAQFAl4LJ1YRHHRoaWpzQGRl
Ymlhbi5vcmcACgkQVvYaeUAdrARjVAf9ERNYAzH4ahOJHWNPQaqGuA5nc5DODrS/
MrPXRFK36EZao/iCxLzNkA5CGhAMI38OwiPIO87c0UqdPiruCQN2ih9kKbinEAZx
yCFnyP/aaEfY0hc5BjfE1k9NCqDrkTNvhqqiNC6J3pI4FbxwZ+3KWLCgVOJCgBax

Bug#945864: marked as done (unhide[208429]: segfault at 7ffd06cfec58 ip 000055c15aa077d3 sp 00007ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000])

[Debian Bug Tracking System]

Your message dated Wed, 08 Jan 2020 21:47:14 +
with message-id 
and subject line Bug#945864: fixed in unhide 20130526-3+deb10u1
has caused the Debian Bug report #945864,
regarding unhide[208429]: segfault at 7ffd06cfec58 ip 55c15aa077d3 sp 
7ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000]
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.)


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



Since 1-3 weeks unhide segfaults every time:

Nov 30 01:39:48 heisenberg kernel: unhide[208429]: segfault at 7ffd06cfec58 ip 
55c15aa077d3 sp 7ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000]
Nov 30 01:39:48 heisenberg kernel: Code: 00 48 89 45 c8 31 c0 48 63 05 5d 98 00 
00 48 8d 04 85 0f 00 00 00 48 83 e0 f0 48 29 c4 48 89 65 98 48 29 c4 31 c0 48 
89 65 90  d8 3e 00 00 31 c0 66 0f 1f 44 00 00 48 8b 4d 98 48 8b 55 90 c7


Cheers,
Chris.

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

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

Versions of packages unhide depends on:
ii  libc6  2.29-3

unhide recommends no packages.

Versions of packages unhide suggests:
ii  rkhunter  1.4.6-7

-- no debconf information
--- End Message ---
--- Begin Message ---
Source: unhide
Source-Version: 20130526-3+deb10u1

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

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Tue, 17 Dec 2019 09:08:39 -0300
Source: unhide
Architecture: source
Version: 20130526-3+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian Security Tools 
Changed-By: Thiago Andrade Marques 
Closes: 945864
Changes:
 unhide (20130526-3+deb10u1) buster; urgency=medium
 .
   * Team Upload.
   * debian/patch/allocate-pid-arrays-from-heap.patch: Added to fix a stack
 exhausting. Thanks to Bernhard Übelacker .
 (Closes: #945864)
Checksums-Sha1:
 345f7ede45a82543e11d58fc0c5e6cf22b0631e7 1914 unhide_20130526-3+deb10u1.dsc
 c7fe2a47ccaa50a2b5410f97a99a5bb3eb64342b 7152 
unhide_20130526-3+deb10u1.debian.tar.xz
 7a712c5f59a563994e9ba4e2077a72ff146ae0ec 5133 
unhide_20130526-3+deb10u1_source.buildinfo
Checksums-Sha256:
 46d1507d03913d75ac58fbb760cc404da37826a70c2732a3d159f8986243de68 1914 
unhide_20130526-3+deb10u1.dsc
 de605f24d5938dc161405638f4c112be1bce37b627692029b2572c737504a624 7152 
unhide_20130526-3+deb10u1.debian.tar.xz
 058df3107feb8300e04888c5f8abe2f6a703cf85e0f279f2157b5d0c3cc213e8 5133 
unhide_20130526-3+deb10u1_source.buildinfo
Files:
 e51f95db212ba63088ac530f270cb998 1914 admin optional 
unhide_20130526-3+deb10u1.dsc
 05804e5d409b62df8f8138a94c731be7 7152 admin optional 
unhide_20130526-3+deb10u1.debian.tar.xz
 349e080a35674d5f4e92da260f227212 5133 admin optional 
unhide_20130526-3+deb10u1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEENX3LDuyVoBrrofDS3mO5xwTr6e8FAl4KugIACgkQ3mO5xwTr
6e/xpxAAqtlJwgHyhgG5O5XnYUia7l30dww5OngqfEldc0/T4RK9DcasbfUqikZK
deNTBimxx7hFYp5q5SotPX3a/fy9Q10oCYheWmace7nXjJ/rZHJWYHUt1l/U1sSm
yhOx6LTZ882IY26wRYxLEASCRvG7NQfACSvRH7JY7F00oI/anU+XTozIOyNu6LRv
6tiaxze3P7KNv7zsve6XcR0FifdMArMrCR+ENUJMetJHoDorn20/UPSOwsCSD8ox
+/1lnSv+eXIFCKVLXoyNZQTFkO7irXh+2iUkf11ABw0xrNnhNiFlFhChPrwE6oi9
J/NYhGc3dWi8k+5FJP38p9aqGZbSyQ522g2Qr4GLnOFsfCsWFXl/ERJzNZXu39Yj
UI4GpDdtr3jBkh27AbRwa34uar/vr8+WIWs5qRhYu5TU9WaFGirIoVLNq+sO3eJn
Twi2PacUx00hX+9UTr/BV6JnskOMrSYklZ8Bko6OxN432tbLgoRPBx2Uud7scU7x
ATkBADNg1XvLRVZyIrgFJLqGjJVRkMtjSSZ+VyGIa+p3P6DBWIh2PWpuM+SVdJmf

Processed: your mail

[Debian Bug Tracking System]

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

> tags 948426 + pending
Bug #948426 [src:python-whoosh] python-whoosh ftbfs in unstable
Added tag(s) pending.
> thanks
Stopping processing here.

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

Processed: Bug#948417 marked as pending in python-astor

[Debian Bug Tracking System]

Processing control commands:

> tag -1 pending
Bug #948417 [src:python-astor] python-astor ftbfs with Python 3.8
Added tag(s) pending.

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

Bug#948417: marked as pending in python-astor

[Tianon Gravi]

Control: tag -1 pending

Hello,

Bug #948417 in python-astor 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/python-astor/commit/77a011ab0cdb658c6da95f15fa41e962c1da73be


Update to 0.8.1 upstream release

- https://github.com/berkerpeksag/astor/pull/163 (Closes: #948417)


(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/948417

Bug#947679: qsynth: FTBFS on s390x: lrelease error: Parse error ... qsynth_sr.ts:734:29: Premature end of document.

[Lisandro Damián Nicanor Pérez Meyer]

Hi!

El mié., 8 ene. 2020 18:08, Sebastian Ramacher 
escribió:

> Control: tags -1 + help moreinfo
>
> On 2019-12-28 22:12:34, Lisandro Damián Nicanor Pérez Meyer wrote:
> > Source: qsynth
> > Version: 0.6.0-1
> > Severity: serious
> > Justification: FTBFS on s390x
> >
> > Hi! Your package failed to build from source on s390x with the following
> error:
> >
> > lrelease error: Parse error at src/translations/qsynth_sr.ts:734:29:
> Premature end of document.
> > make[1]: *** [Makefile:102: src/translations/qsynth_sr.qm] Error 1
> >
> > The full build log can be found at:
> >
> >
> https://buildd.debian.org/status/fetch.php?pkg=qsynth=s390x=0.6.0-1=1576518180=0
> >
> > It is posible that the error might be solved with a give back.
>
> It seems to fail consistently on the buildds, but I cannot reproduce the
> issue on zelenka. Could that be an issue in lrelease?


I'm not discarding it, but if it where all the packages calling lrelease on
s390x would be FTBFS. Except this specific ts file has something weird...
But it's just an xml :-/

Processed: Re: Bug#947679: qsynth: FTBFS on s390x: lrelease error: Parse error ... qsynth_sr.ts:734:29: Premature end of document.

[Debian Bug Tracking System]

Processing control commands:

> tags -1 + help moreinfo
Bug #947679 [src:qsynth] qsynth: FTBFS on s390x: lrelease error: Parse error 
... qsynth_sr.ts:734:29: Premature end of document.
Added tag(s) moreinfo and help.

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

Bug#947679: qsynth: FTBFS on s390x: lrelease error: Parse error ... qsynth_sr.ts:734:29: Premature end of document.

[Sebastian Ramacher]

Control: tags -1 + help moreinfo

On 2019-12-28 22:12:34, Lisandro Damián Nicanor Pérez Meyer wrote:
> Source: qsynth
> Version: 0.6.0-1
> Severity: serious
> Justification: FTBFS on s390x
> 
> Hi! Your package failed to build from source on s390x with the following 
> error:
> 
> lrelease error: Parse error at src/translations/qsynth_sr.ts:734:29: 
> Premature end of document.
> make[1]: *** [Makefile:102: src/translations/qsynth_sr.qm] Error 1
> 
> The full build log can be found at:
> 
> https://buildd.debian.org/status/fetch.php?pkg=qsynth=s390x=0.6.0-1=1576518180=0
> 
> It is posible that the error might be solved with a give back.

It seems to fail consistently on the buildds, but I cannot reproduce the
issue on zelenka. Could that be an issue in lrelease?

Cheers

> 
> Kinds regards, Lisandro.
> 
> -- System Information:
> Debian Release: bullseye/sid
>   APT prefers unstable
>   APT policy: (990, 'unstable'), (500, 'unstable-debug'), (500, 
> 'testing-debug'), (500, 'buildd-unstable'), (500, 'testing'), (1, 
> 'experimental-debug'), (1, 'experimental')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386, arm64, armhf
> 
> Kernel: Linux 5.3.0-3-amd64 (SMP w/2 CPU cores)
> Kernel taint flags: TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
> Locale: LANG=es_AR.UTF-8, LC_CTYPE=es_AR.UTF-8 (charmap=UTF-8), 
> LANGUAGE=es_AR:es (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> Init: systemd (via /run/systemd/system)
> LSM: AppArmor: enabled
> 

-- 
Sebastian Ramacher


signature.asc
Description: PGP signature

Bug#948460: xserver-xorg-video-nvidia-legacy-340xx: Xorg won't start with xserver-xorg-video-nvidia-legacy-340xx on testing/Bullseye

[Alexis]

Package: xserver-xorg-video-nvidia-legacy-340xx
Version: 340.108-2
Severity: grave
Justification: renders package unusable

Dear Maintainer,

first things first, happy new year to all !

I've been using Debian since Potato and I've always found it stable so far.
On 5th january I did a fresh install of Bullseye (testing) from a USB key.

New CPU (Ryzen 2600x) but old graphics card (Nvidia GT240) having working well
for my needs so far.
I started to use the "nouveau" xorg driver but it turned out to be seriously
unstable making the system crash every 10 min or saw. Sometimes faster when
watching a video (30 seconds) sometime more (2h).
So I installed packages to use the nvidia proprietary drivers (xserver-xorg-
video-nvidia-legacy-340xx and related packages).
I took care to remove the nouveau driver (kernel and xorg drivers).
But the system ended up with a back screen, no keyboard no mouse reponse.
Neither the Ctrl-Alt-F1 worked.
So I went to single user mode to manually start the X server.
Extract from the Xorg log :
==
[   813.608] (II) LoadModule: "nouveau"
[   813.608] (WW) Warning, couldn't open module nouveau
[   813.608] (EE) Failed to load module "nouveau" (module does not exist, 0)
[   813.608] (II) LoadModule: "nv"
[   813.608] (WW) Warning, couldn't open module nv
[   813.608] (EE) Failed to load module "nv" (module does not exist, 0)
[   813.608] (II) LoadModule: "modesetting"
[   813.608] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so
[   813.608] (II) Module modesetting: vendor="X.Org Foundation"
[   813.608]compiled for 1.20.6, module version = 1.20.6
[   813.608]Module class: X.Org Video Driver
[   813.608]ABI class: X.Org Video Driver, version 24.0
[   813.608] (II) LoadModule: "fbdev"
[   813.608] (WW) Warning, couldn't open module fbdev
[   813.608] (EE) Failed to load module "fbdev" (module does not exist, 0)
[   813.608] (II) LoadModule: "vesa"
[   813.608] (WW) Warning, couldn't open module vesa
[   813.608] (EE) Failed to load module "vesa" (module does not exist, 0)
[   813.608] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[   813.608] (WW) Falling back to old probe method for modesetting
[   813.608] (EE) Screen 0 deleted because of no matching config section.
[   813.608] (II) UnloadModule: "modesetting"
[   813.608] (EE) Device(s) detected, but none match those in the config file.
[   813.608] (EE)
Fatal server error:
[   813.608] (EE) no screens found(EE)
[   813.608] (EE)
Please consult the The X.Org Foundation support
 at http://wiki.x.org
 for help.
[   813.608] (EE) Please also check the log file at "/var/log/Xorg.1.log" for
additional information.
[   813.608] (EE)
[   813.610] (EE) Server terminated with error (1). Closing log file.
==
nvidia driver wasn't found. So I manually copied nvidia_drv.so in
/usr/lib/xorg/modules/drivers to restart Xorg via startx. But new black screen
and I couldn't find error message neither with journalctl nor in
/var/log/Xorg.0.log.
I felt kind of desperate.
Then I found bug 948195 and the following message :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948195#15
I modified the script to use version 340.108-2 instead of the 340.108-1 from
testing.
But again black screen. I tried in single user mode to manually startx and
again the same error as above.
I manually modified xorg.conf to load the nvidia driver AND I manually copied
the nvidia_drv.so in /usr/lib/xorg/modules/drivers.
Since these modifications it's been stable for the last 24h.
The actions (watching video) that lead to the crash before didn't make the
system crash with nvidia driver.
Hope this help others.



-- Package-specific info:
uname -a:
Linux akatendai 5.3.0-3-amd64 #1 SMP Debian 5.3.15-1 (2019-12-07) x86_64 
GNU/Linux

/proc/version:
Linux version 5.3.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 
20191130 (Debian 9.2.1-21)) #1 SMP Debian 5.3.15-1 (2019-12-07)

/proc/driver/nvidia/version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.108  Wed Dec 11 11:06:58 
PST 2019
GCC version:  gcc version 9.2.1 20200104 (Debian 9.2.1-22) 

lspci 'display controller [030?]':
06:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT215 [GeForce GT 
240] [10de:0ca3] (rev a2) (prog-if 00 [VGA controller])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_legacy_340xx

dmesg:

Device node permissions:
crw-rw+ 1 root video 226,   0 Jan  7 23:17 /dev/dri/card0
crw-rw-rw-  1 root root  195,   0 Jan  7 23:21 /dev/nvidia0
crw-rw-rw-  1 root root  195, 255 Jan  7 23:21 /dev/nvidiactl

/dev/dri/by-path:
total 0
lrwxrwxrwx 1 root root 8 Jan  7 23:17 pci-:06:00.0-card -> ../card0
video:x:44:alexis

OpenGL and NVIDIA library files installed:
-rw-r--r-- 1 root 

Bug#948459: sympy breaks yt autopkgtest: FAIL: Create units with strings and check attributes.

[Paul Gevers]

Source: sympy, yt
Control: found -1 sympy/1.5-1
Control: found -1 yt/3.5.1-2
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of sympy the autopkgtest of yt fails in testing
when that autopkgtest is run with the binary packages of sympy from
unstable. It passes when run with only packages from testing. In tabular
form:
   passfail
sympy  from testing1.5-1
yt from testing3.5.1-2
all others from testingfrom testing

I copied some of the output at the bottom of this report. @yt
maintainers, you want to look at the messages one sees after installing
python3-yt.

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/y/yt/3915709/log.gz

==
FAIL: Create units with strings and check attributes.
--
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/nose/case.py", line 197, in runTest
self.test(*self.arg)
  File "/usr/lib/python3/dist-packages/yt/units/tests/test_units.py",
line 114, in test_create_from_string
assert_true(u3.dimensions == magnetic_field)
AssertionError: False is not true

--
Ran 1387 tests in 781.245s

FAILED (failures=1)



signature.asc
Description: OpenPGP digital signature

Processed: sympy breaks yt autopkgtest: FAIL: Create units with strings and check attributes.

[Debian Bug Tracking System]

Processing control commands:

> found -1 sympy/1.5-1
Bug #948459 [src:sympy, src:yt] sympy breaks yt autopkgtest: FAIL: Create units 
with strings and check attributes.
Marked as found in versions sympy/1.5-1.
> found -1 yt/3.5.1-2
Bug #948459 [src:sympy, src:yt] sympy breaks yt autopkgtest: FAIL: Create units 
with strings and check attributes.
Marked as found in versions yt/3.5.1-2.

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

Processed: sympy breaks octave-symbolic autopkgtest: unsupported operand type(s) for +: 'Singleton' and 'FiniteSet'

[Debian Bug Tracking System]

Processing control commands:

> found -1 sympy/1.5-1
Bug #948458 [src:sympy, src:octave-symbolic] sympy breaks octave-symbolic 
autopkgtest: unsupported operand type(s) for +: 'Singleton' and 'FiniteSet'
Marked as found in versions sympy/1.5-1.
> found -1 octave-symbolic/2.8.0-1
Bug #948458 [src:sympy, src:octave-symbolic] sympy breaks octave-symbolic 
autopkgtest: unsupported operand type(s) for +: 'Singleton' and 'FiniteSet'
Marked as found in versions octave-symbolic/2.8.0-1.

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

Bug#948458: sympy breaks octave-symbolic autopkgtest: unsupported operand type(s) for +: 'Singleton' and 'FiniteSet'

[Paul Gevers]

Source: sympy, octave-symbolic
Control: found -1 sympy/1.5-1
Control: found -1 octave-symbolic/2.8.0-1
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks needs-update

Dear maintainers,

With a recent upload of sympy the autopkgtest of octave-symbolic fails
in testing when that autopkgtest is run with the binary packages of
sympy from unstable. It passes when run with only packages from testing.
In tabular form:
   passfail
sympy  from testing1.5-1
octave-symbolicfrom testing2.8.0-1
all others from testingfrom testing

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

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

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

Paul

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

https://ci.debian.net/data/autopkgtest/testing/amd64/o/octave-symbolic/3915708/log.gz

* test
 e = finiteset();
 s = finiteset(sym(1));
 s2 = e + s;
 assert (isequal (s, s2))
! test failed
Python exception: TypeError: unsupported operand type(s) for +:
'Singleton' and 'FiniteSet'
occurred at line 8 of the Python code block:
return x + y
3 tests, 2 passed, 0 known failure, 0 skipped

[...]

Some tests failed.  Giving up...
Summary: 2300 tests, 2268 passed, 25 known failures, 0 skipped



signature.asc
Description: OpenPGP digital signature

Bug#944742: fixed in assimp 5.0.0~ds2-4

[Debian/GNU]

(resending as a signed-mail, and with the TS included)

On 05.01.20 10:27, Jochen Sprickerhof wrote:
> I would propose to add the workaround for s390x and wait for new test
> results for armhf resp. ignore them for ppc64el, as they where not
> reproducible. If no one disagrees I will do a NMU and close this bug
> next Sunday.

ACK.

i would welcome it, if you would
- push your changes to salsa directly
- use "dgit push" for uploading to the archive

sdft
IOhannes



signature.asc
Description: OpenPGP digital signature

Processed: Re: python3-ownet: Python2-only code shipped in Python3 module

[Debian Bug Tracking System]

Processing control commands:

> reassign -1 src:owfs 3.2p3+dfsg1-2
Bug #943612 {Done: Vincent Danjean } [python3-ownet] 
python3-ownet: Python2-only code shipped in Python3 module
Bug reassigned from package 'python3-ownet' to 'src:owfs'.
No longer marked as found in versions owfs/3.2p3+dfsg1-2.
No longer marked as fixed in versions owfs/3.2p3+dfsg1-5.
Bug #943612 {Done: Vincent Danjean } [src:owfs] 
python3-ownet: Python2-only code shipped in Python3 module
Marked as found in versions owfs/3.2p3+dfsg1-2.
> fixed -1 3.2p3+dfsg1-5
Bug #943612 {Done: Vincent Danjean } [src:owfs] 
python3-ownet: Python2-only code shipped in Python3 module
Marked as fixed in versions owfs/3.2p3+dfsg1-5.
> tag -1 pending
Bug #943612 {Done: Vincent Danjean } [src:owfs] 
python3-ownet: Python2-only code shipped in Python3 module
Added tag(s) pending.

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

Bug#947463: bio-tradis: autopkgtest regression: Use of uninitialized value $total_uis (and lots of mv: cannot stat '/tmp/aut.....)

[Paul Gevers]

Hi Micheal,

On Fri, 3 Jan 2020 09:31:43 +0100 Michael Crusoe
 wrote:
> > With a recent upload of bio-tradis the autopkgtest of bio-tradis fails
> > in testing when that autopkgtest is run with the binary packages of
> > bio-tradis from unstable. It passes when run with only packages from
> > testing.
> 
> Why are we mixing testing scripts and binaries?

We're not, at least not most of the time. What I meant was that we
tested the autopkgtest of src:bio-tradis from unstable with the
src:bio-tradis binaries from unstable in testing. The idea is to see
what happens if the package in unstable would migrate.

Paul



signature.asc
Description: OpenPGP digital signature

Processed: tagging 948452, severity of 948452 is grave

[Debian Bug Tracking System]

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

> tags 948452 + security
Bug #948452 [firefox] firefox: Please update to 72.0.1 (and firefox-esr to 
68.4.1) because of CVE-2019-17026
Added tag(s) security.
> severity 948452 grave
Bug #948452 [firefox] firefox: Please update to 72.0.1 (and firefox-esr to 
68.4.1) because of CVE-2019-17026
Severity set to 'grave' from 'important'
> thanks
Stopping processing here.

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

Bug#943612: python3-ownet: Python2-only code shipped in Python3 module

[Andreas Beckmann]

Followup-For: Bug #943612
Control: reassign -1 src:owfs 3.2p3+dfsg1-2
Control: fixed -1 3.2p3+dfsg1-5
Control: tag -1 pending

(Reassigning to the source package since the BTS does not understand that a
removed python3-ownet is a fixed python3-ownet.)

I've prepared a buster-pu request to drop the broken python3 support
from buster, too: https://bugs.debian.org/948381


Andreas

Processed: Re: xserver-xorg-video-radeon 19.1 (ppc64) crash at startup: undefined symbol: exaGetPixmapDriverPrivate

[Debian Bug Tracking System]

Processing control commands:

> severity -1 important
Bug #943664 [xserver-xorg-video-radeon] xserver-xorg-video-radeon 19.1 (ppc64) 
crash at startup: undefined symbol: exaGetPixmapDriverPrivate
Severity set to 'important' from 'grave'

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

Bug#942895: Fix buster vulnerability

[Bharath Muraleedharan]

Please fix this vulnerability in buster.
https://security-tracker.debian.org/tracker/CVE-2019-18224

Thanks and Regards,
Bharath



The information contained in this e-mail message and any attachments is 
confidential. If the reader of this message is not the intended recipient or an 
agent responsible for delivering it to the intended recipient, you are hereby 
notified that any review, dissemination, distribution or copying of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify the sender immediately by replying to this e-mail and 
delete the message and any attachments from your computer.

Bug#943664: xserver-xorg-video-radeon 19.1 (ppc64) crash at startup: undefined symbol: exaGetPixmapDriverPrivate

[Andreas Beckmann]

Control: severity -1 important

On Sun, 27 Oct 2019 16:59:23 +0100 "Ralf P."  wrote:
> Package: xserver-xorg-video-radeon
> Version: 1:19.0.1-1
> Severity: grave
> Justification: renders package unusable
> 
> Dear Maintainer,
> 
>on the ppc64 architecture the package 

Downgrading the severity for a Debian ports architecture.


Andreas

Bug#948455: ruby-byebug breaks ruby-pry-byebug autopkgtest: missing versioned Breaks

[Paul Gevers]

Source: ruby-byebug
Version: 11.0.1-4
Severity: serious
Tags: sid bullseye
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: breaks

Dear maintainers,

With a recent upload of ruby-byebug the autopkgtest of ruby-pry-byebug
fails in testing when that autopkgtest is run with the binary packages
of ruby-byebug from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
ruby-byebugfrom testing11.0.1-4
ruby-pry-byebugfrom testing3.6.0-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. The test is
fine in unstable, so I think it means that ruby-byebug should add a
versioned Breaks on ruby-pry-byebug.

Currently this regression is blocking the migration of ruby-byebug to
testing [1].

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

Paul

[1] https://qa.debian.org/excuses.php?package=ruby-byebug

https://ci.debian.net/data/autopkgtest/testing/amd64/r/ruby-pry-byebug/3911213/log.gz

autopkgtest [07:13:07]: test gem2deb-test-runner: [---

┌──┐
│ Checking Rubygems dependency resolution on ruby2.5
  │
└──┘

GEM_PATH= ruby2.5 -e gem\ \"pry-byebug\"
/usr/lib/ruby/2.5.0/rubygems/dependency.rb:312:in `to_specs': Could not
find 'byebug' (~> 10.0) - did find: [byebug-11.0.1]
(Gem::MissingSpecVersionError)



signature.asc
Description: OpenPGP digital signature

Bug#948454: python-numpy: autopkgtest regression: tests/capi: 89: Syntax error: word unexpected (expecting ")")

[Paul Gevers]

Source: python-numpy
Version: 1:1.16.5-2
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a (not so) recent upload of python-numpy the autopkgtest of
python-numpy fails in testing when that autopkgtest is run with the
binary packages of python-numpy from unstable. It passes when run with
only packages from testing. In tabular form:
   passfail
python-numpy   from testing1:1.16.5-2
all others from testingfrom testing

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

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

[1] https://qa.debian.org/excuses.php?package=python-numpy

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-numpy/3915478/log.gz

autopkgtest [07:15:08]: test f2py: [---
/tmp/autopkgtest-lxc.jhh9qajz/downtmp/build.odB/src/debian/tests/f2py:
24: Syntax error: Unterminated quoted string
autopkgtest [07:15:08]: test f2py: ---]


[...]

autopkgtest [07:16:39]: test capi: [---
/tmp/autopkgtest-lxc.jhh9qajz/downtmp/build.odB/src/debian/tests/capi:
89: Syntax error: word unexpected (expecting ")")
autopkgtest [07:16:40]: test capi: ---]



signature.asc
Description: OpenPGP digital signature

Bug#948453: python-dmsh: autopkgtest regression: No module named 'perfplot'

[Paul Gevers]

Source: python-dmsh
Version: 0.1.6-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression

Dear maintainers,

With a recent upload of python-dmsh the autopkgtest of python-dmsh fails
in testing when that autopkgtest is run with the binary packages of
python-dmsh from unstable. It passes when run with only packages from
testing. In tabular form:
   passfail
python-dmshfrom testing0.1.6-1
all others from testingfrom testing

I copied some of the output at the bottom of this report. Are you not
missing a (test) dependencies?

Currently this regression is blocking the migration to testing [1]. Can
you please investigate the situation and fix it?

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

Paul

[1] https://qa.debian.org/excuses.php?package=python-dmsh

https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dmsh/3915475/log.gz

autopkgtest [07:11:09]: test test-dmsh: [---

running test_circle.py
Skipping save mesh to file (circle.png) since a module is missing:
No module named 'meshplex'

running test_closed_path.py

running test_difference.py
Skipping save mesh to file (difference.png) since a module is missing:
No module named 'meshplex'

running test_ellipse.py
Skipping save mesh to file (ellipse.png) since a module is missing:
No module named 'meshplex'

running test_halfspace.py
Skipping save mesh to file (halfspace.png) since a module is missing:
No module named 'meshplex'

running test_intersection.py
Skipping save mesh to file (intersection.png) since a module is missing:
No module named 'meshplex'

running test_intersection_three_circles.py
Skipping save mesh to file (intersection_three_circles.png) since a
module is missing:
No module named 'meshplex'

running test_large.py

running test_pacman.py
Skipping save mesh to file (pacman.png) since a module is missing:
No module named 'meshplex'

running test_path.py

running test_polygon.py
Skipping save mesh to file (polygon.png) since a module is missing:
No module named 'meshplex'

running test_rectangle.py
Skipping save mesh to file (rectangle.png) since a module is missing:
No module named 'meshplex'

running test_rectangle_hole.py

running test_refinement_point_line.py
Skipping save mesh to file (refinement_line.png) since a module is missing:
No module named 'meshplex'

running test_rotation.py
Skipping save mesh to file (rotation.png) since a module is missing:
No module named 'meshplex'

running test_scaling.py
Skipping save mesh to file (scaling.png) since a module is missing:
No module named 'meshplex'

running test_show_level_set.py

running test_speed.py
Traceback (most recent call last):
  File "test_speed.py", line 4, in 
import perfplot
ModuleNotFoundError: No module named 'perfplot'

running test_square_hole.py

running test_square_hole_refined.py
Skipping save mesh to file (square_hole_refined.png) since a module is
missing:
No module named 'meshplex'

running test_stretch.py
Skipping save mesh to file (stretch.png) since a module is missing:
No module named 'meshplex'

running test_translation.py

running test_union.py
Skipping save mesh to file (union.png) since a module is missing:
No module named 'meshplex'

running test_union_rectangles.py
Skipping save mesh to file (union_rectangles.png) since a module is missing:
No module named 'meshplex'

running test_union_three_circles.py
Traceback (most recent call last):
  File "test_union_three_circles.py", line 24, in 
X, cells = test_union(show=False)
  File "test_union_three_circles.py", line 16, in test_union
X, cells = dmsh.generate(geo, 0.2, show=show, tol=1.0e-10)
  File "/usr/lib/python3/dist-packages/dmsh/main.py", line 163, in generate
pts[is_outside] = geo.boundary_step(pts[is_outside].T).T
  File "/usr/lib/python3/dist-packages/dmsh/geometry/union.py", line 63,
in boundary_step
out[:, j] = geo.boundary_step(out[:, j])
IndexError: boolean index did not match indexed array along dimension 1;
dimension is 48 but corresponding boolean dimension is 46
autopkgtest [07:11:55]: test test-dmsh: ---]



signature.asc
Description: OpenPGP digital signature

Bug#846695: kadu-mime-tex: FTBFS: mime_tex_plugin.h:12: Error: Undefined interface

[Paul Gevers]

Hi Patryk,

On Sat, 3 Dec 2016 08:20:22 +0100 Lucas Nussbaum  wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.

This bug hasn't seen any activity since it was filed and your package
hasn't been part of testing for 3 years now. I intent to ask for its
removal unless you show activity (e.g. by replying).

Paul



signature.asc
Description: OpenPGP digital signature

Bug#945820: sysvinit: diff for NMU version 2.96-2.1

[Boyuan Yang]

Control: tags 945820 + patch
Control: tags 945820 + pending

Dear maintainer,

I've prepared an NMU for sysvinit (versioned as 2.96-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.

Regards.

diff -Nru sysvinit-2.96/debian/changelog sysvinit-2.96/debian/changelog
--- sysvinit-2.96/debian/changelog  1969-12-31 19:00:01.0 -0500
+++ sysvinit-2.96/debian/changelog  2020-01-08 14:07:13.0 -0500
@@ -1,3 +1,11 @@
+sysvinit (2.96-2.1) unstable; urgency=medium
+
+  * Non-maintainer upload.
+  * No-change package rebuild to fix timestamp issue as raised by
+buildd. (Closes: #945820)
+
+ -- Boyuan Yang   Wed, 08 Jan 2020 14:07:13 -0500
+
 sysvinit (2.96-2) unstable; urgency=medium
 
   * Incorporate runlevel documentation from Debian Policy.


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

Processed: sysvinit: diff for NMU version 2.96-2.1

[Debian Bug Tracking System]

Processing control commands:

> tags 945820 + patch
Bug #945820 [src:sysvinit] sysvinit_2.96-2_amd64.changes REJECTED
Added tag(s) patch.
> tags 945820 + pending
Bug #945820 [src:sysvinit] sysvinit_2.96-2_amd64.changes REJECTED
Added tag(s) pending.

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

Bug#948078: marked as done (autoconf-archive: please apply patch to fix boost_python library link)

[Debian Bug Tracking System]

Your message dated Wed, 08 Jan 2020 19:19:09 +
with message-id 
and subject line Bug#948078: fixed in autoconf-archive 20190106-2.1
has caused the Debian Bug report #948078,
regarding autoconf-archive: please apply patch to fix boost_python library link
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.)


-- 
948078: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=948078
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: autoconf-archive
Version: 20190106-2
Severity: serious

Hello, esys-particle is FTBFS with python3, because the following:
dh_auto_configure -- $(extra_flags) 
--with-boost-libdir=/usr/lib/$(DEB_HOST_MULTIARCH) 
--with-boost-python='boost_python$(PY3VER)'


tanslates the build into a "boost_python37" link line

checking whether boost_python37 is the correct library... yes

/bin/bash ../libtool  --tag=CXX   --mode=link mpicxx  -Wall -g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security -release 2.3.4  -L/usr/lib/i386-linux-gnu 
-lboost_system -lpython3.7m -Wl,-z,relro -Wl,-z,now -o libFoundation.la -rpath 
/usr/lib/i386-linux-gnu libFoundation_la-console.lo libFoundation_la-Counter.lo 
libFoundation_la-Matrix3.lo libFoundation_la-Quaternion.lo 
libFoundation_la-vec3.lo libFoundation_la-Timer.lo 
libFoundation_la-StringUtil.lo libFoundation_la-realdist.lo 
libFoundation_la-PathSearcher.lo libFoundation_la-Runnable.lo 
libFoundation_la-PathUtil.lo libFoundation_la-Rng.lo 
libFoundation_la-BoundingSphere.lo libFoundation_la-BoundingBox.lo 
libFoundation_la-cube_eq.lo -lboost_filesystem boost_python37 -lpython3.7m 
-lmpi++ -lmpi 

note the missing "-l" on python, while it is there for the filesystem link.

The following patch fixes the issue, and I would like to NMU it ASAP if you 
agree.

Author: Gianfranco Costamagna 
Last-Update: 2020-01-03

--- autoconf-archive-20190106.orig/m4/ax_boost_python.m4
+++ autoconf-archive-20190106/m4/ax_boost_python.m4
@@ -109,7 +109,7 @@ if test "$ac_cv_boost_python" = "yes"; t
 BOOST_PYTHON_MODULE(test) { throw "Boost::Python test."; }]], [])],
 [AS_VAR_SET([ax_Lib], [yes])],
 [AS_VAR_SET([ax_Lib], [no])])])
-AS_VAR_IF([ax_Lib], [yes], [BOOST_PYTHON_LIB=$ax_lib break], [])
+AS_VAR_IF([ax_Lib], [yes], [BOOST_PYTHON_LIB=-l$ax_lib break], [])
 AS_VAR_POPDEF([ax_Lib])dnl
   done
   AC_SUBST(BOOST_PYTHON_LIB)


It looks like just an obvious typo, I'll upstream the fix soon.

G.
Author: Gianfranco Costamagna 
Last-Update: 2020-01-03

--- autoconf-archive-20190106.orig/m4/ax_boost_python.m4
+++ autoconf-archive-20190106/m4/ax_boost_python.m4
@@ -109,7 +109,7 @@ if test "$ac_cv_boost_python" = "yes"; t
 BOOST_PYTHON_MODULE(test) { throw "Boost::Python test."; }]], [])],
 [AS_VAR_SET([ax_Lib], [yes])],
 [AS_VAR_SET([ax_Lib], [no])])])
-AS_VAR_IF([ax_Lib], [yes], [BOOST_PYTHON_LIB=$ax_lib break], [])
+AS_VAR_IF([ax_Lib], [yes], [BOOST_PYTHON_LIB=-l$ax_lib break], [])
 AS_VAR_POPDEF([ax_Lib])dnl
   done
   AC_SUBST(BOOST_PYTHON_LIB)
--- End Message ---
--- Begin Message ---
Source: autoconf-archive
Source-Version: 20190106-2.1

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

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

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

Debian distribution maintenance software
pp.
Gianfranco Costamagna  (supplier of updated 
autoconf-archive package)

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


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Fri, 03 Jan 2020 19:46:30 +0100
Source: autoconf-archive
Binary: autoconf-archive
Architecture: source
Version: 20190106-2.1
Distribution: unstable
Urgency: medium
Maintainer: Bastien Roucariès 
Changed-By: Gianfranco Costamagna 
Description:
 autoconf-archive - Autoconf Macro Archive
Closes: 948078
Changes:
 autoconf-archive (20190106-2.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   * debian/patches/0001-ax_boost_python.m4-fix-missing-l-parameter-
 resulting.patch: Upstream proposed fix for python boost wrong linking
 Closes: #948078
Checksums-Sha1:
 a97c956b4799befef4da7a5085b305e50b721d60 2309 

Bug#948450: djview-plugin might be useless now

[Adrian Bunk]

Package: djview-plugin
Version: 4.11-2
Severity: serious

This package provides an NPAPI plugin.
All major browsers have dropped support for NPAPI.

Bug#948449: garmin-plugin might be useless now

[Adrian Bunk]

Package: garmin-plugin
Version: 0.3.23-5
Severity: serious

This package provides an NPAPI plugin.
All major browsers have dropped support for NPAPI.

Bug#947712: autopkgtest regressions in python-dbusmock with newer network-manager 1.22.2-1

[Michael Biebl]

On Sun, 29 Dec 2019 13:35:35 +0100 Michael Biebl  wrote:
> Package: network-manager, python-dbusmock
> Version: 1.22.2-1
> Severity: serious
> 
> The latest update of network-manager causes an autopkgtest regression in
> python-dbusmock.
> 
> https://ci.debian.net/data/autopkgtest/testing/amd64/p/python-dbusmock/3793816/log.gz
> 
> ==
> FAIL: test_eth_and_wifi (__main__.TestNetworkManager)
> --
> Traceback (most recent call last):
>   File "test_networkmanager.py", line 138, in test_eth_and_wifi
> self.assertRegex(out, r'eth0.*\sdisconnected')
> AssertionError: Regex didn't match: 'eth0.*\\sdisconnected' not found in 
> 'DEVICE  TYPE  STATECONNECTION \neth0ethernet  unknown  --
>  \nwlan0   wifi  unknown  -- \n'
> 
> ==
> FAIL: test_one_eth_connected (__main__.TestNetworkManager)
> --
> Traceback (most recent call last):
>   File "test_networkmanager.py", line 115, in test_one_eth_connected
> self.assertRegex(out, r'eth0.*\sconnected')
> AssertionError: Regex didn't match: 'eth0.*\\sconnected' not found in 'DEVICE 
>  TYPE  STATECONNECTION \neth0ethernet  unknown  -- \n'
> 
> ==
> FAIL: test_one_eth_disconnected (__main__.TestNetworkManager)
> --
> Traceback (most recent call last):
>   File "test_networkmanager.py", line 109, in test_one_eth_disconnected
> self.assertRegex(out, r'eth0.*\sdisconnected')
> AssertionError: Regex didn't match: 'eth0.*\\sdisconnected' not found in 
> 'DEVICE  TYPE  STATECONNECTION \neth0ethernet  unknown  --
>  \n'
> 
> ==
> FAIL: test_one_wifi_with_accesspoints (__main__.TestNetworkManager)
> --
> Traceback (most recent call last):
>   File "test_networkmanager.py", line 155, in test_one_wifi_with_accesspoints
> self.assertRegex(out, r'wlan0.*\sconnected')
> AssertionError: Regex didn't match: 'wlan0.*\\sconnected' not found in 
> 'DEVICE  TYPE  STATECONNECTION \nwlan0   wifi  unknown  -- \n'
> 
> ==
> FAIL: test_remove_connection (__main__.TestNetworkManager)
> --
> Traceback (most recent call last):
>   File "test_networkmanager.py", line 349, in test_remove_connection
> self.assertRegex(self.read_device(), r'wlan0.*\sdisconnected')
> AssertionError: Regex didn't match: 'wlan0.*\\sdisconnected' not found in 
> 'DEVICE  TYPE  STATECONNECTION \nwlan0   wifi  unknown  -- \n'
> 
> ==
> FAIL: test_two_eth (__main__.TestNetworkManager)
> --
> Traceback (most recent call last):
>   File "test_networkmanager.py", line 123, in test_two_eth
> self.assertRegex(out, r'eth0.*\sdisconnected')
> AssertionError: Regex didn't match: 'eth0.*\\sdisconnected' not found in 
> 'DEVICE  TYPE  STATECONNECTION \neth0ethernet  unknown  --
>  \neth1ethernet  unknown  -- \n'
> 
> ==
> FAIL: test_two_wifi_with_accesspoints (__main__.TestNetworkManager)
> --


git bisect finds
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/ce0e898fb476df740a1c337ac9910f504251c466
as the faulty commit:

commit ce0e898fb476df740a1c337ac9910f504251c466 (HEAD, refs/bisect/bad)
Author: Thomas Haller 
Date:   Wed Oct 30 11:42:58 2019 +0100

libnm: refactor caching of D-Bus objects in NMClient


I'm bringing Thomas into the loop here.

The failing NM tests that are run by python-dbusmock are available at
https://salsa.debian.org/python-team/modules/python-dbusmock/blob/master/tests/test_networkmanager.py

Thomas, is that a regression in NetworkManager or does python-dbusmock
need to be updated?

Regards,
Michael



signature.asc
Description: OpenPGP digital signature

Bug#771615: marked as done (python-lamson: non-functioning email address for Maintainer)

[Debian Bug Tracking System]

Your message dated Wed, 8 Jan 2020 19:16:33 +0100
with message-id <42ecf1b7-b69d-6e6b-bf3a-72aed3755...@debian.org>
and subject line Re: python-lamson: non-functioning email address for Maintainer
has caused the Debian Bug report #771615,
regarding python-lamson: non-functioning email address for Maintainer
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.)


-- 
771615: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771615
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: python-lamson
Version: 1.0pre11-1
Severity: important

Dear Maintainer,

The “Maintainer” field in ‘debian/control’ has the value:

David Watson 

Email sent to that address encounters permanent delivery failures,
resulting in unnecessary difficulty reaching the package maintainer.

Please put a functioning email address for the package maintainer in
the Maintainer field, and make a new release of this package to
publish it to automated systems.

-- 
 \“Read not to contradict and confute, nor to believe and take |
  `\  for granted … but to weigh and consider.” —Francis Bacon |
_o__)  |
Ben Finney 


signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.0pre11-1.3

On Mon, 1 Dec 2014 11:59:06 +1100 Ben Finney
 wrote:
> The “Maintainer” field in ‘debian/control’ has the value:
> 
> David Watson 

python-lamson (1.0pre11-1.3) unstable; urgency=medium

  * Non-maintainer upload.
  * Swap the Maintainer and Uploaders addresses (both of David Watson).
Closes: #805610

 -- Mattia Rizzolo   Wed, 20 Jan 2016 19:41:23 +


Andreas--- End Message ---