Package Details: jameica 2.8.4-4

Git Clone URL: (read-only)
Package Base: jameica
Description: free runtime environment for java applications
Upstream URL:
Licenses: GPL2
Submitter: jakob
Maintainer: fordprefect
Last Packager: fordprefect
Votes: 74
Popularity: 0.793137
First Submitted: 2006-10-21 16:11
Last Updated: 2019-03-14 12:09

Required by (3)

Sources (7)

Latest Comments

1 2 3 4 5 6 ... Next › Last »

fordprefect commented on 2019-03-14 12:08

@stepborc: please import the key and try again: gpg --receive-keys 5A8ED9CFC0DB6C70. You can setup gpg autoretrieve as well.

@mareex: jre versions are a mess. jre above 9 includes java-jce_ustrength, which otherwise needs to be supplied as dependency. However, some jameica plugins (notably mashup) require the oracle java in version 8 (still the suggested version at their website). so, i agree that enforcing java-environment>10 does not really make sense, the fractured java ecosystem is not easy to handle in this case.

stepborc commented on 2019-03-09 07:41

Unfortunately there is a problem with the public key.

"FEHLGESCHLAGEN (Unbekannter öffentlicher Schlüssel 5A8ED9CFC0DB6C70)"

mareex commented on 2019-02-25 17:38

Any valid reason why this PKGBUILD enforces 'java-runtime>=10'? Everything works fine here with java 8

r4ndom commented on 2019-01-24 21:25

@fordprefect: Works on my side. Thanks

fordprefect commented on 2019-01-24 09:36

Ok. I will leave this as it is now and fix this tonight on my arch machine. Sorry! EDIT: should all be fixed now, runs like this smoothly at least for me. Please test and report issues. Thanks everyone!

r4ndom commented on 2019-01-24 09:34

@fordprefect: Running sed -i 's/jameica-linux/\/opt\/jameica\/jameica-linux/g' /usr/bin/jameica and running jameica afterwards returns an error saying manifest /usr/bin/plugin.xml not readable.

I guess it is because the current path is incorrect (like @Taijian already stated)

fordprefect commented on 2019-01-24 08:50

@Taijian: damn, didn't think about that. Unfortunately I'm not at my machine now, so I can't test. Does it work prepending the jameica-linux with /opt/jameica in /usr/bin/jameica:21 ?

Taijian commented on 2019-01-24 08:43

OK, now it doesn't start any more. Looking at the patch you removed, I think you went a little too far. You should only have removed the java9 compatability line, NOT the whole patch, because now /usr/bin/jameica looks for jameica-linux64.jar in whatever dir the user was in when trying to start jameica, not in /opt/jameica. So please restore most of 'jameica-start-script.patch', only removing the java9 part.

Thank you!

fordprefect commented on 2019-01-24 08:03

@kwe: thanks, fixed. pkgrel bump omitted.

kwe commented on 2019-01-23 23:05

@fordprefect In 0036171d029b you've removed jameica-start-script.patch but the file is still in the prepare() function.