Re: More Assignments
On Tue, Aug 19, 2003 at 05:32:02PM +1000, Anthony Towns wrote:
> This week's assignment is to pick between 10 and 20 source packages
> each to be removed from testing and/or unstable. Assignments are due
> next Monday (25th), and should look like:
> Package: pretzel
> Testing: 2.0n-1.1
> Unstable: 2.0n-1.1
> Bugs: 196579
> Suggestion: remove-from-testing
> Bug has been open for over two months, has had a patch for about
> a month and a half, no comments from the maintainer. No indication
> it'll be solved anytime soon.
Might as well start with a controversial one! Since we're going to
release with debian-installer, now would be a good time to eliminate
the confusion that still occasionally results from the continued
presence of the boot-floppies package. I'm only suggesting
remove-from-testing for now because the unstable distribution is the
only one to contain the actual boot-floppies source with which we
released woody, and removing that would be a bad idea. That should be a
candidate for a stable point release, upon which it could be removed
from unstable too.
Uninstallable, bug open for five months. Waiting for upstream to port
it to GNOME 2, which doesn't seem particularly forthcoming.
Depends on Qt2, and so uninstallable in unstable; bug open for six
months, RC for four. It's actually still installable in testing, but
won't be if we want to have KDE 3.
This is still installable in testing, actually, but only because it's
one of the packages holding back KDE 3. It's orphaned, nothing in
unstable depends on it, and the KDE maintainer agrees with removing it
for now (see http://lists.debian.org/debian-kde-0308/msg00183.html).
Fails to build due to new dh_kpatches requirement, bug filed eight
months ago. No response from maintainer.
Non-free, old binary (18.104.22.1684-1) on alpha.
Bugs: 161670 201866
Fails to build in various ways; 161670 open for nearly a year, 201866
open for a month. No maintainer upload since December 2001.
Bugs: 178732 185881
Completely broken as reported in #178732; bug open for seven months
with no response from the maintainer. Doesn't build either; bug open
for five months with no response from the maintainer. Note that
orp-classpath depends on this, but is obviously useless itself with a
Built for KDE 2.2, bug filed for five months, no response from
maintainer, only one upload ever (October 2001), upstream inactive.
Fails to build, bug open for three months. No comments from the
maintainer, who hasn't been seen since May.
Caught short in the Python 2.2 transition, now uninstallable in
testing, and all sorts of things have to be updated before it can
become installable again. Let's remove it until that happens.
Fails to build with current flex, bug open for three and a half months.
No response from the maintainer, who is famously inactive; no
maintainer upload since February 2002.
Depends on library that's been gone from unstable for ages and that we
want to remove from testing. New version fails to build on arm, m68k,
mips, mipsel; bug 198905 filed two months ago, no response. One of the
last packages holding up the libsigc++ dependency chain (at least once
glibc is fixed).
Fails to build for strange assembler reasons. Bug filed four months
ago, patch sent over a month ago. No comments from the maintainer.
Non-free, old binaries (1r2-6, 1r2-6.1) on arm, powerpc, sparc.
Fails to build with g++-3.0 and later. Bug open for nearly a year and a
half. No comments from the maintainer. Only recommending removal from
testing and not unstable because it does seem to fill a niche (slightly
different from an automounter).
Non-free, old binaries (3.1-4, 3.1-5) on alpha, arm, powerpc, sparc.
Non-free, old binaries (1.41-1) on ia64, sparc.
Uninstallable in unstable, since heyu was removed due to having a
non-free licence (#185031, which I guess is still an RC bug in testing,
really). Due to that, I think we would be better off releasing without
these two packages. In #185031, the maintainer said that he is no
longer able to maintain these packages; I've delegated this upwards to
Broken with current zope, bug filed five months ago, unmaintained
upstream and Debian maintainer apparently doesn't know how to fix it.
Colin Watson [email@example.com]