Marking this "Fix released" instead:
it fails if there's not enough RAM, e.g. on a 256MB OpenVZ machine (which has
no swap space).
It's fixed like this in 6b17~pre3-1 (and probably before):
if ! $basedir/bin/java -client -Xshare:dump -XX:PermSize=128m > $log;
then
cat >&2 $lo
Oh, seems very probable to me, because that time I had
vm.overcommit_memory=2. And now surprise: I had this problem on system
with 1510MB of RAM and 1907MB of swap.
--
Java upgrade from gutsy to hardy is broken: openjdk-6-jre-headless
(6b09-0ubuntu2) configuration fails
https://bugs.launchpad.ne
"java -client -Xshare:dump -XX:PermSize=128m > $log.txt" as part of
/var/lib/dpkg/info/openjdk-6-jre-headless.postinst seems to be the
problem. Specifically, at least in my case, the problem is tied in with
my use of sysctl vm.overcommit_memory=2 to avoid overcommiting memory.
Changing back to the
I don't know why it works now and didn't three days ago :/
Sorry for making trouble
** Changed in: openjdk-6 (Ubuntu)
Status: Incomplete => Invalid
--
Java upgrade from gutsy to hardy is broken: openjdk-6-jre-headless
(6b09-0ubuntu2) configuration fails
https://bugs.launchpad.net/bugs/21
couldn't reproduce this yet; is the reproducible on another machine?
** Changed in: openjdk-6 (Ubuntu)
Status: New => Incomplete
--
Java upgrade from gutsy to hardy is broken: openjdk-6-jre-headless
(6b09-0ubuntu2) configuration fails
https://bugs.launchpad.net/bugs/219631
You received
** Attachment added: "log"
http://launchpadlibrarian.net/13578823/log
--
Java upgrade from gutsy to hardy is broken: openjdk-6-jre-headless
(6b09-0ubuntu2) configuration fails
https://bugs.launchpad.net/bugs/219631
You received this bug notification because you are a member of Ubuntu
Bugs, w
