Hi,
sorry for bothering you, but there's something wrong (again) w/ migration
of SableVM packages to testing. Last time 1.1.0-5 was "hinted", so I
though that the "hint" is permanent and it would work this time also.
But the packages seem to be stalled again and for a reason no better
than previously. It's 13 days since upload, no bugs or missing deps
seem to invalidate transition to testing. The only thing is, that this
group of packages should migrate to testing together:
libsablevm1-dev libsablevm-native1 libsablevm-classlib1-java sablevm
jikes-sablevm libsablevm1
Could you please take a look at what's going on?
Thanks,
Grzegorz B. Prokopski
http://bjorn.haxx.se/debian/testing.pl?package=sablevm
Checking sablevm
* trying to update sablevm from 1.1.0-5 to 1.1.3-1 (candidate is 13
days old)
* sablevm is waiting for sablevm-classlib
o Updating sablevm-classlib makes 2 depending packages uninstallable
on alpha: libsablevm1, sablevm
o Updating sablevm-classlib makes 1 non-depending packages uninstallable
on alpha: libsablevm-native1
* Updating sablevm makes 2 non-depending packages uninstallable on alpha:
libsablevm1, sablevm
--
Grzegorz B. Prokopski <[EMAIL PROTECTED]>
Debian GNU/Linux http://www.debian.org
SableVM - LGPLed JVM http://www.sablevm.org
Why SableVM ?!? http://devel.sablevm.org/wiki/WhySableVM
