Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de> writes: > Arnaud Vandyck <avdyk@debian.org> writes: > >> Sorry if it's already been replied, I'm not up-to-date... > > No, your still on the "Thanks for the quick reply" list. Tomorrow I > might drop the 'quick'. ;) >> About every Java packages, they are not going in contrib because most >> depends on j2sdk1.(3|4) so, they are in contrib. THEY ARE NOT BROKEN! >> They just need a non-free JDK to build or to run. > > Which means they need manual intervention to get pushed into sarge. It > just needs to be done where appropriate. A bunch of the java related > packages maintainer replied that they are waiting on sablevm or > kaffe. Maybe that will be ready for sarge. All the java package with j2sdk1.3|j2sdk1.4 dependencies or with the virtual package java2-runtime are not able to be compiled or run with sablevm or kaffe. They need a non-free JDK. That is a problem and I think it has already been discussed. > ? No Problem ;) >> > argouml >> >> At the moment, argouml is 0.14. It's the latest stable release of the >> software and stuck in unstable because it needs j2sdk1.(3|4). If you >> wanna write some of the Swing classes to fill the 'classpath' project >> gaps, feel free to do it. > > Then it should just be hinted into sarge. Yes, but it cannot go to sarge because of the non-free j2sdk dependency (I mean automatically) >> > ibm-jdk1.1-installer > > Noted, will check back on it. If it's not marked removed, you can do it, it should! [...] > Thats fine. No hurry. You said you are around and aware of the > packages and thats enough. NP Cheers, -- Arnaud
Attachment:
pgpOMCGmhqtwo.pgp
Description: PGP signature