On Fri, May 07, 2004 at 08:15:05AM +0200, Andreas Metzler wrote: > Now that kdepim is finally in sync on m68k I was thinking whether it > would go into testing and stumbled e.g. over this: > In testing there a source-package "juk" that generates the binary > package juk, but the new version of kdemultimedia has juk integrated, > therefore there is no juk source in sid. - Will this be handled > automatically or does juk need to be hinted for removal[1]. This should happen automatically as soon as kdemultimedia makes it into testing. Since the only packages that appear to be holding up kdemultimedia are the debian-edu ones, this should resolve itself shortly. > Similar problems arise with kopete[1]. Then the answer should be the same. > I am prety sure that this > hint kdepim/4:3.2.2-2 kdenetwork/4:3.2.2-1 > is needed, because e.g. kmail has moved from kdenetwork to kdepim. The main reason the hint is needed seems to be that lurker depends on kdepim, installing kdenetwork on its own breaks lurker, and installing kdepim on its own breaks libkdenetwork2-dev. It doesn't bother anything for binary packages to be removed (or moved to a different source package), it's when they're uninstallable that testing balks. The hint appears to be correct in any case, and has been applied. Cheers, -- Steve Langasek postmodern programmer
Attachment:
signature.asc
Description: Digital signature