Re: [ANN] New version of j2se-package (formerly mpkg-j2sdk)
Takashi Okamoto wrote: I would like to upload j2se-package Nov 11. If you disagree, please tell me. I don't disagree but I think the FTP admins will reject the package after reading the "ftpmaster accepts packages that have been rejected a few days ago" thread in -devel, especially http://lists.debian.org/debian-devel/2003/debian-devel-200311/msg00766.html. Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [ANN] New version of j2se-package (formerly mpkg-j2sdk)
I don't disagree but I think the FTP admins will reject the package after reading the "ftpmaster accepts packages that have been rejected a few days ago" thread in -devel, especially http://lists.debian.org/debian-devel/2003/debian-devel-200311/msg00766.html. And why do you think that? The cases look quite different to me. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [ANN] New version of j2se-package (formerly mpkg-j2sdk)
Stefan Gybas <[EMAIL PROTECTED]> writes: > I don't disagree but I think the FTP admins will reject the package > after reading the "ftpmaster accepts packages that have been rejected > a few days ago" thread in -devel, especially > http://lists.debian.org/debian-devel/2003/debian-devel-200311/msg00766.html. Well, it seems that _some_ FTP admins will and some don't, so if you get a REJECT just keep on submitting it until you get REJECTs from each of them... :) -- * Sufficiently advanced magic is indistinguishable from technology (T.P) * * PGP public key available @ http://www.iki.fi/killer * -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [ANN] New version of j2se-package (formerly mpkg-j2sdk)
Daniel Bonniot wrote: And why do you think that? The cases look quite different to me. Because the FTP admins abviously don't want to have a lot of small packages when these small scripts/binaries with the same target users can easily be put into a single package (that's also my opinion). But we'll see if the package gets accepted or not, I really don't mind if it gets accepted. Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[charva] Shared libs and JNI
Hi this(); I'm working on 'charva' package (#203187) and it has a shared library called libTerminal.so. Is it a good name? If not, how to change it? Do I put it in /usr/lib/jni/? Do I have to split the package or can I just package it as 'charva'? [I think it's very java-centric and it's the first time I'm dealing with JNI! If debian-mentors is more appropriate, I'm also a subscriber, so feel free to redirect the discussion on that list.] Best regards, -- .''`. Arnaud Vandyck : :' : http://people.debian.org/~avdyk/ `. `' `- pgp0.pgp Description: PGP signature
Re: [ANN] New version of j2se-package (formerly mpkg-j2sdk)
Because the FTP admins abviously don't want to have a lot of small packages when these small scripts/binaries with the same target users can easily be put into a single package (that's also my opinion). Yes, but I don't see what existing package could hold this script. java-common certainly belongs to main, while this script requires non-free software, and so should be in contrib. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kaffe in testing
Salut Arnaud, hi all, Arnaud Vandyck wrote: On Tue, 11 Nov 2003 14:20:39 +0100 Daniel Bonniot <[EMAIL PROTECTED]> wrote: [...] Given that a release it coming, it would be really nice if these issues could be solved. There are at the moment 17 packages prevented to enter testing because of kaffe. Or looking at it more positively, making kaffe enter testing would allow (or at least help?) 17 other package to enter too. :-) Two more important bugs (but I did not file it on the bts): - problem with xml entities (bug introduced by gnujaxp): resolved with 1.1.2 - java.util.TimeZone.SHORT does not exists: resolved with 1.1.2 Dalibor, when do you plan a new release of kaffe? I am not personally involved in the debian packaging of kaffe [1], so I can't say what Ean's plans are. Kaffe 1.1.3 should come out by the beginning of december according to our 'every two months a release' [2] schedule. Marko Jung, one of our local debianistas in Saarbruecken, expressed some interest in helping out with the packaging of kaffe to take some of the load off Ean due to our frequent release schedule, and to help with getting up to date kaffe releases into testing, and the next debian release. I've CC:ed him on this mail, too. If Ean approves, he could help out with kaffe packaging. I think Marko already applied to become a debian maintainer, and is, AFAIK, currently packaging the ATI binary drivers. cheers, dalibor topic [1] Beside going over the debian bug database ocassionally, and pointing out what's been fixed in the CVS. [2] http://www.mail-archive.com/[EMAIL PROTECTED]/msg03400.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kaffe in testing
Daniel Bonniot wrote: The other bug is a build problem on m68k, so it is probably going to go away when the builds on (alpha, arm, m68k, s390, sparc) are fixed. Are these architecture supported upstream? If yes, then maybe Dalibor could look at the logs and help with diagnosing the problem. If not, then maybe they should be removed from kaffe architecture list, so it can move in testing for the working ones. Those build failures should have been fixed in 1.1.2. They were mostly introduced by the new gcc version being more strict about bad code than versions before ;) In general, you can regard any platform in the CVS as supported with kaffe. How far the support goes, though, depends on how many people there are developing on it. As usual, the more popular platforms (intel) have more developers working on them, so bugs get spotted faster and fixed quicker. ;) cheers, dalibor topic -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kaffe in testing
Hi, Thanks Dalibor for these great news (and his work on Kaffe itself). So it seems that upstream 1.1.2 fixes most of the releast-critical problems of kaffe (except the manpage bug). It would therefore be very important for Java-on-Debian to have a new package made soon. Ean, can you do it? If you are busy, maybe Marko can prepare the packages, and you can review them and upload them when they are OK. Daniel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Kaffe in testing
On Wed, 12 Nov 2003 15:51:39 +0100 Dalibor Topic <[EMAIL PROTECTED]> wrote: > I am not personally involved in the debian packaging of kaffe, so I > can't say what Ean's plans are. I think Ean does not want to upload a newer kaffe because it's nearly freeze time for Debian... It would be better to resolve the last 'trivial bugs' and upload the newest release as possible _before_ freeze time. > Kaffe 1.1.3 should come out by the beginning of december > according to our 'every two months a release' schedule. Great! I'd love to see this release in Debian... stable ;) Best regards, -- .''`. Arnaud Vandyck : :' : http://people.debian.org/~avdyk/ `. `' `- pgp0.pgp Description: PGP signature
Re: [charva] Shared libs and JNI
Hallo Arnaud,
* Arnaud Vandyck wrote:
>I'm working on 'charva' package (#203187) and it has a shared library
>called libTerminal.so.
>Is it a good name?
>If not, how to change it?
Hm, from my basic JNI knowledge from eclipse, the lib is loaded from
code in a static block somewhere. Look for something like
static {
System.loadLibrary(name);
}
change the name probably involves renaming the native library and that
call. If you want to support different versions of that lib, it is
probably better to change the name to -.so. Thats what
eclipse does.
>Do I put it in /usr/lib/jni/?
Yes.
When we switch to the findjava system, it should even be possible to
get the sun derived, binary only JVMs to include that dir in
-Djava.library.path by setting that optionin the 'GENERAL_ARGS'
variable of the java-config file. So to be policy complient, there
isn't a need for wrapper scripts.
>Do I have to split the package or can I just package it as 'charva'?
When I read the policy right, it's better to split out *big* arch
dependend portions, so if your whole package is only very small, just
put everything into one package and label it as 'any' instead of
'all'. This will mean, that you have to build it on all platform
(while you are on it: eclipse needs to have its libswt-*-java and
eclipse-platform compiled on all kaffe platforms...), when i can' go
into main...
If the both parts are very large, then it would make sense to split
it into one arch dependend and one 'arch all' package, but I gues that
will never be achieved by a simple java lib...
>[I think it's very java-centric and it's the first time I'm dealing with
>JNI! If debian-mentors is more appropriate, I'm also a subscriber, so
>feel free to redirect the discussion on that list.]
Read the policy, IMO it explains the problem quite good.
Jan
--
Jan Schulz [EMAIL PROTECTED]
"Wer nicht fragt, bleibt dumm."
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [ANN] New version of j2se-package (formerly mpkg-j2sdk)
In message: <[EMAIL PROTECTED]> Jan Schulz <[EMAIL PROTECTED]> writes: >Hallo Hubert, > >* Hubert Schmid wrote: >>the package also be called 'mpkg-j2se'? > >BTW: what does "2se stand for?" J2SE stands for Java2 Standard Edition in Sun-speak. Similarly, J2EE is Java2 Enterprise Edition, including a bunch of extra libraries useful for running an app server. In the mpkg-j2se context, it's presumably referring to the distribution that's getting packaged. - Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFT: charva -- java windowing toolkit for text terminals
Request For Tests (and for Review and for Comments)
Hi all,
It's the first time I package a jni library ('java native interface')
with a java library. Charva uses native bindings to render buttons,
listboxes etc. in a terminal.
You can apt-get libcharva1-java and libcharva1-jni here:
deb http://people.debian.org/myjava/charva/ ./
deb-src http://people.debian.org/myjava/charva/ ./
You can build the examples (don't forget to put
/usr/share/java/charva.jar in your classpath) and run it but
README.Debian first! ;)
Note: You can answer me in private,
the result will be in the pool asap.
Warning: It's in contrib and you'll need a jdk to build and a jre to
run... maybe nonfree jdk and jre at the moment.
Best regards and many thanks for your time and patience,
--
.''`. Arnaud Vandyck
: :' : http://people.debian.org/~avdyk/
`. `' http://people.debian.org/~avdyk/myjava/
`-
pgp0.pgp
Description: PGP signature
Re: [ANN] New version of j2se-package (formerly mpkg-j2sdk)
Hallo T., * T. Alexander Popiel wrote: >J2SE stands for Java2 Standard Edition in Sun-speak. Similarly, >J2EE is Java2 Enterprise Edition, including a bunch of extra >libraries useful for running an app server. In the mpkg-j2se >context, it's presumably referring to the distribution that's >getting packaged. Hm: I think most users will no know this context and will search for "java". So IMO, it would be best to include that buzzword somewhere in the package name. mpkg-java comes to my mind :) Jan -- Jan Schulz [EMAIL PROTECTED] "Wer nicht fragt, bleibt dumm." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
