On Sat, Nov 12, 2005 at 05:03:33AM -0600, Ross Johnson wrote:
> This might not be a kig problem, but it's a problem for kig to be in 
> testing when its dependencies can't be met.  Can we assign this bug 
> somewhere else or merge this with an existing bug report?

To what end?  This is not a bug that any package maintainer needs to take
action to fix; what needs to happen is that various packages need to have
their *other* bugs fixed so that they can be updated in testing.  Assigning
the bug elsewhere would just mean users couldn't see the status here when
looking at the BTS.

> I can't install kde in testing because it depends the problem originally 
> posted.  How did kig get into testing if it can't be installed in a 
> testing environment?

It was a least-bad choice in order to keep the necessary etch transitions
moving.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
[EMAIL PROTECTED]                                   http://www.debian.org/

Attachment: signature.asc
Description: Digital signature

Reply via email to