On Tue, Apr 20, 2004 at 20:22 -0400, Joey Hess wrote: > > Now I see. discover in testing depends on libdiscover1. libdiscover1 > > in testing in turn depends on discover-data. But discover-data in > > testing is discover2's data. So that's what you get. > > !! Isn't this a big problem with testing then?
Well, yes, I suppose. It's certainly a problem. I don't know exactly how the plan works though, how are you keeping discover2 out of testing? I don't see an RC bug against it. Furthermore, how are you going to install discover2 on 2.6 systems if it is not allowed into testing? Anyway, some ideas on how to solve this: - Get discover1 into testing. Currently it doesn't migrate because the old libdiscover-dev is in its way. The libdiscover1 in unstable depends on discover1-data instead of discover-data. - Copy the *.lst files from discover1-data to discover-data, drop discover1-data and make discover-data the only data package. - Get both discover2 and discover1 into testing and apt-install discover1 instead of discover from hw-detect. -- Pelle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
