On Sun, 2008-01-20 at 15:51 -0800, Daniel B. Thurman wrote:
Andrew Overholt wrote:
> * Dan Thurman <dant(a)cdkkt.com> [2008-01-11 20:33]:
> > 1) Installing updates:
> > a) First time I installed update as a normal user,
> > I noticed that updates was falling all over itself
> > when it could not write to /usr/share/eclipse nor
> > to /usr/lib/eclipse directory due to permission
> > errors. Ok, so I created a group name, added to
> > that group name a list of allowable "updaters"
> > and chgrp -R, chmod 775, the above directorys.
> > If there is a proper way of doing this please let
> > me know.
> We carry a patch that makes this just work. You should not
> be prompted to install into /usr/share but rather it should
> by default go into ~/.eclipse somewhere.
From what I saw, the default after choosing updates goes to
/usr/share/eclipse unless you change this default. It wasn't
until later I realized this.
I cannot duplicate this. I added the ECF update site  and it
defaulted to ~/.eclipse/<something or other>.
> > b) I wanted to install all of the 'new stuff',
> > BIRT, C/C++, etc., and I quickly discovered that some
> > of the items on the list should be avoided, such as
> > 'change log', and 'The Eclipse Project' patches.
> > Why these are there, I do not know - but they are
> > sure as heck annoying as a newbie if you have no clue.
> > Hey! That's me! ;-/ If you wanted install 'everything',
> > what is the safe way to go about it and what would you
> > choose and what would you avoid? Are there any other
> > 'packages' that are not in the updater list that are
> > also available?
> I'm very confused by what you're trying to accomplish here. Please
What I was trying to accomplish was a successful upgrade and I was
not able to perhaps due to certain choices that was preventing me
from updating these packages. I got into a certain situation in
which some kind of package was installed into my system and yet,
I could not remove it.
I'm still quite confused.
> > c) I know I did not select 'Eclipse Patches',
so why in
> > the heck are these RCP patches appearing in my above
> > mentioned directories?
> What is 'Eclipse Patches'?
+ Help->Software Updates->Find and Install...
<dialog pops up>
+ Select: Search for new features to install
+ Select: The Eclipse Project Updates, Click: Finish
<dialog pops up>
+ Click: '+'
You should see: 'Eclipse 3.3.1' patches
Why are you trying to update files owned by system-installed RPMs? This
will break verification of these RPMs. It also won't work. If you want
to use upstream releases, just download a zip and put it in your home
> > d) I noticed from time to time that when in the middle
> > of an installation, invariably the network drops and
> > there is an incomplete installation. I have had to
> > remove eclipse and start over especially when the
> > the configuration is a mess. Maybe I am going
> > about this in the wrong way - but what is your advice?
> Are you running Fedora Eclipse or an upstream download?
What is odd, that originally, the download site starts out small
but after selecting many packages, the original list has expanded
out to include each of the new group packages and the list is long.
What is annoying is that now if you choose to install new packages
it is not obvious what they now are - so you are navigating a land
mind - not knowing where to step. Since I had navigated each and
every package, one at a time, I got various errors:
This sounds like you don't like the Eclipse Update Manager. You're not
alone in this :)
Network connection problems during search.
Unable to access
Error parsing site stream. [Premature end of file].
Premature end of file
- Above two lines repeated once again.
+ EMF SDO:
Unable to complete action for feature: "Eclipse Modeling Framework
(EMF) Examples" Due to errors.
- Unable to create file "null".
[/tmp/1427<blah,blah>/eclipse.38531.tmp (too many open files.)]
- 3 more lines similiar to above- too many open files error.
Seems that a lot of the sites I picked was similar to BIRT above.
Premature end of file stream. Maybe that simply means there is
nothing new to update but I am guessing here.
These all seem like upstream project (BIRT, whatever) issues. Or
network issues. If you can track down specific Fedora Eclipse issues,
it would be great if you could file bugs at bugzilla.redhat.com
I even had several outright crashes of the Fedora Eclipse, just
boom - crash. No warning. Strange.
That sounds like a VM crash.
> > e) I was playing around and clicked Help->Welcome
> > toobar menu item, and boom! It killed the eclipse
> > IDE, everytime I tried it. Bug?
> I've never experienced this. If you're running Fedora Eclipse, feel
> free to file a bug with all the relevant info (which VM, which arch,
> output of for f in `rpm -qa | egrep "swt|eclipse"; do rpm -qV
> $f && echo
> $f; done, etc.)
for f in `rpm -qa | egrep "swt|eclipse"`; do
rpm -qV $f && echo $f;
Ok, here it is:
It looks like you have a lot of files that have changed on disk since
their RPM installation. I don't know what to say about that except that
it *could* be affecting your installation. As per usual with eclipse
stuff, try with different VMs, with the -clean startup option, with a
new workspace with ~/.eclipse out of the way without any 3rd party
plugins, etc., etc. If you can reliably reproduce issues, file bugs in
Red Hat bugzilla and people can take a look.