ccontrol is marked for autoremoval from testing

2019-10-06 Thread Debian testing autoremoval watch
ccontrol 1.0-2 is marked for autoremoval from testing on 2019-10-21 It is affected by these RC bugs: 885519: ccontrol: Recommends unmaintained pygtk

fslint is marked for autoremoval from testing

2019-10-06 Thread Debian testing autoremoval watch
fslint 2.46-1 is marked for autoremoval from testing on 2019-10-21 It is affected by these RC bugs: 885280: fslint: Depends on unmaintained pygtk

Bug#941878: RM: vusb-analyzer -- RoQA; unmaintained, depends on Python2 and pygtk

2019-10-06 Thread Jeremy Bicha
Package: ftp.debian.org X-Debbugs-Cc: vusb-analy...@packages.debian.org Affects: src:vusb-analyzer vusb-analyzer was orphaned in 2011 and has had basic packaging fixes since then. The packaging itself is fine. The problem is that it uses Python2 and pygtk and both are in the process of being

Processed: volti: Depends on unmaintained pygtk

2019-10-06 Thread Debian Bug Tracking System
Processing control commands: > block 885135 by -1 Bug #885135 [src:pygtk] pygtk: Unmaintained, use GObject Introspection instead Bug #885752 [src:pygtk] pygtk: Unmaintained, should not be released with Debian 885135 was blocked by: 885481 885515 885478 885140 885365 941869 885269 885267 885494

Bug#941877: volti: Depends on unmaintained pygtk

2019-10-06 Thread Jeremy Bicha
Source: volti Version: 0.2.3-7 Severity: serious Control: block 885135 by -1 User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs pygtk Tags: sid bullseye pygtk is unmaintained upstream. It has not had a release since GNOME 3 was released in 2011. Also, it uses Python2 and

Bug#885280: bumping severity of pygtk bugs

2019-10-06 Thread Jeremy Bicha
Control: severity -1 serious Control: tags -1 -buster Control: block 885135 by -1 As part of the Python2 removal, it is our intent that pygtk will be removed from Testing before the release of Debian 11 "Bullseye". Therefore, I am bumping the severity of this bug to Serious to ensure that there

Processed: bumping severity of pygtk bugs

2019-10-06 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #885280 [src:fslint] fslint: Depends on unmaintained pygtk Severity set to 'serious' from 'important' > tags -1 -buster Bug #885280 [src:fslint] fslint: Depends on unmaintained pygtk Removed tag(s) buster. > block 885135 by -1 Bug #885135

Bug#885519: bumping severity of pygtk bugs

2019-10-06 Thread Jeremy Bicha
Control: severity -1 serious Control: tags -1 -buster As part of the Python2 removal, it is our intent that pygtk will be removed from Testing before the release of Debian 11 "Bullseye". Therefore, I am bumping the severity of this bug to Serious to ensure that there is plenty of warning

Processed: bumping severity of pygtk bugs

2019-10-06 Thread Debian Bug Tracking System
Processing control commands: > severity -1 serious Bug #885519 [src:ccontrol] ccontrol: Recommends unmaintained pygtk Severity set to 'serious' from 'important' > tags -1 -buster Bug #885519 [src:ccontrol] ccontrol: Recommends unmaintained pygtk Removed tag(s) buster. -- 885519:

Bug#941819: Removed package(s) from unstable

2019-10-06 Thread Debian FTP Masters
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: liborbit-2-0 | 1:2.14.19-4 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el, s390x liborbit2 | 1:2.14.19-4 | amd64, arm64, armel, armhf, i386, mips64el, mipsel, ppc64el,

Bug#941819: Removed package(s) from unstable

2019-10-06 Thread Debian FTP Masters
Version: 1:2.14.19-4+rm Dear submitter, as the package orbit2 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/941819