Re: Packaging eclipse 3.4.1 for debian/ubuntu
On Wed, 10 Dec 2008, Pantelis Koukousoulas wrote: I 'm interested to (help) package eclipse 3.4.1 for debian / ubuntu. Great. This is quite a big task so I 'd like as much help as I can get if this is to succeed. The plan is to start by copying as much as possible from what Fedora and Gentoo have already done plus whatever debian/ubuntu work is already there and improving upon those. Would you be willing to help? I have to admit that I'm very frustrated about the responsibility of the maintainer, namely the Debian Java Team to bug #432350 and the failure to even send a single response to the bug report. The consequence that I have to draw from this fact is that this team either does not have a single member which is working on Eclipse at all. If this assumtion is true - I hope at least this can be confirmed by any member of the team, if not I have to assume that there is no such team at all - I think we should add more staff to the team. So my first action now was to subscribe to the list. I never felt competent to do so in the past because ma Java knowledge is basically zero - but as I said, I have some packaging experience and if there are some testers I might be helpful. I also asked to add myself to the alioth project to be able to commit to the development svn. I would advise anybody who really intends to be helpful to follow these two steps. For the concrete packaging I would at first suggest to clean up the source packaging. Currently the source tarball contains three zip archives from completely separate upstream projects. IMHO this is no optimal packaging strategy and I would start by packaging icu4j and jsch separately and once this is done create a proper get-upstream-source target for debian/rules to enable newcomers to drop in by providing a defined state of work. In case there is some reason to merge separate upstream projects in one source tarball which might have been introduced by Michael Koch (icu4) and Vladimir Lapacek (jsch) I would like to hear these reasons and whether they are valid until today (=with the new Eclipse version). Kind regards Andreas. -- http://fam-tille.de ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#508342: ant: Ant dependency
Package: ant Version: 1.7.0-6 Severity: normal I installed ant with openjdk-6-jre and gij. When i try to run ant it's saying: $ ant Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-6-openjdk/lib/tools.jar After installed openjdk-6-jdk it's solved. I guess openjdk-6-jdk should be depend of ant. Best regards. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages ant depends on: ii gij [java-virtual-machine]4:4.3.2-2 The GNU Java bytecode interpreter ii gij-4.3 [java-virtual-machine 4.3.2-2The GNU Java bytecode interpreter ii libxerces2-java 2.9.1-2Validating XML parser for Java wit ii openjdk-6-jre [java2-runtime] 6b11-9 OpenJDK Java runtime, using Hotspo ii openjdk-6-jre-headless [java- 6b11-9 OpenJDK Java runtime, using Hotspo Versions of packages ant recommends: ii ant-gcj 1.7.0-6Java based build tool like make ii ant-optional 1.7.0-6Java based build tool like make - Versions of packages ant suggests: pn ant-doc none (no description available) -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: Packaging eclipse 3.4.1 for debian/ubuntu
So my first action now was to subscribe to the list. Done. I also asked to add myself to the alioth project to be able to commit to the development svn. I would advise anybody who really intends to be helpful to follow these two steps. I 'm not a debian developer, would it be possible for me to do this? In any case I think I 'd prefer to keep this unofficial at first and commit to a central repository when we have something reasonably serviceable. For the concrete packaging I would at first suggest to clean up the source packaging. Currently the source tarball contains three zip archives from completely separate upstream projects. IMHO this is no optimal packaging strategy and I would start by packaging icu4j and jsch separately and once this is done create a proper get-upstream-source target for debian/rules to enable newcomers to drop in by providing a defined state of work. Agreed. Btw, It would be nice if interested people drop by #debian-java in OFTC to discuss things in person. Thanks, Pantelis ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: Packaging eclipse 3.4.1 for debian/ubuntu
On Wed, 10 Dec 2008, Pantelis Koukousoulas wrote: So my first action now was to subscribe to the list. Done. Fine. I 'm not a debian developer, would it be possible for me to do this? In any case I think I 'd prefer to keep this unofficial at first and commit to a central repository when we have something reasonably serviceable. You can do this if you ask for an Alioth guest account first. Btw, It would be nice if interested people drop by #debian-java in OFTC to discuss things in person. I can not IRC at daytime and I hesitate to IRC in my spare time. I'd be willing to join a meeting at a defined date and time. Kind regards Andreas. -- http://fam-tille.de ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Processing of plexus-io_1.0~alpha2-1_i386.changes
plexus-io_1.0~alpha2-1_i386.changes uploaded successfully to localhost along with the files: plexus-io_1.0~alpha2-1.dsc plexus-io_1.0~alpha2.orig.tar.gz plexus-io_1.0~alpha2-1.diff.gz libplexus-io-java_1.0~alpha2-1_all.deb Greetings, Your Debian queue daemon ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#508342: ant: Ant dependency
Ant itself does not need java compiler to run. Following is the message I get. $ ant Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-6-openjdk/lib/tools.jar Buildfile: build.xml does not exist! Build failed You can see that while tools.jar is not present, ant tried to lookup build.xml in current directory. Which means ant is running fine. You will need tools.jar only when you decide to use tasks that are accomplished with JDK ex. compilations, javadoc generation etc. For the tasks which don't need JDK ant will work just fine without tools.jar ex. creating directories, copying files, archiving directories etc. java2-compiler can be added as 'Recommends' to ant as javac is in my opinion most frequently used task. But the decision needs to be taken by package maintainers. Onkar Onkar ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Processing of plexus-archiver_1.0~alpha10-1_i386.changes
plexus-archiver_1.0~alpha10-1_i386.changes uploaded successfully to localhost along with the files: plexus-archiver_1.0~alpha10-1.dsc plexus-archiver_1.0~alpha10.orig.tar.gz plexus-archiver_1.0~alpha10-1.diff.gz libplexus-archiver-java_1.0~alpha10-1_all.deb Greetings, Your Debian queue daemon ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Processing of maven-archiver_2.3-1_i386.changes
maven-archiver_2.3-1_i386.changes uploaded successfully to localhost along with the files: maven-archiver_2.3-1.dsc maven-archiver_2.3.orig.tar.gz maven-archiver_2.3-1.diff.gz libmaven-archiver-java_2.3-1_all.deb Greetings, Your Debian queue daemon ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#508363: libaccess-bridge-java: makes openjdk-6-jre-headless depend on openjdk-6-jre
Package: libaccess-bridge-java Version: 1.23.0-3 Severity: important Updating from 1.23.0-2 on a server installation pulls openjdk-6-jre and its dependencies, on a total of almost 100M of packages. openjdk-6-jre-headless depends on libaccess-bridge-java libaccess-bridge-java 1.23.0-2 depends on openjdk-6-jre | cacao-oj6-jre | java5-runtime-headless (openjdk-6-jre-headless provides java5-runtime-headless) but: libaccess-bridge-java 1.23.0-3 depends on default-jre (= 1.5) | openjdk-6-jre | cacao-oj6-jre Marked important since it makes openjdk-6-jre-headless useless; please downgrade if appropriate. Thanks, Wagner -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-6-vserver-686 (SMP w/1 CPU core) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages libaccess-bridge-java depends on: ii openjdk-6-jre-headless [java5 6b11-9 OpenJDK Java runtime, using Hotspo ii sun-java6-jre [java5-runtime- 6-07-4 Sun Java(TM) Runtime Environment ( libaccess-bridge-java recommends no packages. libaccess-bridge-java suggests no packages. -- no debconf information ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Processing of maven-jar-plugin_2.2-1_i386.changes
maven-jar-plugin_2.2-1_i386.changes uploaded successfully to localhost along with the files: maven-jar-plugin_2.2-1.dsc maven-jar-plugin_2.2.orig.tar.gz maven-jar-plugin_2.2-1.diff.gz libmaven-jar-plugin-java_2.2-1_all.deb Greetings, Your Debian queue daemon ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
plexus-io_1.0~alpha2-1_i386.changes is NEW
(new) libplexus-io-java_1.0~alpha2-1_all.deb optional libs Plexus IO Components Plexus IO is a set of plexus components, which are designed for use in I/O operations. These I/O operations are doing nothing spectacular. For example, Apache Commons IO is a much more powerful library in the same area. However, the implementation as a plexus component allows reuse in Maven. . The following component groups are currently available: * File Mappers * File Selectors (new) plexus-io_1.0~alpha2-1.diff.gz optional libs (new) plexus-io_1.0~alpha2-1.dsc optional libs (new) plexus-io_1.0~alpha2.orig.tar.gz optional libs Changes: plexus-io (1.0~alpha2-1) unstable; urgency=low . * Initial release. (Closes: #475726) Override entries for your package: Announcing to [EMAIL PROTECTED] Closing bugs: 475726 Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#279246: S'il vous plait repondez moi vite.
Noukou Robert Matheo Officier de Crédit /Change et Recouvrements des Fonds à la Bank Of Africa (BOA).Ouagadougou Burkina Faso Bonjour, Je m'appelle Mr Noukou Robert Matheo, employé à la Bank Of Africa du Burkina Faso(BOA BF),en tant que officier du département de crédit et de rémittence internationale. Je viens trèsrespectueusement solliciter votre collaboration pour une transaction; En effet, j'ai decouvert la souscription d'un de nos clients décédé depuis 2003. Sans nouvelle des parentsde ce dernier, notre Institution est sur le point de faire de cette souscription le patrimoine de la Banque, mais elle reste prête à effectuer le remboursement à toute personne qui se présenterait comme étant bénéficiaire de ladite souscription et qui fournirait toutes les informations relativesà ce compte. Je vous contacte à présent afin que vous interveniez en tant qu'héritier de cette souscription. Jevous fournirai plus de détails sur l'opération dès que je je recevrai votre accord par rapport à la proposition. Ils'agit de la somme de 11.000 000 dollars US,et j'accepete de vous donnerles 40 % de cette somme,pour votre participation. Je reste optimiste à recevoir une suite favorable à ma proposition.Veuillez me laisser votre contact téléphonique,pour une étroite collaboration. Mr Noukou Robert Matheo. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
maven-jar-plugin_2.2-1_i386.changes is NEW
(new) libmaven-jar-plugin-java_2.2-1_all.deb optional devel Maven Jar plugin Maven is a software project management and comprehension tool. Based on the concept of a project object model (POM), Maven can manage a project's build, reporting and documentation from a central piece of information. . Maven's primary goal is to allow a developer to comprehend the complete state of a development effort in the shortest period of time. In order to attain this goal there are several areas of concern that Maven attempts to deal with: . * Making the build process easy * Providing a uniform build system * Providing quality project information * Providing guidelines for best practices development * Allowing transparent migration to new features . This plugin provides the capability to build and sign jars. (new) maven-jar-plugin_2.2-1.diff.gz optional devel (new) maven-jar-plugin_2.2-1.dsc optional devel (new) maven-jar-plugin_2.2.orig.tar.gz optional devel Changes: maven-jar-plugin (2.2-1) unstable; urgency=low . * Initial release. (Closes: #508316) Override entries for your package: Announcing to [EMAIL PROTECTED] Closing bugs: 508316 Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Re: Packaging eclipse 3.4.1 for debian/ubuntu
On Wed, 10 Dec 2008, Pantelis Koukousoulas wrote: * jsch is already in debian, version 1.37 should be fine and even copying the debian folder to 1.40 seems to work ok so we are fine if we need the latest version too. This is normally the case. So if this package is just in Debian there is even less sense in copying the source. We should make sure that the existing package also provides an eclipse plugin. * icu4j doesn't seem to be in debian but I already have 3.8.1 in my ubuntu ppa: http://launchpad.net/~pktoss/+archive In fact, the work for this was already done by someone wih the nick rockwalrus) I have invited both him and the 2 eclipse teams in ubuntu to join this effort. Sounds reasonable. As for a get-upstream-source target for eclipse's debian/rules I think we can just include the upstream zip file (the sourceIncluded one) verbatim. I think I 've seen this done in other packages. While this might work I do not regard this as the optimal solution. I also did not verified whether the upstream zip files just contains the source or also the binary build result. If the later is the case for my taste we should strip all unneeded parts and provide *only* the source - but I'd like to hear comments on this. OTOH, fedora and gentoo seem to perform a large amount of massage/sanitizing to the source before building: * Remove existing .so files * Lots of misc sed'ing * Fedora has its own launcher sources and a part of ecf too that is needed for building the SDK (ecf-filetransfer). I think these need to go to the * Removing various bundled external jars and symlinking them to their /usr/share/java equivalents Sounds reasonable. Perhaps we might steal some code from there for a get-orig-source target. I wonder what would be the best way to handle this: Should we have a separate script in debian/ that is called by a target in the rules file? Putting all this hackery to a makefile is just awful :-) I always prefer a debian/get-orig-source script (which you might like to call from a shell as an alternative) and call this out of the debian/rules file. For now, going after the goal of just getting 3.4.1 to build ok seems like a good plan. I think so, too. Btw: the gentoo code is in svn co https://overlays.gentoo.org/svn/proj/java/chewi-overlay And the fedora code is in cvs co :pserver:[EMAIL PROTECTED]:/cvs/pkgs/devel/eclipse Would you volunteer to take this as a base for a debian/get-orig-source script? I'd be able to test this and then we should commit it to svn. Kind regards Andreas. -- http://fam-tille.de ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#508358: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: argouml | 0.19.6-2.1 | source, all argouml-doc | 0.19.6-2.1 | all Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are never removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED] This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED] Debian distribution maintenance software pp. Thomas Viehmann (the ftpmaster behind the curtain) ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#508372: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: dresden-ocl | 1.1.debian-2 | source libocl-argo-java | 1.1.debian-2 | all Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are never removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED] This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED] Debian distribution maintenance software pp. Thomas Viehmann (the ftpmaster behind the curtain) ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#508342:
Yes Onkar. You are right. It's working fine without jdk, but it's only getting this warning. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#447951: Plese Depend on or Recommend libsaxon-java
HI, Am Mittwoch, den 10.12.2008, 22:41 +0100 schrieb Joachim Breitner: Hi, I have hit this problem, and it seems it can be solved by libsaxon-java – at least that made it go away here, and the pictures appeared. I don’t know the exacts how and why, but (at least) the png files were affected by this. sorry, it doesn’t help when trying to use openjdk-6-jre, only with sun-java6-jre. I’m going to file a separte bugreport. Maybe this bug here is actually an openjdk bug? Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
