Bug#526489: Time to orphan eclipse? (Bug#526489: eclipse: should this package be orphaned?)
Thanks for dropping an answer... On Mon, Jun 15, 2009 at 06:18:06PM +0200, Matthias Klose wrote: Ana Guerrero schrieb: On Wed, May 20, 2009 at 01:40:49AM +0200, Ana Guerrero wrote: I filed the quoted report almost 3 weeks ago. Resending to people listed as eclipse uploaders in case they did not get it. Third and last warning, I will orphan eclipse next saturday (20th June), so if somebody from the Java team is interested, please step up now. please wait until afer debconf with orphaning the package. there might be some interest. uhm, I fail to see what debconf is going to change with respect this situation :? Usually, I would have orphaned the package already, but I was hoping from somebody from the team take over it. Sadly, I did not get a word from any of the uploaders (a i am not longer interested email would have been nice) or from somebody else from the team. For the record, even if the last version we have in Debian is 3.2.2, there was some work done (from one year ago) in the SVN for the version 3.4: http://svn.debian.org/wsvn/pkg-java/trunk/eclipse/debian/?op=logrev=0sc=0isdir=1 care to help with this? the problem with eclipse is that everybody seems to start his/her own packaging and gets stuck with it. Just doing some QA here, I am not a eclipse user :) Ana ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#526489: eclipse: should this package be orphaned
On Mon, Jun 15, 2009 at 02:41:45PM +0300, Pantelis Koukousoulas wrote: On Mon, Jun 15, 2009 at 2:20 PM, Marcus Bettermar...@better.se wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, From: Ana Guerrero a...@debian.org Third and last warning, I will orphan eclipse next saturday (20th June), Perhaps the right thing to do is simply to have eclipse removed from the archive. It is way too outdated to be useful now, and would require *major* work to update. The major work is essentially equivalent to a rewrite (of the packaging). Different jdk, build system, update management, policy, etc etc. Pretty much the only things left will be the boilerplate (debian/copyright files and such). Removing the eclipse 3.2 from the archive would be fine with me, fwiw, especially if it motivates anyone to contribute towards getting 3.5 in. I think removing directly is not a good idea. It is a widely used application, so I am really hoping somebody gets interested in maintaining it. But if nobody takes over, yes, eventually we should remove it. In the meantime, IMHO it makes sense ask the removal from testing. Ana ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#526489: Time to orphan eclipse? (Bug#526489: eclipse: should this package be orphaned?)
Hi Markus, Jens and list: On Mon, Jun 15, 2009 at 03:52:34PM +0200, Jens Kapitza wrote: Hi, can I be of any help? (I would take it over) I can offer my time but i think i need some help. You could ask to join the java team for maintaining eclipse, so you can commit in the pkg-java's SVN and updating the package. (*) Given the size of eclipse and all its functionalities, only one single maintainer is too few. And even if you all do not manage to fix all the problems, some maintainance is better than none. The main issue is you will always need an interested Debian Developer to sponsor the package. (*) Ask about this in debian-j...@lists.debian.org list. Ana ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#526489: Time to orphan eclipse? (Bug#526489: eclipse: should this package be orphaned?)
I filed the quoted report almost 3 weeks ago. Resending to people listed as eclipse uploaders in case they did not get it. On Fri, May 01, 2009 at 04:33:20PM +0200, Ana Guerrero wrote: Package: eclipse Version: 3.2.2-6.1 Severity: important After being hit by #507536 (merged with #511713, #515747) and read http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507536#104 I have been looking at the status of eclipse in Debian. Eclipse's packaging is under the umbrella of the Debian Java Maintainers, but it is currently lacking of a main maintainer. Latest maintainer upload was almost a year ago (8 May 2008), and the package has missed a few upstream releases (Current version is 3.4.2) since then. I am cc'ing all the people listed in the uploaders field, are you still interested in maintaining eclipse? Ana Original bug report at: http://bugs.debian.org/526489 ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#507536: it does not work here either
On Fri, May 01, 2009 at 05:32:44AM +0300, Pantelis Koukousoulas wrote: Please try openjdk instead of gcj, gcj has never been really reliable for eclipse afaict. The only reason it was pursued was because it has the right license. Now with openjdk, gcj should probably be deprecated (at least for eclipse). I need to use gcj, if eclipse does not work with it, after the line testing /usr/lib/jvm/java-gcj...found it should stop. Also, make sure you have installed xulrunner-dev or the equivalent. If that doesn't work either, then the problem is that unstable has a too new version of xulrunner for eclipse. If i need to install xulrunner-dev then a depend is missing. Mozilla people tend to change the interfaces at will which tends to break eclipse a lot. The most current breakage (also reported as a Fedora bug) is iirc still being discussed in upstream eclipse's bugzilla. then this depende should be versioned :? ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#507536: it does not work here either
On Fri, May 01, 2009 at 05:32:44AM +0300, Pantelis Koukousoulas wrote: Please try openjdk instead of gcj, gcj has never been really reliable for eclipse afaict. The only reason it was pursued was because it has the right license. Now with openjdk, gcj should probably be deprecated (at least for eclipse). Also, make sure you have installed xulrunner-dev or the equivalent. If that doesn't work either, then the problem is that unstable has a too new version of xulrunner for eclipse. Mozilla people tend to change the interfaces at will which tends to break eclipse a lot. The most current breakage (also reported as a Fedora bug) is iirc still being discussed in upstream eclipse's bugzilla. BTW, thanks for the quick help. ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#526489: eclipse: should this package be orphaned?
Package: eclipse Version: 3.2.2-6.1 Severity: important After being hit by #507536 (merged with #511713, #515747) and read http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=507536#104 I have been looking at the status of eclipse in Debian. Eclipse's packaging is under the umbrella of the Debian Java Maintainers, but it is currently lacking of a main maintainer. Latest maintainer upload was almost a year ago (8 May 2008), and the package has missed a few upstream releases (Current version is 3.4.2) since then. I am cc'ing all the people listed in the uploaders field, are you still interested in maintaining eclipse? Ana ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#507536: it does not work here either
severity 507536 serious thanks pure unstable/amd64 system here. I just installed eclipse to test something and I got this problem too. When starting eclipse from command line i got: a...@pryan:$ eclipse searching for compatible vm... testing /usr/lib/jvm/java-6-openjdk...not found testing /usr/lib/jvm/java-gcj...found ***Here it stops and i get a popup message: This Eclipse build doesn't have support for the integrated browser. I accept and it continues ... Could not create /usr/local/lib/eclipse/.eclipseextension. Please run as root: touch /usr/local/lib/eclipse/.eclipseextension chmod 2775 /usr/local/lib/eclipse/.eclipseextension chown root:staff /usr/local/lib/eclipse/.eclipseextension /usr/lib/jvm/java-gcj/bin/java: symbol lookup error: /home/ana/.eclipse/org.eclipse.platform_3.2.0/configuration/org.eclipse.osgi/bundles/46/1/.cp/libswt-mozilla-gtk-3236.so: undefined symbol: _ZN4nsID5ParseEPKc It it the first time I install eclipse (never used it before, really). Ana ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
Bug#400172: cacao: FTBFS on amd64: import java/lang/management/MemoryUsage is not valid
tags 400172 - unreproducible severity 400172 serious thanks On Fri, Nov 24, 2006 at 10:43:35AM +0100, Lucas Nussbaum wrote: Package: cacao Version: 0.97-2 Severity: serious Justification: FTBFS on amd64, already has amd64 binaries in etch Usertags: grid5000 Hi, During a rebuild of all packages in etch, I discovered that your package failed to build on amd64. [...] I can reproduce this problem in a etch/i386 pbuilder. It builds fine in a sid/i386, though. Ana ___ pkg-java-maintainers mailing list pkg-java-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
