On Thu, Mar 11, 2004 at 01:21:45AM -0500, Grzegorz B. Prokopski wrote: > And I still cannot understand why packages built from sablevm source > (sablevm, libsablevm1, libsablevm-dev, jikes-sablevm) cannot migrate to > testing along with packages built from sablevm-classlib > (libsablevm-classlib1-java and libsablevm-nativelib1).
> The script says: > sablevm is waiting for sablevm-classlib > * Updating sablevm-classlib makes 2 depending packages > uninstallable on alpha: libsablevm1, sablevm > * Updating sablevm makes 2 non-depending packages uninstallable on > alpha: libsablevm1, sablevm > I understand that there might be some other dependencies of some of > these binary packages. Maybe libsablevm-native1 has been built with > newer version of gtk+? I _don't know_ and I see no way to get these > informations from any of interfaces known to me. This would help me > assess if ex. it makes sense to upload new packages, or should I just > wait 3 days for some abcdef package to migrates too... > I've seen (on the MLs) that some packages need "hints" in testing > scripts. Do I need them for SableVM? How can I find out? Or is there > some problem with my packages? On SID they apt-get install just fine. Yes, this package does need a hint, which I've now added. Assuming there are no problems I missed, both sablevm and sablevm-classlib should make it into testing on the 12th. Regards, -- Steve Langasek postmodern programmer
signature.asc
Description: Digital signature
