[Sablevm-developer] Pushing newer SableVM to testing (current sarge version is broken)

[Grzegorz B. P. <ga...@de...>]

tags 215314 fixed
close 215314
tags 230770 pending
tags 230770 sarge
thanks

Spoiler: classpath from SVN went into testing thus broke old sablevm
Solution: letting unstable version go into testing

Months ago, when I created SableVM Debian packages I assumed that
sablevm package of version ex. 1.0.9 should use classpath from
range 1.0.9 <= X < 1.0.10. This would prevent migration to testing
of unmatching sablevm/classlib. However recently I uploaded SableVM
and its Classpath Debian pacakages in version like 1.0.9+svnXXXXXX
which is still less "<" than 1.0.10. Thus it went into testing
w/o me noticing.

Therefore the only solution is to let unstable version go into testing
which was planeed to happen in a few days anyway, after the version,
that is currently held in NEW queue (and requires ftpmasters
intervention) is let into unstable.

Please keep in mind, that current unstable version has some minor
problems, but they're still much, much smaller than not working,
old 1.0.9 version.

To solve the problem now - please pull SableVM packages from unstable.

HTH

				Grzegorz B. Prokopski

-- 
Grzegorz B. Prokopski <ga...@de...>
Debian GNU/Linux      http://www.debian.org
SableVM - LGPLed JVM  http://www.sablevm.org
Why SableVM ?!?       http://devel.sablevm.org/wiki/WhySableVM