From bugmaster at FreeBSD.org Mon Jan 5 11:06:49 2009 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Jan 5 11:07:35 2009 Subject: Current problem reports assigned to freebsd-eclipse@FreeBSD.org Message-ID: <200901051106.n05B6m33002728@freefall.freebsd.org> Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o ports/129323 eclipse [PATCH] java/eclipse-webtools: update to 2.0.3 o ports/129321 eclipse [PATCH] java/eclipse-emf: update to 2.3.2 o ports/129320 eclipse [PATCH] java/eclipse-gef: update to 3.3.2 3 problems total. From glewis at FreeBSD.org Sat Jan 10 17:55:28 2009 From: glewis at FreeBSD.org (glewis@FreeBSD.org) Date: Sat Jan 10 17:55:35 2009 Subject: ports/129320: [PATCH] java/eclipse-gef: update to 3.3.2 Message-ID: <200901110155.n0B1tRTa005025@freefall.freebsd.org> Synopsis: [PATCH] java/eclipse-gef: update to 3.3.2 State-Changed-From-To: open->closed State-Changed-By: glewis State-Changed-When: Sun Jan 11 01:55:27 UTC 2009 State-Changed-Why: Committed. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=129320 From dfilter at FreeBSD.ORG Sat Jan 10 18:00:17 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sat Jan 10 18:00:23 2009 Subject: ports/129320: commit references a PR Message-ID: <200901110200.n0B20HA3005176@freefall.freebsd.org> The following reply was made to PR ports/129320; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/129320: commit references a PR Date: Sun, 11 Jan 2009 01:55:22 +0000 (UTC) glewis 2009-01-11 01:55:10 UTC FreeBSD ports repository Modified files: java/eclipse-gef Makefile distinfo Log: . Update to 3.3.2. PR: 129320 Submitted by: lioux@ Revision Changes Path 1.13 +4 -5 ports/java/eclipse-gef/Makefile 1.10 +3 -3 ports/java/eclipse-gef/distinfo _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From glewis at FreeBSD.org Sat Jan 10 18:05:22 2009 From: glewis at FreeBSD.org (glewis@FreeBSD.org) Date: Sat Jan 10 18:05:28 2009 Subject: ports/129321: [PATCH] java/eclipse-emf: update to 2.3.2 Message-ID: <200901110205.n0B25KKY012130@freefall.freebsd.org> Synopsis: [PATCH] java/eclipse-emf: update to 2.3.2 State-Changed-From-To: open->closed State-Changed-By: glewis State-Changed-When: Sun Jan 11 02:05:20 UTC 2009 State-Changed-Why: Committed. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=129321 From dfilter at FreeBSD.ORG Sat Jan 10 18:10:03 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sat Jan 10 18:10:10 2009 Subject: ports/129321: commit references a PR Message-ID: <200901110210.n0B2A324012220@freefall.freebsd.org> The following reply was made to PR ports/129321; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/129321: commit references a PR Date: Sun, 11 Jan 2009 02:05:15 +0000 (UTC) glewis 2009-01-11 02:05:03 UTC FreeBSD ports repository Modified files: java/eclipse-emf Makefile distinfo Log: . Update to 2.3.2 PR: 129321 Submitted by: lioux@ Revision Changes Path 1.15 +3 -4 ports/java/eclipse-emf/Makefile 1.11 +3 -3 ports/java/eclipse-emf/distinfo _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From glewis at FreeBSD.org Sat Jan 10 20:31:51 2009 From: glewis at FreeBSD.org (glewis@FreeBSD.org) Date: Sat Jan 10 20:31:58 2009 Subject: ports/129323: [PATCH] java/eclipse-webtools: update to 2.0.3 Message-ID: <200901110431.n0B4VpD5024913@freefall.freebsd.org> Synopsis: [PATCH] java/eclipse-webtools: update to 2.0.3 State-Changed-From-To: open->closed State-Changed-By: glewis State-Changed-When: Sun Jan 11 04:31:50 UTC 2009 State-Changed-Why: Committed. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=129323 From dfilter at FreeBSD.ORG Sat Jan 10 20:40:03 2009 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sat Jan 10 20:40:10 2009 Subject: ports/129323: commit references a PR Message-ID: <200901110440.n0B4e3a6026253@freefall.freebsd.org> The following reply was made to PR ports/129323; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: ports/129323: commit references a PR Date: Sun, 11 Jan 2009 04:31:41 +0000 (UTC) glewis 2009-01-11 04:31:32 UTC FreeBSD ports repository Modified files: java/eclipse-webtools Makefile distinfo Log: . Update to 2.0.3. PR: 129323 Submitted by: lioux@ Revision Changes Path 1.7 +6 -8 ports/java/eclipse-webtools/Makefile 1.4 +3 -3 ports/java/eclipse-webtools/distinfo _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From QAT at FreeBSD.org Sat Jan 17 20:25:35 2009 From: QAT at FreeBSD.org (QAT@FreeBSD.org) Date: Sat Jan 17 20:25:41 2009 Subject: java/eclipse-webtools - fails: mtree Message-ID: <20090118040006.E03AD8FC48@release.ixsystems.com> Hi, Excerpt from http://QAT.TecNik93.com/logs/7-STABLE-FPT-NPD/eclipse-webtools-2.0.3.log : building eclipse-webtools-2.0.3 in directory /usr/local/tinderbox/7-STABLE-FPT-NPD maintained by: freebsd-eclipse@FreeBSD.org building for: 7.1-STABLE amd64 Makefile ident: $FreeBSD: ports/java/eclipse-webtools/Makefile,v 1.7 2009/01/11 04:31:32 glewis Exp $ port directory: /usr/ports/java/eclipse-webtools ................................................... skipping mkfontscale-1.0.3, already added pkg_add gnome-doc-utils-0.14.2.tbz skipping gnome-doc-utils-0.14.2, already added pkg_add libfontenc-1.0.4.tbz skipping libfontenc-1.0.4, already added pkg_add py25-libxml2-2.7.2.tbz skipping py25-libxml2-2.7.2, already added pkg_add docbook-xml-4.3.tbz skipping docbook-xml-4.3, already added pkg_add docbook-xml-4.4.tbz skipping docbook-xml-4.4, already added pkg_add eclipse-3.3.2.tbz pkg_add eclipse-emf-2.3.2.tbz pkg_add eclipse-gef-3.3.2.tbz ===> Installing for eclipse-webtools-2.0.3 ===> eclipse-webtools-2.0.3 depends on executable: eclipse - found ===> eclipse-webtools-2.0.3 depends on file: /usr/local/eclipse/features/org.eclipse.emf_2.3.2.v200802051830/feature.xml - found ===> eclipse-webtools-2.0.3 depends on file: /usr/local/eclipse/features/org.eclipse.gef_3.3.2.v20080129/feature.xml - found ===> eclipse-webtools-2.0.3 depends on file: /usr/local/diablo-jdk1.6.0/bin/java - found ===> Generating temporary packing list ===> Checking if java/eclipse-webtools already installed ===> Registering installation for eclipse-webtools-2.0.3 ================================================================ ======================================== ===> Building package for eclipse-webtools-2.0.3 Creating package /tmp/packages/All/eclipse-webtools-2.0.3.tbz Registering depends: eclipse-emf-2.3.2 eclipse-gef-3.3.2 eclipse-3.3.2 libgnomeui-2.24.0 libbonoboui-2.24.0 libgnome-2.24.1 gnome-vfs-2.24.0 gvfs-1.0.3 gnome-mount-0.8_2 policykit-gnome-0.9.2 gnome-keyring-2.24.1_1 gconf2-2.24.0 libgnomecanvas-2.20.1.1_2 libglade2-2.6.3 gnome-icon-theme-2.24.0_2 libnotify-0.4.5 xulrunner-1.8.0.4_14 gtk-2.14.7 atk-1.24.0 zip-3.0 libcdio-0.78.2_2 cdparanoia-3.9.8_8 esound-0.2.41 libaudiofile-0.2.6 libcddb-1.3.0 libbonobo-2.24.0 ORBit2-2.14.16 libIDL-0.8.12 shared-mime-info-0.51 pango-1.22.4 hal-0.5.11_11 consolekit-0.3.0_3 policykit-0.9_2 avahi-app-0.6.24 dbus-glib-0.78 libsoup-2.24.3 desktop-file-utils-0.15_1 gio-fam-backend-2.18.4 gamin-0.1.10 glib-2.18.4 gnome-mime-data-2.18.0_3 popt-1.7_5 gnome-doc-utils-0.14.2 rarian-0.8.1 bash-3.2.48_1 getopt-1.1.4_1 libgphoto2-2.4.3 libexif-0.6.17 gnutls-2.6.3 libgcrypt-1.4.3 libgpg-error-1.6_1 gettext-0.17_1 dbus-1.2.4.4 libxslt-1.1.24_2 py25-libxml2-2.7.2 libxml2-2.7.2_1 samba-libsmbclient-3.0.32_3 fus efs-libs-2.7.3 libiconv-1.11_1 gdbm-1.8.3_3 libdaemon-0.12 libltdl-1.5.26 cairo-1.8.6,1 xcb-util-0.3.0 libxcb-1.1.90.1 libpthread-stubs-0.1 libusb-0.1.12_4 libvolume_id-0.81.0 nss-3.11.9_2 nspr-4.7 pcre-7.8 pixman-0.12.0 xorg-fonts-truetype-7.3 bitstream-vera-1.10_4 font-bh-ttf-1.0.0 font-misc-meltho-1.0.0_1 font-misc-ethiopic-1.0.0 libXft-2.1.13 fontconfig-2.6.0,1 mkfontdir-1.0.3_1 mkfontscale-1.0.3 freetype2-2.3.7 libXcursor-1.1.9_1 libXrandr-1.2.2_1 libXrender-0.9.4_1 libGLU-7.0.3 libGL-7.0.3 libXdamage-1.1.1 libXcomposite-0.4.0,1 libXfixes-4.0.3_1 libXxf86vm-1.0.1 libXi-1.1.3,1 libXmu-1.0.3,1 libXinerama-1.0.2,1 libXpm-3.5.7 libXext-1.0.3,1 libXt-1.0.5_1 startup-notification-0.9_2 libX11-1.1.3_1,1 libXau-1.0.3_2 libXdmcp-1.0.2_1 libSM-1.0.3_1,1 libICE-1.0.4_1,1 libfontenc-1.0.4 diablo-jdk-1.6.0.07.02_3 xproto-7.0.10_1 libart_lgpl-2.3.20,1 libtasn1-1.5 pkg-config-0.23_1 jasper-1.900.1_6 tiff-3.8.2_2 jpeg-6b_7 libdrm-2.3.1 png-1.2.34 javavmwrapper-2.3.2 perl-5.8.9 xcb-prot o-1.2 python25-2.5.2_3 gnomehier-2.3_11 hicolor-icon-theme-0.10_2 pciids-20081012 dmidecode-2.10 fusefs-kmod-0.3.9.p1.20080208_5 gnome_subr-1.0 docbook-sk-4.1.2_4 docbook-xsl-1.74.0 docbook-xml-4.2_1 docbook-xml-4.3 docbook-xml-4.4 expat-2.0.1 sdocbook-xml-1.1,1 xmlcatmgr-2.2 encodings-1.0.2,1 font-util-1.0.1 compositeproto-0.4 damageproto-1.1.0_2 fixesproto-4.0 inputproto-1.4.2.1 kbproto-1.0.3 randrproto-1.2.1 renderproto-0.9.3 xextproto-7.0.2 xf86vidmodeproto-2.2.2 xineramaproto-1.1.2. Registering conflicts: eclipse-lomboz-3.*. Creating bzip'd tar ball in '/tmp/packages/All/eclipse-webtools-2.0.3.tbz' Deleting eclipse-webtools-2.0.3 ================================================================ === Checking filesystem state list of files present before this port was installed but missing after it was deinstalled) ./usr/local/eclipse/plugins/javax.servlet.jsp_2.0.0.v200706191603.jar missing ./usr/local/eclipse/plugins/javax.servlet_2.4.0.v200706111738.jar missing ./usr/local/eclipse/plugins/org.apache.commons.el_1.0.0.v200706111724.jar missing ./usr/local/eclipse/plugins/org.apache.commons.logging_1.0.4.v200706111724.jar missing ================================================================ build of /usr/ports/java/eclipse-webtools ended at Sun Jan 18 04:00:05 UTC 2009 The tarballed WRKDIR can be found here: http://QAT.TecNik93.com/wrkdirs/7-STABLE-FPT-NPD/eclipse-webtools-2.0.3.tbz PortsMon page for the port: http://portsmon.freebsd.org/portoverview.py?category=java&portname=eclipse-webtools The build which triggered this BotMail was done under tinderbox-3.1.2_1; dsversion: 3.1 on RELENG_7 on amd64 with tinderd_flags="-nullfs -plistcheck -onceonly" and ccache support, with the "official" up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. A description of the testing process can be found here: http://T32.TecNik93.com/FreeBSD/QA-Tindy/ Thanks for your work on making FreeBSD better, -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" FreeBSD committer -> itetcu@FreeBSD.org, PGP Key ID 057E9F8B493A297B From glewis at eyesbeyond.com Sat Jan 24 21:57:00 2009 From: glewis at eyesbeyond.com (Greg Lewis) Date: Sat Jan 24 21:57:07 2009 Subject: Eclipse plugins ports? Message-ID: <20090125051928.GA86858@misty.eyesbeyond.com> G'day all, I'm looking into a problem with one of the Eclipse plugin ports and I have to say that I wonder why we bother having plugin ports. Eclipse has good built in plugin management tools, so the only reason I can see for having a port for one is if there is some code that needs changes (and the only one of those I see is eclipse-cdt). What are peoples thoughts on this? Who feels they get a lot of value out of having FreeBSD ports for those plugins that we do have and why? -- Greg Lewis Email : glewis@eyesbeyond.com Eyes Beyond Web : http://www.eyesbeyond.com Information Technology FreeBSD : glewis@FreeBSD.org From mbowie at buzmo.com Sat Jan 24 22:31:32 2009 From: mbowie at buzmo.com (Mike Bowie) Date: Sat Jan 24 22:31:38 2009 Subject: Eclipse plugins ports? In-Reply-To: <20090125051928.GA86858@misty.eyesbeyond.com> References: <20090125051928.GA86858@misty.eyesbeyond.com> Message-ID: <497C00FB.1070204@buzmo.com> Greg Lewis wrote: > G'day all, > > I'm looking into a problem with one of the Eclipse plugin ports and I have > to say that I wonder why we bother having plugin ports. Eclipse has good > built in plugin management tools, so the only reason I can see for having > a port for one is if there is some code that needs changes (and the only > one of those I see is eclipse-cdt). > > What are peoples thoughts on this? Who feels they get a lot of value out > of having FreeBSD ports for those plugins that we do have and why? > G'day indeed Greg, Nice to hear from you. If you recall or review a few of my prior posts on the matter, you'll find I was wondering the same thing. I myself don't see the point at this, uh, point, besides the minor patches to CDT, everything else is somewhat redundant and only serves to cause confusion. Cheers, Mike. -- "You don't see FreeBSD developers sitting in a smoke-filled room plotting the overthrow of Microsoft. We sit in light, airy rooms and plot where to get the best drinks." - Michael Lucas From linimon at FreeBSD.org Mon Jan 26 00:16:39 2009 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Mon Jan 26 00:16:46 2009 Subject: FreeBSD ports that you maintain which are currently marked broken Message-ID: <20090126081638.83F121CCA5@mail.droso.net> Dear FreeBSD port maintainer: As part of an ongoing effort to reduce the number of problems in the FreeBSD ports system, we periodically notify users of ports that are marked as "broken" in their Makefiles. In many cases these ports are failing to compile on some subset of the FreeBSD build environments. The most common problem is that recent versions of -CURRENT include gcc4.2, which is much stricter than older versions. The next most common problem is that compiles succeed on the i386 architecture (e.g. the common Intel PC), but fail on one or more of the other architectures due to assumptions about things such as size of various types, byte-alignment issues, and so forth. In occasional cases we see that the same port may have different errors in different build environments. The script that runs on the build cluster uses heuristics to try to 'guess' the error type to help you isolate problems, but it is only a rough guide. One more note: on occasion, there are transient build errors seen on the build farm. Unfortunately, there is not yet any way for this algorithm to tell the difference (humans are much, much better at this kind of thing.) The errors are listed below. In the case where the same problem exists on more than one build environment, the URL points to the latest errorlog for that type. (By 'build environment' here we mean 'combination of 5.x/6.x/-current with target architecture'.) (Note: the dates are included to help you to gauge whether or not the error still applies to the latest version. The program that generates this report is not yet able to determine this automatically.) portname: java/eclipse-webtools broken because: deletes files installed by dependency on deinstall build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20090113074140/eclipse-webtools-2.0.3.log (Sat Jan 17 10:03:13 UTC 2009) overview: http://portsmon.FreeBSD.org/portoverview.py?category=java&portname=eclipse-webtools If these errors are ones that you are already aware of, please accept our apologies and ignore this message. On the other hand, if you no longer wish to maintain this port (or ports), please reply with a message stating that, and accept our thanks for your efforts in the past. Every effort has been made to make sure that these error reports really do correspond to a port that you maintain. However, due to the fact that this is an automated process, it may indeed generate false matches. If one of these errors fits that description, please forward this email to the author of this software, Mark Linimon , so that he can attempt to fix the problem in the future. Thanks for your efforts to help improve FreeBSD. From sepotvin at videotron.ca Mon Jan 26 13:18:07 2009 From: sepotvin at videotron.ca (Stephane E. Potvin) Date: Mon Jan 26 13:18:16 2009 Subject: Eclipse plugins ports? In-Reply-To: <20090125051928.GA86858@misty.eyesbeyond.com> References: <20090125051928.GA86858@misty.eyesbeyond.com> Message-ID: <497E262F.6060900@videotron.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Greg Lewis wrote: > G'day all, > > I'm looking into a problem with one of the Eclipse plugin ports and I have > to say that I wonder why we bother having plugin ports. Eclipse has good > built in plugin management tools, so the only reason I can see for having > a port for one is if there is some code that needs changes (and the only > one of those I see is eclipse-cdt). > > What are peoples thoughts on this? Who feels they get a lot of value out > of having FreeBSD ports for those plugins that we do have and why? > +1, As this is the main reason that eclipse-devel is still -devel, I wholeheartedly support removing the plugins (except those that require native libraries, like cdt). Most eclipse problems that I've received would have been avoided if people had used eclipse-devel in the first place. As for CDT 5.0, even the missing native libraries are not that critical. Some minor functionalities are not working right and the integration with the toolchain leaves much to be desired but the functionality is there and is working properly in the majority of cases. Regards, Steph (eclipse-devel maintainer hat) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl+Ji8ACgkQmdOXtTCX/nttCQCguE2QUYSg9oqOp/+5+oiNOPdO VCMAoOsnuSvHBwLu5ON4/9FpTs50AanU =HnHb -----END PGP SIGNATURE----- From rick-freebsd2008 at kiwi-computer.com Mon Jan 26 13:51:58 2009 From: rick-freebsd2008 at kiwi-computer.com (Rick C. Petty) Date: Mon Jan 26 13:52:04 2009 Subject: Eclipse plugins ports? In-Reply-To: <20090125051928.GA86858@misty.eyesbeyond.com> References: <20090125051928.GA86858@misty.eyesbeyond.com> Message-ID: <20090126212515.GA85635@keira.kiwi-computer.com> On Sat, Jan 24, 2009 at 09:19:28PM -0800, Greg Lewis wrote: > > I'm looking into a problem with one of the Eclipse plugin ports and I have > to say that I wonder why we bother having plugin ports. Eclipse has good > built in plugin management tools, so the only reason I can see for having > a port for one is if there is some code that needs changes (and the only > one of those I see is eclipse-cdt). > > What are peoples thoughts on this? Who feels they get a lot of value out > of having FreeBSD ports for those plugins that we do have and why? IIRC, in the original discussion we wanted to get rid of all eclipse plugins as ports and use Eclipse's plugin management system. However there were some patches against some of these plugins. My suggestion was to push those patches upstream and remove the plugins from our ports. As to the removal of old eclipse versions, I think it would be nice if we could keep legacy ones around. For example, I use 3.2.1 because of a missing feature in later versions. perhaps eclipse-32 for this port and similar names for the others. The most recent released eclipse should always be eclipse and the snapshots should be eclipse-devel. No one has put the effort into making all these changes. Also I think eclipse-* should be in devel instead of java (as its primary location; it can remain in java as an auxiliary category), but that's another story. -- Rick C. Petty From sepotvin at videotron.ca Mon Jan 26 14:11:12 2009 From: sepotvin at videotron.ca (Stephane E. Potvin) Date: Mon Jan 26 14:11:18 2009 Subject: Eclipse plugins ports? In-Reply-To: <20090126212515.GA85635@keira.kiwi-computer.com> References: <20090125051928.GA86858@misty.eyesbeyond.com> <20090126212515.GA85635@keira.kiwi-computer.com> Message-ID: <497E34F4.5050608@videotron.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Rick C. Petty wrote: > On Sat, Jan 24, 2009 at 09:19:28PM -0800, Greg Lewis wrote: >> I'm looking into a problem with one of the Eclipse plugin ports and I have >> to say that I wonder why we bother having plugin ports. Eclipse has good >> built in plugin management tools, so the only reason I can see for having >> a port for one is if there is some code that needs changes (and the only >> one of those I see is eclipse-cdt). >> >> What are peoples thoughts on this? Who feels they get a lot of value out >> of having FreeBSD ports for those plugins that we do have and why? > > IIRC, in the original discussion we wanted to get rid of all eclipse > plugins as ports and use Eclipse's plugin management system. However there > were some patches against some of these plugins. My suggestion was to push > those patches upstream and remove the plugins from our ports. > > As to the removal of old eclipse versions, I think it would be nice if we > could keep legacy ones around. For example, I use 3.2.1 because of a > missing feature in later versions. perhaps eclipse-32 for this port and > similar names for the others. The most recent released eclipse should > always be eclipse and the snapshots should be eclipse-devel. No one has > put the effort into making all these changes. > > Also I think eclipse-* should be in devel instead of java (as its primary > location; it can remain in java as an auxiliary category), but that's > another story. > I originally planned to have the eclipse 3.4 port named eclipse-ganymede and have eclipse 3.3 renamed eclipse-europa. But Greg preferred to have only one version of eclipse at any given time. This way it's easier for the users as they know that by installing eclipse they get the latest one (instead of having to chose between eclipse-europa, eclipse-ganymede, eclipse-gelileo, eclipse-savor-of-the-day). I admit that eclipse is currently lagging behind and that eclipse-devel should already have been switched as the main eclipse port and I accept full responsibility for that. I've been bogged down with other issues and have not had the time to convert/test all the plugins to the new p2 framework so they integrate correctly with Ganymede. Greg's proposition to remove the plugins will greatly facilitate my work and enable me to concentrate on finishing the CDT port and switching eclipse-devel to Galileo. Regards, Steph -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl+NPQACgkQmdOXtTCX/nvqfgCg6FV+KeOG8IIZBNYTVo/M1rhd X4MAniB8PoCNV9iOLQ0rndDyHV3Jr+w+ =zwSx -----END PGP SIGNATURE----- From vova at fbsd.ru Tue Jan 27 07:36:25 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Tue Jan 27 07:36:32 2009 Subject: eclipse-devel does not works after recent upgrade Message-ID: <1233067889.1659.50.camel@localhost> Hi After recent upgrade (gnome, xorg) eclipse-devel does not works any more it shows splash screen, then hide it, then show again and so on in infinite loop. In logs there is: !SESSION 2009-01-27 16:26:00.539 ----------------------------------------------- eclipse.buildId=M20080911-1700 java.version=1.6.0_03-p4 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=freebsd, ARCH=x86, WS=gtk, NL=ru_RU Command-line arguments: -os freebsd -ws gtk -arch x86 !ENTRY org.eclipse.osgi 4 0 2009-01-27 16:26:01.912 !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar/ [1] is not active. Same time $ zip -T /usr/local/eclipse-devel/plugins/org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar test of /usr/local/eclipse-devel/plugins/org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar OK $ If I remove .eclipse - new, fresh version of eclipse works just fine, but I loose all installed plugins and configuration. $ diff -u .eclipse/1767688504/configuration/config.ini .eclipse.new/1767688504/configuration/config.ini --- .eclipse/1767688504/configuration/config.ini 2009-01-27 16:25:52.000000000 +0300 +++ .eclipse.new/1767688504/configuration/config.ini 2009-01-27 16:13:59.000000000 +0300 @@ -1,4 +1,3 @@ -#This configuration file was written by: org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxFwConfigFileParser -#Fri Dec 12 10:46:15 MSK 2008 +#Linked configuration +#Tue Jan 27 16:13:59 MSK 2009 osgi.sharedConfiguration.area=file\:configuration/ -osgi.bundles=reference\:file\:../../../home/vova/.eclipse/1767688504/plugins/org.eclipse.equinox.transforms.hook_1.0.0.v20080610.jar@4,reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar@1\:start $ Any hints how to make it work without loosing configuration ? -- Vladimir B. Grebenschikov vova@fbsd.ru From sepotvin at videotron.ca Tue Jan 27 09:05:35 2009 From: sepotvin at videotron.ca (Stephane E. Potvin) Date: Tue Jan 27 09:05:42 2009 Subject: eclipse-devel does not works after recent upgrade In-Reply-To: <1233067889.1659.50.camel@localhost> References: <1233067889.1659.50.camel@localhost> Message-ID: <497F3C7B.2090607@videotron.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Vladimir Grebenschikov wrote: > Hi > > After recent upgrade (gnome, xorg) > eclipse-devel does not works any more > > it shows splash screen, then hide it, then show again and so on in infinite loop. > > In logs there is: > > !SESSION 2009-01-27 16:26:00.539 ----------------------------------------------- > eclipse.buildId=M20080911-1700 > java.version=1.6.0_03-p4 > java.vendor=Sun Microsystems Inc. > BootLoader constants: OS=freebsd, ARCH=x86, WS=gtk, NL=ru_RU > Command-line arguments: -os freebsd -ws gtk -arch x86 > > !ENTRY org.eclipse.osgi 4 0 2009-01-27 16:26:01.912 > !MESSAGE Bundle initial@reference:file:plugins/org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar/ [1] is not active. > > > Same time > $ zip -T /usr/local/eclipse-devel/plugins/org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar > test of /usr/local/eclipse-devel/plugins/org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar OK > $ > > If I remove .eclipse - new, fresh version of eclipse works just fine, but I loose all installed plugins and configuration. > > $ diff -u .eclipse/1767688504/configuration/config.ini .eclipse.new/1767688504/configuration/config.ini > --- .eclipse/1767688504/configuration/config.ini 2009-01-27 16:25:52.000000000 +0300 > +++ .eclipse.new/1767688504/configuration/config.ini 2009-01-27 16:13:59.000000000 +0300 > @@ -1,4 +1,3 @@ > -#This configuration file was written by: org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxFwConfigFileParser > -#Fri Dec 12 10:46:15 MSK 2008 > +#Linked configuration > +#Tue Jan 27 16:13:59 MSK 2009 > osgi.sharedConfiguration.area=file\:configuration/ > -osgi.bundles=reference\:file\:../../../home/vova/.eclipse/1767688504/plugins/org.eclipse.equinox.transforms.hook_1.0.0.v20080610.jar@4,reference\:file\:org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar@1\:start > $ > > > Any hints how to make it work without loosing configuration ? > This is weird... As I've not yet done the jump to the new Xorg so I can't be sure that it will work out of the box but I would not have expected it to cause any problems. The problem that you are reporting doesn't seems to be caused by the switch to Xorg. Can you confirm that you didn't install any new plugin around the time you upgraded to thew new Xorg? Your osgi.bundles property doesn't seems quite right. The org.eclipse.equinox.transform.hook reference should normally be listed in a osgi.framework.extensions property. The osgi.bundles should have a reference to the actual transforms that you are using (like org.eclipse.equinox.transforms.xslt for example). You could try to remove the osgi.bundles property of your config.ini file. This should give you back most of your plugins but I guess that the plugin that added this funny line will probably won't work. I'll update a scratch box to the new Xorg and check whether it works correctly just in case I'm digressing with the transform hook part. Steph -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkl/PHoACgkQmdOXtTCX/nsk2gCgirPKGKQhTvWnsazIVhyd30zR qBsAn1JzKEzGvn0AYgxydqAUZLcd4cOy =x12e -----END PGP SIGNATURE----- From vova at fbsd.ru Tue Jan 27 09:05:52 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Tue Jan 27 09:06:02 2009 Subject: eclipse-devel does not works after recent upgrade In-Reply-To: <497F3C7B.2090607@videotron.ca> References: <1233067889.1659.50.camel@localhost> <497F3C7B.2090607@videotron.ca> Message-ID: <1233075947.1659.82.camel@localhost> > This is weird... > > As I've not yet done the jump to the new Xorg so I can't be sure that it > will work out of the box but I would not have expected it to cause any > problems. The problem that you are reporting doesn't seems to be caused > by the switch to Xorg. Can you confirm that you didn't install any new > plugin around the time you upgraded to thew new Xorg? Yes, I do not change anything in plugins while upgrade. > Your osgi.bundles property doesn't seems quite right. The > org.eclipse.equinox.transform.hook reference should normally be listed > in a osgi.framework.extensions property. The osgi.bundles should have a > reference to the actual transforms that you are using (like > org.eclipse.equinox.transforms.xslt for example). > > You could try to remove the osgi.bundles property of your config.ini > file. This should give you back most of your plugins but I guess that > the plugin that added this funny line will probably won't work. I've tried, for my surprise, it starts, but looks like all configuration (with installed plugins) was lost. > I'll update a scratch box to the new Xorg and check whether it works > correctly just in case I'm digressing with the transform hook part. Probably it does not related to Xorg upgrade but related to Gnome upgrade ? As far as I remember there was an command line option for eclipse to reset configuration somehow. Unfortunately I can't remember exact spelling. Probably this may help ? > Steph -- Vladimir B. Grebenschikov vova@fbsd.ru From mbowie at buzmo.com Tue Jan 27 09:41:44 2009 From: mbowie at buzmo.com (Mike Bowie) Date: Tue Jan 27 09:41:51 2009 Subject: eclipse-devel does not works after recent upgrade In-Reply-To: <1233075947.1659.82.camel@localhost> References: <1233067889.1659.50.camel@localhost> <497F3C7B.2090607@videotron.ca> <1233075947.1659.82.camel@localhost> Message-ID: <497F4115.6010800@buzmo.com> Vladimir Grebenschikov wrote: > > As far as I remember there was an command line option for eclipse to > reset configuration somehow. Unfortunately I can't remember exact > spelling. Probably this may help ? > eclipse -clean ? Mike. -- "You don't see FreeBSD developers sitting in a smoke-filled room plotting the overthrow of Microsoft. We sit in light, airy rooms and plot where to get the best drinks." - Michael Lucas From vova at fbsd.ru Tue Jan 27 15:01:23 2009 From: vova at fbsd.ru (Vladimir Grebenschikov) Date: Tue Jan 27 15:01:35 2009 Subject: eclipse-devel does not works after recent upgrade In-Reply-To: <497F4115.6010800@buzmo.com> References: <1233067889.1659.50.camel@localhost> <497F3C7B.2090607@videotron.ca> <1233075947.1659.82.camel@localhost> <497F4115.6010800@buzmo.com> Message-ID: <1233097268.2181.2.camel@localhost> On Tue, 2009-01-27 at 09:15 -0800, Mike Bowie wrote: > Vladimir Grebenschikov wrote: > > > > > As far as I remember there was an command line option for eclipse to > > reset configuration somehow. Unfortunately I can't remember exact > > spelling. Probably this may help ? > > > > eclipse -clean ? Unfortunately it does not helps. > Mike. -- Vladimir B. Grebenschikov vova@fbsd.ru From sepotvin at videotron.ca Sat Jan 31 06:03:45 2009 From: sepotvin at videotron.ca (Stephane E. Potvin) Date: Sat Jan 31 06:03:52 2009 Subject: eclipse-devel does not works after recent upgrade In-Reply-To: <1233097268.2181.2.camel@localhost> References: <1233067889.1659.50.camel@localhost> <497F3C7B.2090607@videotron.ca> <1233075947.1659.82.camel@localhost> <497F4115.6010800@buzmo.com> <1233097268.2181.2.camel@localhost> Message-ID: <49844C17.6070700@videotron.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Vladimir Grebenschikov wrote: > On Tue, 2009-01-27 at 09:15 -0800, Mike Bowie wrote: >> Vladimir Grebenschikov wrote: >> >>> As far as I remember there was an command line option for eclipse to >>> reset configuration somehow. Unfortunately I can't remember exact >>> spelling. Probably this may help ? >>> >> eclipse -clean ? > > Unfortunately it does not helps. > I found out what's happening. It seems that p2 doesn't like when eclipse's timestamp are earlier than the timestamps recorded in the .eclipse directory. When you upgraded to Xorg 7.4, eclipse was reinstalled, which changed the timestamps. As a workaround, you can run the following command which should fix the problem: find ~/.eclipse -exec touch {} \; I have no idea yet why it's doing this though. Steph -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.10 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmETBcACgkQmdOXtTCX/nveXgCguSOoqxLguyjiQPBYxDI+bQEh 5xkAnReSPabXgV3a4zlWvEGaoM+23hgy =PZjb -----END PGP SIGNATURE-----