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

[Debian Bug Tracking System]

Your message dated Wed, 27 Nov 2019 10:51:47 +
with message-id 
and subject line Bug#938230: fixed in python-ttystatus 0.38-3
has caused the Debian Bug report #938230,
regarding python-ttystatus: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:python-ttystatus

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

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

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

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

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

Debian distribution maintenance software
pp.
Ondřej Nový  (supplier of updated python-ttystatus 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, 27 Nov 2019 11:36:59 +0100
Source: python-ttystatus
Architecture: source
Version: 0.38-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Ondřej Nový 
Closes: 938230
Changes:
 python-ttystatus (0.38-3) unstable; urgency=medium
 .
   * QA upload.
   * Drop Python 2 support (Closes: #938230).
   * Add dh-python to B-D.
   * d/copyright: Change Format URL to correct one.
   * Use debhelper-compat instead of debian/compat.
   * d/changelog: Remove trailing whitespaces.
   * d/control: Remove trailing whitespaces.
   * Enable autopkgtest-pkg-python testsuite.
Checksums-Sha1:
 64ec2a92b50fdd165a3e26f4e8c94d583b8912fd 1885 python-ttystatus_0.38-3.dsc
 21f82583b3a253f8d1ec1d65dc1deb165f1d8ed6 3008 
python-ttystatus_0.38-3.debian.tar.xz
 ce74fb22cc0d9eb58cf6808e84e28fb20c2b8765 6569 
python-ttystatus_0.38-3_amd64.buildinfo
Checksums-Sha256:
 b1600aabd9c5032c3de025d6510c12c7c46f1202af85ca

Processing of python-ttystatus_0.38-3_source.changes

[Debian FTP Masters]

python-ttystatus_0.38-3_source.changes uploaded successfully to localhost
along with the files:
  python-ttystatus_0.38-3.dsc
  python-ttystatus_0.38-3.debian.tar.xz
  python-ttystatus_0.38-3_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

python-ttystatus_0.38-3_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Nov 2019 11:36:59 +0100
Source: python-ttystatus
Architecture: source
Version: 0.38-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Ondřej Nový 
Closes: 938230
Changes:
 python-ttystatus (0.38-3) unstable; urgency=medium
 .
   * QA upload.
   * Drop Python 2 support (Closes: #938230).
   * Add dh-python to B-D.
   * d/copyright: Change Format URL to correct one.
   * Use debhelper-compat instead of debian/compat.
   * d/changelog: Remove trailing whitespaces.
   * d/control: Remove trailing whitespaces.
   * Enable autopkgtest-pkg-python testsuite.
Checksums-Sha1:
 64ec2a92b50fdd165a3e26f4e8c94d583b8912fd 1885 python-ttystatus_0.38-3.dsc
 21f82583b3a253f8d1ec1d65dc1deb165f1d8ed6 3008 
python-ttystatus_0.38-3.debian.tar.xz
 ce74fb22cc0d9eb58cf6808e84e28fb20c2b8765 6569 
python-ttystatus_0.38-3_amd64.buildinfo
Checksums-Sha256:
 b1600aabd9c5032c3de025d6510c12c7c46f1202af85ca0258b7347f03bceb12 1885 
python-ttystatus_0.38-3.dsc
 f03991c54d0001ebf490467e08081a65145869a1264b5a64b572d246d657c548 3008 
python-ttystatus_0.38-3.debian.tar.xz
 5bc43815136a44c6e349a3ef4a145fc3b157cad54356250eb764f0edd7361168 6569 
python-ttystatus_0.38-3_amd64.buildinfo
Files:
 feefbf4fbe54d16032eeb19a6d255b61 1885 python optional 
python-ttystatus_0.38-3.dsc
 73661ef5ad522037ffdde15474d50894 3008 python optional 
python-ttystatus_0.38-3.debian.tar.xz
 22c72bf97d02fe21d0f1a5bf4a69 6569 python optional 
python-ttystatus_0.38-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAl3eUlYACgkQNXMSVZ0e
BksxHQ/+IEJEf6vMxrR68ZOF6f7+fNnYRssphF1cqccIIRjw6+DoGEQ7Jtls4IZz
zdNiCLru8Smg4U16MAxvliwnO+S2qg1vIffpVXmTbX5nUJZfQH50ydJFCzedrQNO
bzdJgLY8Zz7ZoOwW7X+ZDdzaKxRYFOjwqO1lBHNPGbvBiWF3/mWcJf18m6r7mOTs
KcbHwigKMIiw8skHdqjRlpRc9THTE33bwE+knMnT8PFOd2HkJA0qwTjaF23T9koj
xqUcnHuE4DhJV+rycGof37LpmVzq9ZVGzdk0kjmcFQpBEuBMoAI7IywS7yMyud+s
XAp9qBe9X4Z0cq6X7cNJQ77Tbb7oKp79XJtwx+JPUfljcIzuI4RHyRwbzy4I0htn
2Zse6DpkNnNRrMJili197JoDgEiZn4Ci80NuG3vRWDEYcPtuHBVY83tm8g0TgKts
DrjYI3PdqaKnpb4oTuCKpY5L54jkPNZEleu6zJVYqgZz4xABXZpgGPecUCpDlvf/
t/UvFgqLoWS/r+RFUnDBfPvEmDjEBgO/5DTEaWMoQHzhEDGtw5Eb5VsItw0ixbY0
A+OeFzmoMkFslAjA1oD19nYNpYYCFj8GM4lbOxC3NuwmtOSr/ObbtuI/Ac1+DKSV
nBCUFHtFxR+TJhFNSpXXXnR5nBPBM7HY3w16Dtp7z/piiRRc4rs=
=YFzS
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processing of flask-babel_0.11.2-3_source.changes

[Debian FTP Masters]

flask-babel_0.11.2-3_source.changes uploaded successfully to localhost
along with the files:
  flask-babel_0.11.2-3.dsc
  flask-babel_0.11.2-3.debian.tar.xz
  flask-babel_0.11.2-3_amd64.buildinfo

Greetings,

Your Debian queue daemon (running on host usper.debian.org)

flask-babel_0.11.2-3_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Wed, 27 Nov 2019 11:49:05 +0100
Source: flask-babel
Architecture: source
Version: 0.11.2-3
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Ondřej Nový 
Closes: 936524
Changes:
 flask-babel (0.11.2-3) unstable; urgency=medium
 .
   * Orphan package.
   * d/control: Remove ancient X-Python-Version field.
   * d/control: Remove ancient X-Python3-Version field.
   * d/copyright: Use https protocol in Format field.
   * Use debhelper-compat instead of debian/compat.
   * Use Python 3 for building docs.
   * Drop Python 2 support (Closes: #936524).
   * Enabler autopkgtest-pkg-python testsuite.
Checksums-Sha1:
 15b5f6984997f03911d77b8b254c8d5bcd8d6410 2160 flask-babel_0.11.2-3.dsc
 20be8e5805bfdc4f50dd2d64be5e837791f7a6d4 3988 
flask-babel_0.11.2-3.debian.tar.xz
 dea2d50d8c2142942a548f3edd1240b3d130ed17 7556 
flask-babel_0.11.2-3_amd64.buildinfo
Checksums-Sha256:
 59021090e7d36029d8821ca4af7898cc5efdcdc9223d0cafea3ce6d04eb69ff3 2160 
flask-babel_0.11.2-3.dsc
 b3f3d8913d172ab358eb71ec4174860ef0c115f181966f0884afc19d6b42663a 3988 
flask-babel_0.11.2-3.debian.tar.xz
 8393d3ef6487bc58fd523c0e667a3297b1cf634402dd9ff1d5e117545fc65c70 7556 
flask-babel_0.11.2-3_amd64.buildinfo
Files:
 907b54e26d2274fcebe328a84a5dd04d 2160 python optional flask-babel_0.11.2-3.dsc
 2532474fb6d3a3049ad0aced13914a81 3988 python optional 
flask-babel_0.11.2-3.debian.tar.xz
 29ec7081f8bf4380a86de9500af6b571 7556 python optional 
flask-babel_0.11.2-3_amd64.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAl3eVR0ACgkQNXMSVZ0e
Bks/Mg/9E4hZ0WkZBzrsStAwRfiHPa8mQBjvb6rm9Trq+Jys3nv/UUD46UB6Mzq/
JqsyVYQAk5Jz8aLRbT1kLv3OIk3gzVse30GU30n9rrlrGy1b4eJx8+VyQ4+6ruvG
AjfgXjuQjlMZSQhS6THmw7tHHTEQWl4hgGT1qENs930kR6nZ9oJ68RSz1wYP61db
ZLydWCcXOjHfDOGdhv/IbxgkS7Gej0qsGKX/rixd6CoMQPxJfPYl/ukUDgV4t6S8
mXi3rQQ6CUsXKIRvqftH8bSWLqRpO925UETwY90KPCyXZii2ehruw1hfm4hd2EaO
72/7TTGsPBU1aHPbl+EDTTgXVn6HUs1PN2k2FrnM6dCS2SDr+pwZWy/tx7tBV8Nv
nPUKndP0myDbRPa5m7sWyShbeGcz0a0GkM3WgLdcuMrwNbPbgEmvT0I5d+bziVEQ
JgoUTStAyuUNsfsrBd1/6BjPD0u3W25H7KlOs5Tog3qmgNZK/zwwnt1+0wW/Lv9i
81Sghk2dnsyfjnDLqkAtT3gfQnymAVlO0yM1s8Z/d9hkDIG3ePeGkO7QbGciS9XG
qsyLkWPMYVFcLzioFzn+Kc7z33Ypp/pu61s0rs+MCytnFoIsAu6Sje0O+2VIXMWK
2FG1vZ4Yyr7ZwCeULHUUOGc25xMRzXIIQTc8SDgXnRrSWR7gaXE=
=761M
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Processed: reassign 944135 to src:linux, tagging 945489, tagging 945567, tagging 945566, tagging 945545

[Debian Bug Tracking System]

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

> reassign 944135 src:linux
Bug #944135 {Done: Bdale Garbee } [linux-image-5.2.0-3-amd64] 
laptop audio not working
Warning: Unknown package 'linux-image-5.2.0-3-amd64'
Bug reassigned from package 'linux-image-5.2.0-3-amd64' to 'src:linux'.
No longer marked as found in versions linux-signed-amd64/5.2.17+1.
Ignoring request to alter fixed versions of bug #944135 to the same values 
previously set
> tags 945489 + experimental
Bug #945489 [src:llvm-toolchain-9] llvm-toolchain-9: autopkgtest needs update 
for new version of cmake: fails on warning
Added tag(s) experimental.
> tags 945567 + sid bullseye
Bug #945567 [src:network-manager-strongswan] network-manager-strongswan FTBFS: 
error: G_ADD_PRIVATE
Added tag(s) sid and bullseye.
> tags 945566 + sid bullseye
Bug #945566 {Done: Mike Gabriel } 
[src:ayatana-indicator-application] ayatana-indicator-application FTBFS: error: 
G_ADD_PRIVATE
Added tag(s) bullseye and sid.
> tags 945545 + sid bullseye
Bug #945545 [src:xpp] xpp FTBFS: error: invalid use of incomplete type 'ipp_t'
Added tag(s) sid and bullseye.
> thanks
Stopping processing here.

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

Bug#945630: cplay: Python2 removal in sid/bullseye

[Sandro Tosi]

Source: cplay
Version: 1.50-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

Bug#945650: ccontrol: Python2 removal in sid/bullseye

[Sandro Tosi]

Source: ccontrol
Version: 1.0-2
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

Bug#945658: ladr: Python2 removal in sid/bullseye

[Sandro Tosi]

Source: ladr
Version: 0.0.200911a-2.1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

Bug#945671: fofix-dfsg: Python2 removal in sid/bullseye

[Sandro Tosi]

Source: fofix-dfsg
Version: 3.121-7
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

Bug#945676: obex-data-server: Python2 removal in sid/bullseye

[Sandro Tosi]

Source: obex-data-server
Version: 0.4.6-1
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

Bug#945689: polipo: Python2 removal in sid/bullseye

[Sandro Tosi]

Source: polipo
Version: 1.1.1-10
Severity: normal
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2removal

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

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

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

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

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

  This is the least preferred option.

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

fet_5.40.3-1_source.changes ACCEPTED into unstable

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Format: 1.8
Date: Fri, 22 Nov 2019 20:58:39 -0300
Source: fet
Architecture: source
Version: 5.40.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group 
Changed-By: Thiago Andrade Marques 
Closes: 934854
Changes:
 fet (5.40.3-1) unstable; urgency=medium
 .
   * QA upload, orphaning package; see #945298.
   * New upstream version 5.40.3.
   * debian/control:
   - Added 'Rules-Requires-Root: no' in source stanza.
   - Added VCS fields.
   - Bumped Standards-Version to 4.4.1.
   * debian/rules: Removed override_dh_dwz, no longer needed. (Closes: #934854)
   Thanks to Gianfranco Costamagna.
Checksums-Sha1:
 19209951cbf7f9244c4f0966a2c59b6a189b23c9 2112 fet_5.40.3-1.dsc
 d812fff52256f4d357a49b5a24fcaafee7702211 12415149 fet_5.40.3.orig.tar.bz2
 7b51c3db3ae4d5391ac6b2f56f61a7b855dbbee0 833 fet_5.40.3.orig.tar.bz2.asc
 e732dc4881aca42635526d0995545b592abbddce 20348 fet_5.40.3-1.debian.tar.xz
 e764a6c417a10aa480b81edea3da9fa64da63cc3 5462 fet_5.40.3-1_source.buildinfo
Checksums-Sha256:
 33ccac6253aece9045ce441c9be44ca44a8e9be85e5527cc5542f32963d8b64d 2112 
fet_5.40.3-1.dsc
 0fb4a9eedbaa7825ff2ba090db96a187ccb60d1a5948cce58ec74d151ec76eff 12415149 
fet_5.40.3.orig.tar.bz2
 07d97d4af553a5d039ae37299480be07f708013c9ad9b4da7e4903c8363b7bd7 833 
fet_5.40.3.orig.tar.bz2.asc
 aeba6df5dfe926c6705d78f1bc317d2c779371ea4226da62f1055c7b8b94b8d4 20348 
fet_5.40.3-1.debian.tar.xz
 73d8cf0e661a5c8f61c12a579f675443248ee6369b5822f7f61fc00cbaf138c7 5462 
fet_5.40.3-1_source.buildinfo
Files:
 996f7e71196302c7e520552bcd49d7c6 2112 misc optional fet_5.40.3-1.dsc
 615ee468cd721b52bc6048e97fe07ac5 12415149 misc optional fet_5.40.3.orig.tar.bz2
 b7390fa5470e56c426e8d32a0585ba22 833 misc optional fet_5.40.3.orig.tar.bz2.asc
 f0c8ea9be92cec1df756d3f1172f3009 20348 misc optional fet_5.40.3-1.debian.tar.xz
 b443fe7ce0376dad97955d40d592f4ed 5462 misc optional 
fet_5.40.3-1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl3fLpwACgkQweDZLphv
fH6RpA/9EJPMf6jHIKaQiSdTYdpXwcL3DvHSrkHrWlK94d+Bl/65PfBK+COGb24g
E01tpSeIAT41FWkyx2I6mpOz0UjndHWVpxSo8Bk/h1vGa69H8iGxSe4IW8ETrza6
+KvHN0w5sZGOcsUyDYaSVjw25AfAPAAYHShUewIgpVDXeYQOu3jnfq2pGBvT++QB
boOIXWsDThpmJ0XGpo1UtYsFPuIshQsFwdlAs1xGSjaaw4jSgVDSY5x7xssrQqfa
5fQ4x9/fFVbYZC7rfnDsAS9tuM8owtb/HXYEXDIJ1u92d2HKaOE5mndYc1ISzZnw
eHNTNu+mHIyqgWoAD5Rr41emQW2/7XOgT5VZ9AgGctztot5nBH8iWTs33oNt3wNZ
SKyEktxv41+04LkeyohSVR1hy/WDfjYVYF/TaxDJ7OlyMlZJlP791re7FB9/tr2o
XKGfShly/8owERFPT8Lh6BZQ8Z5ckeVQFDZ3/6IKwN2w4kcx2dJeKRXYe8f7Zwfq
gzoVtVv8OGNkxU3Fu4NyaW0dALJ2VZe8X9XRIKjjLuQiKl/QxnxOLivaDuqkjwTH
DQ2f2lQXLI3/693lGiZ4fBjmUTt2q7FoZViqCHZ3ykQ0ScyCNz/0fylD4tyDSVIn
G0LRqmUPRwTn9yqDPQk4IxaVc3RT6KJBJpiCD1Rbp4NrBCzjl2Q=
=iFzo
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

Bug#128360: marked as done (ipcheck: debconf script could create /etc/ppp/ip-up.d/ipcheck)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:36:44 +
with message-id 
and subject line Bug#839971: Removed package(s) from unstable
has caused the Debian Bug report #128360,
regarding ipcheck: debconf script could create /etc/ppp/ip-up.d/ipcheck
to be marked as done.

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

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


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

Would be nice if ipcheck had a debconf script which asks the user for
interface, username, password and hostname and then creates a script
in /etc/ppp/ip-up.d/.

I think a lot of people  use it with ppp

-- System Information
Debian Release: 3.0
Kernel Version: Linux sonne 2.4.16-k7 #1 Wed Nov 28 11:06:52 EST 2001 i686 
unknown

Versions of the packages ipcheck depends on:
ii  python 2.1.1-4An interactive object-oriented scripting lan

--- End Message ---
--- Begin Message ---
Version: 0.233-2+rm

Dear submitter,

as the package ipcheck 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/839971

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#122195: marked as done (ipcheck: Have ipcheck automatically update dyndns.org.)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:36:44 +
with message-id 
and subject line Bug#839971: Removed package(s) from unstable
has caused the Debian Bug report #122195,
regarding ipcheck: Have ipcheck automatically update dyndns.org.
to be marked as done.

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

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


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

It'd be lovely if the ipcheck package did all the magic required to
have it automatically update the dyndns.org database when one's IP
address actually changed.  I suspect most users have simply setup cron
to update the dyndns.org database, regardless of whether or not their
IP address had changed.  It'd be nice if ipcheck not only updated only
when necessary (ie: on IP address change) but also made sure it
updated at least every 28 days to make sure people with static or
relatively static dynamic IPs didn't lose their hostnames.  Also, I
believe setting up cron to update often (read: every five minutes)
falls into the category of "abuse" under the terms of the dyndns.org
user agreement.

-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux nirvana 2.4.14-686-smp #1 SMP Fri Nov 9 22:56:52 EST 2001 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages ipcheck depends on:
ii  python2.1.1-4An interactive object-oriented scr


--- End Message ---
--- Begin Message ---
Version: 0.233-2+rm

Dear submitter,

as the package ipcheck 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/839971

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#139083: marked as done (please provide dyndns-client)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:36:44 +
with message-id 
and subject line Bug#839971: Removed package(s) from unstable
has caused the Debian Bug report #139083,
regarding please provide dyndns-client
to be marked as done.

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

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


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

Package: ipcheck
Severity: wishlist

Hi!

There are a few packages that act as dyndns clients
now. Please could you set a Provides: dyndns-client in
this package?

Thanks

--

Robert Millan  Debian GNU/* user
zeratul2 wanadoo eshttp://getyouriso.dyndns.org/




--- End Message ---
--- Begin Message ---
Version: 0.233-2+rm

Dear submitter,

as the package ipcheck 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/839971

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#268620: marked as done (cplay: should be able to quit at end of playlist)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #268620,
regarding cplay: should be able to quit at end of playlist
to be marked as done.

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

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


-- 
268620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=268620
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cplay
Version: 1.49-5
Severity: wishlist

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hi,

I call cplay from a shell script which at runtime assembles a
playlist.  Therefore a "-q" option for quitting automatically
after playing the last file would be helpful.

Ciao; Gregor


- -- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8
Locale: LANG=de_DE@euro, LC_CTYPE=de_DE@euro

Versions of packages cplay depends on:
ii  python2.3.4-3sid An interactive high-level object-o

- -- no debconf information

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBL33I8uuCWtJTB8oRAmYaAJ40ESeB0DbhHEUA0XAz4IqTMJUDQwCfS3ey
PdAnuUdtD2N6AiHTk33A+v0=
=yF3r
-END PGP SIGNATURE-

--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#226167: marked as done (cplay: Wishlist item: Adding and changing playlist with shell command)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #226167,
regarding cplay: Wishlist item: Adding and changing playlist with shell command
to be marked as done.

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

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


-- 
226167: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=226167
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cplay
Version: 1.49-2
Severity: wishlist

Hi,

I would like to have the possibility in cplay to add items to playlist
from "outside", that is, from another shell and not the cplay user
interface. In that way it would be possible to change the playlist
without navigating with the cplay "Filelist".

xmms supports such a feature. If xmms is running and you run a command
like 'xmms $SOMEDIR/audio.mp3' it is played at once. You can also supply
paths and m3u playlists to xmms with this command.
If you run the same command with the parameter '-e', the items are added
(enqueued) to the current playlist of xmms.

I would like to have such behaviour for cplay, too.

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux charlie 2.4.21 #2 Mon Jul 28 01:23:17 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=de_DE@euro

Versions of packages cplay depends on:
ii  python2.3-4  An interactive high-level object-o

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#263374: marked as done (cplay: saner list window handling)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #263374,
regarding cplay: saner list window handling
to be marked as done.

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

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


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

Package: cplay
Version: 1.49-4
Severity: wishlist
Tags: patch

The cplay handling of scrolling lists has always seemed suboptimal.  In
both the directory / file window and the playlist window, as you scroll
up or down, there is no text overlap between screenfuls.  In addition,
the PgUp and PgDown keys always reposition your cursor at the top of
the window.

The following patch provides a 2-line overlap between screenfuls, and,
as much as possible, keeps your cursor on the same screen line as you
page up and down.  Despite the length of the patch (it was harder than
it looked!) there are no other changes.

It is reasonably well tested, but I'm not a Python programmer, so
caveat maintainor.

Peter
--- cplay.orig  2003-12-05 02:20:56.0 -0600
+++ cplay   2004-08-03 19:16:44.0 -0500
@@ -169,6 +169,7 @@
 self.w = self.newwin()
 self.ypos, self.xpos = self.getbegyx()
 self.rows, self.cols = self.getmaxyx()
+self.scrollinc = self.rows - 2
 self.keypad(1)
 self.leaveok(0)
 self.scrollok(0)
@@ -400,10 +401,16 @@
  self.parent.ypos+2, self.parent.xpos)
 
 def update(self, force = 1):
-self.bufptr = max(0, min(self.bufptr, len(self.buffer) - 1))
-scrptr = (self.bufptr / self.rows) * self.rows
-if force or self.scrptr != scrptr:
-self.scrptr = scrptr
+bufmax = len(self.buffer) - 1
+self.bufptr = max(0, min(self.bufptr, bufmax))
+self.scrptr = max(0, min(self.scrptr, bufmax))
+if force or \
+   self.bufptr < self.scrptr or \
+   self.bufptr > self.scrptr + self.rows - 1:
+self.scrptr = self.bufptr - self.bufptr % self.scrollinc
+if self.scrptr >= self.scrollinc and \
+   self.scrptr + self.rows - self.scrollinc > bufmax:
+self.scrptr -= self.scrollinc
 self.move(0, 0)
 self.clrtobot()
 i = 0
@@ -445,30 +452,55 @@
 if self.bufptr >= len(self.buffer): self.bufptr = len(self.buffer) - 1
 return self.buffer[self.bufptr]
 
-def cursor_move(self, ydiff):
+def cursor_moveto(self, y):
 if app.input_mode: app.cancel_input()
 if not self.buffer: return
 self.update_line(refresh = 0)
-self.bufptr = (self.bufptr + ydiff) % len(self.buffer)
+self.bufptr = y % len(self.buffer)
 self.update(force = 0)
+
+def cursor_move(self, ydiff):
+self.cursor_moveto(self.bufptr + ydiff)
 
 def cursor_ppage(self):
-tmp = self.bufptr % self.rows
-if tmp == self.bufptr:
-self.cursor_move(-(tmp+(len(self.buffer) % self.rows) or 
self.rows))
+if self.scrptr > 0:
+# Yes, ugly.  The double move is in order to force the
+# cursor onto the correct page ("scrptr"), since lines at the
+# top / bottom of a page could go on either of two pages.  The
+# same thing, for the same reason, appears in 3 other places.
+tmp = max(0, self.bufptr - self.rows)
+tmp2 = max(0, self.bufptr - self.scrollinc)
+self.cursor_moveto(tmp)
+self.cursor_moveto(tmp2)
 else:
-self.cursor_move(-(tmp+self.rows))
+# Wrap to last page.  This is complicated by the fact that
+# the "last page" as calculated by "% scrollinc" sometimes
+# overestimates by one page.
+buflen = len(self.buffer)
+lastscr = buflen - buflen % self.scrollinc
+if lastscr + self.rows - self.scrollinc > buflen - 1:
+lastscr -= self.scrollinc
+bufptr = min(self.bufptr + lastscr, buflen - 1)
+self.cursor_moveto(buflen - 1)
+self.cursor_moveto(bufptr)
 
 def cursor_npage(self):
-tmp = self.rows - self.bufptr % self.rows
-if self.bufptr + tmp > len(self.buffer):
-self.cursor_move(len(self.buffer) - self.bufptr)
+buflen = len(self.buffer)
+if self.scrptr + self.rows < buflen:
+# See comment in cursor_ppage re: double move.

Bug#153566: marked as done (ipcheck: I have created a /etc/init.d/ipcheck file.)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:36:44 +
with message-id 
and subject line Bug#839971: Removed package(s) from unstable
has caused the Debian Bug report #153566,
regarding ipcheck: I have created a /etc/init.d/ipcheck file.
to be marked as done.

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

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


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

Package: ipcheck
Version: 0.177-1
Severity: wishlist

To use create a directory /var/lib/ipcheck/ 
Put in /etc/ipcheck.conf your username, password and hostnames.
Set your options in /etc/init.d/ipcheck
Setting "--makedat" in /etc/init.d/ipcheck the first time only.
Execute "update-rc.d ipcheck defaults" so it runs on boot.

-- System Information
Debian Release: 3.0
Kernel Version: Linux Midkemia 2.4.16 #1 Wed Dec 19 23:38:52 EST 2001
i686 unknown

Versions of the packages ipcheck depends on:
ii  python 2.1.3-3An interactive object-oriented
scripting lan


#! /bin/sh
#
# ipcheck	File to be put in /etc/init.d/ to execute ipcheck.
#		ipcheck is a dynamic DNS client that sends your ip
#		to a server which assocates it with hostnames.
#		An example of a service provider is dyndns.org
#		ipcheck should be run everytime your ip address 
#		changes or every 25 days.
#		
# This file based on skeleton 
#		Written by Miquel van Smoorenburg .
#		Modified for Debian GNU/Linux
#		by Ian Murdock .
#
# Version:	@(#)skeleton  1.9.1  08-Apr-2002  miqu...@cistron.nl
#		ipcheck   1.0.0  19-Jul-2002  p...@andreassen.com.au
#

PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/sbin/ipcheck
NAME=ipcheck
DESC="dynamic DNS client"
OPTIONS="-T password -w"
# must be run with "--makedat" first time
# debug with verbose option "-v"

test -x $DAEMON || exit 0

set -e

case "$1" in
  start)
	echo -n "Starting $DESC: $NAME"
	$DAEMON --syslog -d /var/lib/ipcheck $OPTIONS --acctfile=/etc/ipcheck.conf
	echo "."
	;;
  stop)
	echo -n "Stopping $DESC: $NAME "
#	-o requires service provider consent
#	$DAEMON --syslog -d /var/lib/ipcheck -p 8245 $OPTIONS -o --acctfile /etc/ipcheck.conf	
	echo "."
	;;
  #reload)
	#
	#	If the daemon can reload its config files on the fly
	#	for example by sending it SIGHUP, do it here.
	#
	#	If the daemon responds to changes in its config file
	#	directly anyway, make this a do-nothing entry.
	#
	# echo -n "Reloading $DESC configuration..."
	# start-stop-daemon --stop --signal 1 --quiet --pidfile \
	#	/var/run/$NAME.pid --exec $DAEMON
	# echo "done."
  #;;
  restart|force-reload)
	#
	#	If the "reload" option is implemented, move the "force-reload"
	#	option to the "reload" entry above. If not, "force-reload" is
	#	just the same as "restart".
	#
	echo -n "Restarting $DESC: $NAME"
	$DAEMON --syslog -d /var/lib/ipcheck -p 8245 $OPTIONS --acctfile /etc/ipcheck.conf		
	echo "."
	;;
  *)
	N=/etc/init.d/$NAME
	# echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
	echo "Usage: $N {start|stop|restart|force-reload}" >&2
	exit 1
	;;
esac

exit 0
--- End Message ---
--- Begin Message ---
Version: 0.233-2+rm

Dear submitter,

as the package ipcheck 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/839971

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#231320: marked as done (Major Security hole in ipcheck with SMC routers 7004ABR and 7004VBR)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:36:44 +
with message-id 
and subject line Bug#839971: Removed package(s) from unstable
has caused the Debian Bug report #231320,
regarding Major Security hole in ipcheck with SMC routers 7004ABR and 7004VBR
to be marked as done.

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

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


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

The script works with SMC routers specifically the 7004ABR Barricade and the 
7004VBR Barricade only if you login before you run the script, set the 
administrator timeout to zero and kill the browser.  THIS CONFIGURATION IS 
UNACCEPTABLE!  This leaves the router config open on the linux box in question 
and does not allow for a proper securing of the router.  ANY person logging in 
on the linux box in question running the ipcheck script with the open router 
login will have access to modifythe router if connected.  This is a major 
security hole. 

Your script in an ideal situation for both routers should do the following:

1.  Log in to the router.
2.  switch to the status.HTM page on the router
3.  Read the IP address
4.  Log out of the router.

This should occur with an administrator login timeout  of ten minutes.

I am willing to test your script but am unable to write in python.  I do
not know python scripting.  

-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux xrayserve 2.4.21 #1 SMP Tue Feb 3 16:54:29 EST 2004 i686
Locale: LANG=C, LC_CTYPE=C

Versions of packages ipcheck depends on:
ii  python2.3.3-5An interactive high-level object-o

-- no debconf information



























--- End Message ---
--- Begin Message ---
Version: 0.233-2+rm

Dear submitter,

as the package ipcheck 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/839971

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#590184: marked as done (cplay: would be great that after quit, resume the last playlist)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #590184,
regarding cplay: would be great that after quit, resume the last playlist
to be marked as done.

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

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


-- 
590184: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590184
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cplay
Version: 1.49-10
Severity: wishlist

For fvwm, cplay could be great to resume what we were playing last time of use
Best regards
Y.

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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

Versions of packages cplay depends on:
ii  python2.6.5-5An interactive high-level object-o

Versions of packages cplay recommends:
ii  python-pyvorbis   1.4-2+b1   Python interface to the Ogg Vorbis
ii  vorbis-tools  1.4.0-1several Ogg Vorbis tools

Versions of packages cplay suggests:
pn  mikmod (no description available)
pn  python-id3 (no description available)
pn  sox(no description available)
pn  speex  (no description available)
ii  splay 0.9.5.2-11 Sound player for MPEG-1,2 layer 1,
pn  xmp(no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#397889: marked as done (ipcheck with Alcatel firmware v. 4.3.2.6)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:36:44 +
with message-id 
and subject line Bug#839971: Removed package(s) from unstable
has caused the Debian Bug report #397889,
regarding ipcheck with Alcatel firmware v. 4.3.2.6
to be marked as done.

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

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


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

ipcheck does not detect the ip on Alcatel routers with firmware version 
4.3.2.6.
The command to show the ip list has changed, and the list has another form,
Here is a transcript:

=> ip iplist
Interface   TypeIP-address   Point-to-point/Mask
2   LocalNetworkEthernet   *192.168.xxx.xxx 255.255.255.0
1   InternetSerial  83.53.215.201192.168.153.1
0   loopInternal127.0.0.1255.255.255.255

I made that modification to the ipcheck program, that works for me, and I 
believe the previous functionality is preserved,

# connect to the router's admin webpage
try:
  logger.logit("Trying Alcatel STP")
  # disables negotiation to prevent the connection being dropped
  telnetlib.IAC="\021"  
  tn = telnetlib.Telnet(iphost)
  logger.logit("Creating telnetlib obj done")
  tn.read_until(" : ")
  logger.logit("User prompt found")
  tn.write(Alcatel_user + "\r")
  tn.write(opt_AlcatelSTP_password + "\r")
  logger.logit("opt_AlcatelSTP_password sent")
  tn.read_until("=>")
  tn.write("ip aplist\r")
  logger.logit("ip aplist sent")
  ret=tn.read_until("SERIAL",5)
  if string.find(ret,"SERIAL")==-1:
# is an Alcatel version 4.3.2.6 ?
tn.write("\r")
tn.read_until("=>")
tn.write("ip iplist\r")
logger.logit("ip iplist sent")
ret=tn.read_until("Serial  ",5)
if string.find(ret,"Serial  ")==-1:
   raise "not connected"
  else:
tn.read_until("addr:")
  ip2 = tn.read_until(" ")
  logger.logit("ip read")
  ipdata = ip2[:-1]

I suggest do some modification like the previous one,

I am using Debian GNU/Linux 3.2, kernel 2.6.18


--- End Message ---
--- Begin Message ---
Version: 0.233-2+rm

Dear submitter,

as the package ipcheck 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/839971

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#287871: marked as done (seek forward can start from wrong offset when new song is chosen)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #287871,
regarding seek forward can start from wrong offset when new song is chosen
to be marked as done.

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

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


-- 
287871: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=287871
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cplay
Version: 1.49-6
Severity: minor

Image that you play a song, then you either select the next song (with
n) or start the same song again (with enter), and then you immediately
press ctrl-f to forward in the new song.  In most cases, cplay does
the right thing and starts the forward from offset 0 in the new file.
However, in some cases it starts from the offset of the last song
which was played.

This is a bit tricky to reproduce since you have to be very quick and
need some luck, but I added some debug messages to cplay to show
what's going on.  Basically, what happens is that the new song is
chosen, offset is set to 0, but then sometimes parse_progress() would
be called which still has the file handles of the old song.  It will
parse the output and set offset to the old offset, overwriting
offset = 0 which was just set.

I guess cplay should immediately close the file handles when a new
song is chosen to make sure that the output of the old song is not
parsed.

Here is the case when a new song was chosen, ctrl-f pressed
immediately and it would continue from the old offset.  The
interesting line is "Player set_position(): offset = 3039..." right
after the offset is set to 0:

[the old song plays at some offset]
Player set_position(): offset = 3037, length  = 7197, values = [3037, 4160]
Player parse_progress(): self.stopped: 0, self.step: 0
Player set_position(): offset = 3039, length  = 7198, values = [3039, 4159]
[a new song is chosen, offset set to 0, etc]
command_play()
command_play(): entry exists (1)
command_play(): entry exists (2)
Applicaton play(): offset = 0
Player stop():
Player setup(): offset: 0
Player setup(): offset is 0, setting self.offset = 0
Applicaton play(): ok, found player: offset = 0
play(): self.offset : 0
play(): self.offset : 0
update_status()
Player parse_progress(): self.stopped: 0, self.step: 0
[the output of the old song are read and offset is overwritten]
Player set_position(): offset = 3039, length  = 7197, values = [3039, 4158]
Applicaton(): offset = 1, relative = 1
Player(): offset = 1, relative = 1
 self.length: 7197
 self.offset: 3039
 self.step (before): 0.00
 self.step (after): 14.394000
 self.offset (before): 3039.00
 self.offset (after): 3053.394000
play(): self.offset : 0
Applicaton(): offset = 1, relative = 1
Player(): offset = 1, relative = 1
 self.length: 7197
 self.offset: 3053
 self.step (before): 14.394000
 self.step (after): 28.788000
 self.offset (before): 3053.394000
 self.offset (after): 3082.182000
Applicaton(): offset = 1, relative = 1
Player(): offset = 1, relative = 1
 self.length: 7197
 self.offset: 3082
 self.step (before): 28.788000
 self.step (after): 43.182000
 self.offset (before): 3082.182000
 self.offset (after): 3125.364000


In comparison, this is what happens normally:

Player set_position(): offset = 2356, length  = 7196, values = [2356, 4840]
Player parse_progress(): self.stopped: 0, self.step: 0
Player set_position(): offset = 2357, length  = 7196, values = [2357, 4839]
command_play()
command_play(): entry exists (1)
command_play(): entry exists (2)
Applicaton play(): offset = 0
Player stop():
Player setup(): offset: 0
Player setup(): offset is 0, setting self.offset = 0
Applicaton play(): ok, found player: offset = 0
play(): self.offset : 0
play(): self.offset : 0
play(): self.offset : 0
update_status()
Player parse_progress(): self.stopped: 0, self.step: 0
Player set_position(): offset = 0, length  = 7196, values = [0, 7196]
Applicaton(): offset = 1, relative = 1
Player(): offset = 1, relative = 1
 self.length: 7196
 self.offset: 0
 self.step (before): 0.00
 self.step (after): 14.392000
 self.offset (before): 0.00
 self.offset (after): 14.392000
Applicaton(): offset = 1, relative = 1
Player(): offset = 1, relative = 1
 self.length: 7196
 self.offset: 14
 self.step (before): 14.392000
 self.step (after): 28.784000
 self.offset (before): 14.392000
 self.offset (after): 43.176000
Applicaton(): offset = 1, relative = 1
Player(): offset = 1, relative = 1
 self.length: 7196
 self.offset: 43
 self.step (before): 28.784000
 self.step (after): 43.176000
 self.offset (before): 43.176000
 self.of

Bug#590093: marked as done (cplay: repeat mode should be clearer: track or playlist ?)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #590093,
regarding cplay: repeat mode should be clearer: track or playlist ?
to be marked as done.

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

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


-- 
590093: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590093
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cplay
Version: 1.49-10
Severity: wishlist



Press H 
" r, R  : toggle repeat/Random mode"

 cplay: repeat mode should be clearer: track or playlist ?


Best regards


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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

Versions of packages cplay depends on:
ii  python2.6.5-5An interactive high-level object-o

Versions of packages cplay recommends:
ii  python-pyvorbis   1.4-2+b1   Python interface to the Ogg Vorbis
ii  vorbis-tools  1.4.0-1several Ogg Vorbis tools

Versions of packages cplay suggests:
pn  mikmod (no description available)
pn  python-id3 (no description available)
pn  sox(no description available)
pn  speex  (no description available)
ii  splay 0.9.5.2-11 Sound player for MPEG-1,2 layer 1,
pn  xmp(no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#581690: marked as done (cplay not playing the url into the m3u of streams)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #581690,
regarding cplay not playing the url into the m3u of streams
to be marked as done.

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

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


-- 
581690: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581690
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cplay
Version: 1.49-10
Severity: important

Hello,

I am using often splay, because it is cool and is not X.

I encountered errors when trying to paly a playlist of streams, containing into 
a m3u type file.
It is the rmffm of m3u that is available on the next. So the program hangs and  
cannot play the music.

I can manage using : mplayer -playlist rmf.m3u

Any ideas to make cplay better in the future?

cheers


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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

Versions of packages cplay depends on:
ii  python2.5.4-9An interactive high-level object-o

Versions of packages cplay recommends:
ii  python-pyvorbis   1.4-2+b1   Python interface to the Ogg Vorbis
ii  vorbis-tools  1.4.0-1several Ogg Vorbis tools

Versions of packages cplay suggests:
pn  mikmod (no description available)
pn  python-id3 (no description available)
pn  sox(no description available)
pn  speex  (no description available)
ii  splay 0.9.5.2-11 Sound player for MPEG-1,2 layer 1,
pn  xmp(no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#585239: marked as done (ipcheck: Python string exceptions no more allowed in Python 2.6)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:36:44 +
with message-id 
and subject line Bug#839971: Removed package(s) from unstable
has caused the Debian Bug report #585239,
regarding ipcheck: Python string exceptions no more allowed in Python 2.6
to be marked as done.

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

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


-- 
585239: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=585239
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: ipcheck
Version: 0.233-1
Severity: minor
User: debian-pyt...@lists.debian.org
Usertags: python2.6

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

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

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

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

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

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

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

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

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

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

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


--- End Message ---
--- Begin Message ---
Version: 0.233-2+rm

Dear submitter,

as the package ipcheck 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/839971

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#557447: marked as done (cplay: crash once we forward, with right arrow, the music)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #557447,
regarding cplay: crash once we forward, with right arrow, the music
to be marked as done.

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

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


-- 
557447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=557447
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cplay
Version: 1.49-10
Severity: important

Dear Sir

cplay hangs while playing music. I had ogg123 that was running,
i listen mp3 and press RIGHT arrow to go bit further in the mp3
it directly jumps to the next track insted :( 

I thought that it can for ogg123
...
so les beta testing
apt-get remove ogg123

then 
restart cplay.
and here we go
splay plays the music 

and it hangs again as soon as we fool around to listen bit forward (right key) 
on several mp3... 
so it hangs again

1. It was workign under Debian Stable
2. It hangs, please it s crashing 
3. It is an important or serious issue


lsmod | grep snd

 lsmod | grep snd
snd_usb_audio  70272  0
snd_usb_lib13440  1 snd_usb_audio
snd_hwdep   6212  1 snd_usb_audio
snd_hda_intel 325688  0
snd_pcm_oss32800  0
snd_mixer_oss  12320  1 snd_pcm_oss
snd_pcm62660  3 snd_usb_audio,snd_hda_intel,snd_pcm_oss
snd_page_alloc  7816  2 snd_hda_intel,snd_pcm
snd_seq_dummy   2660  0
snd_seq_oss24992  0
snd_seq_midi5728  0
snd_rawmidi18496  2 snd_usb_lib,snd_seq_midi
snd_seq_midi_event  6432  2 snd_seq_oss,snd_seq_midi
snd_seq41456  6 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
snd_timer  17800  2 snd_pcm,snd_seq
snd_seq_device  6380  5 
snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
snd45636  11 
snd_usb_audio,snd_hwdep,snd_hda_intel,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
soundcore   6368  1 snd
usbcore   118192  6 
snd_usb_audio,snd_usb_lib,usbhid,ehci_hcd,uhci_hcd



Best regards
Y.



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

Kernel: Linux 2.6.26-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages cplay depends on:
ii  python2.5.2-3An interactive high-level object-o

Versions of packages cplay recommends:
ii  python-pyvorbis   1.3-2  A Python interface to the Ogg Vorb
ii  vorbis-tools  1.2.0-5several Ogg Vorbis tools

Versions of packages cplay suggests:
pn  mikmod (no description available)
ii  mpg123   1.4.3-4 MPEG layer 1/2/3 audio player
ii  mpg321 [mpg123]  0.2.10.6mpg123 clone that doesn't use floa
pn  python-id3 (no description available)
ii  sox  14.0.1-2+b1 Swiss army knife of sound processi
pn  speex  (no description available)
ii  splay0.9.5.2-11  Sound player for MPEG-1,2 layer 1,
pn  xmp(no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#303282: marked as done (pressing 'n' immediately confuses cplay)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #303282,
regarding pressing 'n' immediately confuses cplay
to be marked as done.

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

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


-- 
303282: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=303282
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cplay
Version: 1.49-7
Severity: minor

When you start cplay passing it a directory of songs to play and then
immediately press 'n' before cplay comes up it gets confused.  It will
play the first song and say that it's playing the first song, but the
second song will be highlighted.  When you press 'n' in cplay, it will
go to the third song (skipping the second one).

I've attached a screenshot.

This may or may not be related to #287871 ("seek forward can start from
wrong offset when new song is chosen").



-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-686
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages cplay depends on:
ii  python2.3.5-2An interactive high-level object-o

-- no debconf information

-- 
Martin Michlmayr
http://www.cyrius.com/
--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#308679: marked as done (ipcheck: please add support for Siemens Speedstream 2604)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:36:44 +
with message-id 
and subject line Bug#839971: Removed package(s) from unstable
has caused the Debian Bug report #308679,
regarding ipcheck: please add support for Siemens Speedstream 2604
to be marked as done.

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

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


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

Hi,
I am using a Siemens Speedstream 2604 router which has a dyndns client
built in. It seems to be different from the Siemens 2620, which is already
supported by ipcheck. I am submitting information which I hope is sufficient
to add support for the 2604. 

One of the password protected pages (at least in my config), that displays
the IP is (with router being my router): http://router/title.htm

And the page looks like this:






SpeedSteam 2604













SpeedStream 2604







 Internet:

 IP Address:
 82.83.xxx.yyy


 Connection:
 PPPoE




 


 LAN: 
 IP Address:
 192.168.xxx.yyy



 DHCP Server:
 OFF














Christian

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.10-1-386
Locale: LANG=C, LC_CTYPE=en_US (charmap=ISO-8859-1)

Versions of packages ipcheck depends on:
ii  python2.3.5-2An interactive high-level object-o

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 0.233-2+rm

Dear submitter,

as the package ipcheck 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/839971

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#339553: marked as done (cplay: please add audioscrobbler support)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #339553,
regarding cplay: please add audioscrobbler support
to be marked as done.

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

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


-- 
339553: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=339553
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cplay
Version: 1.49-10
Severity: wishlist

It'd rock to have audioscrobbler support for cplay since all of the
other players that support it are... not as good. I have no idea how
this could be implemented, but maybe it's easy.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.12-1-amd64-k8
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages cplay depends on:
ii  python2.3.5-3An interactive high-level object-o

Versions of packages cplay recommends:
ii  python-pyvorbis   1.3-1  A Python interface to the Ogg Vorb
ii  vorbis-tools  1.0.1-1.5  Several Ogg Vorbis Tools

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#290896: marked as done (cplaly doesn't check if files exist)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #290896,
regarding cplaly doesn't check if files exist
to be marked as done.

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

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


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

When you do "cplay foo" it doesn't check whether foo exists; the same
applies for files listed in a playlist.

* jo...@magma.com.ni  [2005-01-16 13:59]:
> I learned, that cplay does not care about existing or not existing files
> and directories.  The net results is, that they are silently ignored (it
> does not sigfault at least :)
> 
> IMHO the check about existing or not existing media should go into the
> Filelist or playlist class, with proper and/or convenient error
> handling.
> 
> Saludos,
> 
> Jorge-León

-- 
Martin Michlmayr
http://www.cyrius.com/

--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#590091: marked as done (it could be cool that one can play music stream with cplay, like a jukebox)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #590091,
regarding it could be cool that one can play music stream with cplay, like a 
jukebox
to be marked as done.

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

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


-- 
590091: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=590091
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cplay
Version: 1.49-10
Severity: wishlist

 it could be cool that one can play music stream with cplay, like a jukebox


cplay is cool cuz it is command line !!!

Love it

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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

Versions of packages cplay depends on:
ii  python2.6.5-5An interactive high-level object-o

Versions of packages cplay recommends:
ii  python-pyvorbis   1.4-2+b1   Python interface to the Ogg Vorbis
ii  vorbis-tools  1.4.0-1several Ogg Vorbis tools

Versions of packages cplay suggests:
pn  mikmod (no description available)
pn  python-id3 (no description available)
pn  sox(no description available)
pn  speex  (no description available)
ii  splay 0.9.5.2-11 Sound player for MPEG-1,2 layer 1,
pn  xmp(no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#896089: marked as done (cplay: Please move to new upstream source)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #896089,
regarding cplay: Please move to new upstream source
to be marked as done.

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

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


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

Dear Maintainer,

the version of cplay that is packaged with debian is 7 years old.  The
upstream source is no longer active, but there are two active forks I
know of:  (maintained by myself) and
.

Both forks have fixed several bug, refactored the code to modern
coding python coding standards (e.g. pep8), and support python3. They
have also added support for new backends like gst123 and mpv. My
version is packaged for pypi. We activly share patches.

Note that I started my fork after reporting
.

Given that python2 support will end in 2020, I would like to ask you
to switch to one of these upstream repos. Is there anything we can do
to help with that switch?

tobias
--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#624596: marked as done (ipcheck: New upstream version available (0.241))

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:36:44 +
with message-id 
and subject line Bug#839971: Removed package(s) from unstable
has caused the Debian Bug report #624596,
regarding ipcheck: New upstream version available (0.241)
to be marked as done.

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

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


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

A new upstream version (0.241) is available:

  http://ipcheck.sourceforge.net/ipcheck.py

Cheers,
Francois


--- End Message ---
--- Begin Message ---
Version: 0.233-2+rm

Dear submitter,

as the package ipcheck 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/839971

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

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:36:44 +
with message-id 
and subject line Bug#839971: Removed package(s) from unstable
has caused the Debian Bug report #943069,
regarding ipcheck: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package ipcheck 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/839971

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

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #945630,
regarding cplay: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package cplay 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/827890

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

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:37:37 +
with message-id 
and subject line Bug#891353: Removed package(s) from unstable
has caused the Debian Bug report #936477,
regarding email2trac: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

  affects  + src:email2trac

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

Dear submitter,

as the package email2trac 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/891353

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

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:37:04 +
with message-id 
and subject line Bug#869312: Removed package(s) from unstable
has caused the Debian Bug report #942995,
regarding dctrl2xml: 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.)


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

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

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

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

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

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

  This is the least preferred option.

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

Dear submitter,

as the package dctrl2xml 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/869312

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#597999: marked as done (cplay: press I to get information about track: artists, folder, path, size, codecs ...)

[Debian Bug Tracking System]

Your message dated Thu, 28 Nov 2019 06:35:41 +
with message-id 
and subject line Bug#827890: Removed package(s) from unstable
has caused the Debian Bug report #597999,
regarding cplay: press I to get information about track: artists, folder, path, 
size, codecs ...
to be marked as done.

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

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


-- 
597999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: cplay
Version: 1.49-10
Severity: wishlist

I pressed H and there is no key for information about the track(s)

coudl be great to be added:

press I to get information about track: artists, folder, path, size, codecs ...


All the best , cplay is cool


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

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

Versions of packages cplay depends on:
ii  python2.6.5-11   interactive high-level object-orie

Versions of packages cplay recommends:
ii  python-pyvorbis   1.4-2+b1   Python interface to the Ogg Vorbis
ii  vorbis-tools  1.4.0-1several Ogg Vorbis tools

Versions of packages cplay suggests:
pn  mikmod (no description available)
pn  python-id3 (no description available)
pn  sox(no description available)
pn  speex  (no description available)
ii  splay 0.9.5.2-11 Sound player for MPEG-1,2 layer 1,
pn  xmp(no description available)

-- no debconf information


--- End Message ---
--- Begin Message ---
Version: 1.50-2+rm

Dear submitter,

as the package cplay 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/827890

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#827890: Removed package(s) from unstable

[Debian FTP Masters]

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

 cplay | 1.50-2 | source, all

--- Reason ---
RoQA; orphaned 3+ years ago; python2-only; dead upstream; low popcon
--

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

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

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

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

Bug#839971: Removed package(s) from unstable

[Debian FTP Masters]

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

   ipcheck |0.233-2 | source, all

--- Reason ---
RoQA; orphaned 3+ years ago; python2-only; dead upstream; low popcon; 
alternatives exist
--

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

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

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

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

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

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

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

Bug#869312: Removed package(s) from unstable

[Debian FTP Masters]

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

 dctrl2xml |   0.20 | source, all

--- Reason ---
RoQA; orphaned 2+ years ago; python2-only; dead upstream (native pkg); low 
popcon
--

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

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

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

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

Bug#891353: Removed package(s) from unstable

[Debian FTP Masters]

Version: 2.10.0-2+rm

Dear submitter,

as the package email2trac 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/891353

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)

Bug#891353: Removed package(s) from unstable

[Debian FTP Masters]

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

email2trac |   2.10.0-2 | source
trac-email2trac |   2.10.0-2 | all

--- Reason ---
RoQA; orphaned 1+ years ago; python2-only (as trac is); low popcon
--

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

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

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

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

Bug#869312: Removed package(s) from unstable

[Debian FTP Masters]

Version: 0.20+rm

Dear submitter,

as the package dctrl2xml 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/869312

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)