Red Hat Bugzilla – Bug 162443
Update to Eclipse 3.1 in FC4
Last modified: 2007-11-30 17:11:09 EST
Just so people know, this is still waiting on the CVS issue fix.
Thanks for the info.
I hope the CVS issues get resolved ASAP, so we can finally have Eclipse 3.1 on FC4.
Hi, next week this bug is going to be 3 months old. Any news regarding this
issue ? For a distro that heavly focused on development (specially in java) I
think this may be too much.
As I said on 1 September (and as is indicated by the dependency tree), this is
waiting on bug 161483.
Please test eclipse-3.1.1-1jpp_1fc.FC4.4 when it appears in updates-testing (see
fedora-announce-list (and/or fedora-test-list)).
# rpm -Fvh eclipse*
error: Failed dependencies:
eclipse-rcp = 1:3.1.1-1jpp_1fc.FC4.4 is needed by
libswt3-gtk2 = 1:3.1.1-1jpp_1fc.FC4.4 is needed by
lucene is needed by eclipse-platform-3.1.1-1jpp_1fc.FC4.4.i386
lucene-demo is needed by eclipse-platform-3.1.1-1jpp_1fc.FC4.4.i386
yum update eclipse-pde (or eclipse-jdt or eclipse-platform or whatever)
That'll bring in the deps you need.
Negative. The mirror at kernel.org does not contain the files and
I refuse to use yum.
Correction: the files do exist in the mirror.
rpm -Fvh is just too stupid to see the files sitting there, so one
must install them manually, then run the rpm -Fvh.
Also, the elipse*rcp* stuff is a fun little tar baby.
(In reply to comment #8)
> I refuse to use yum.
May I ask why?
Sure. I don't need yum. And I don't want to be tracked.
I mirror the updates repository and run an 'rpm -Fvh *.rpm'. I maintain
that this should work without pain.
Sitting in a mirror'ed rpm update repository, FRESHEN should be able to
figure things out and do the right thing. In this case (FCOL!) its a
FRESHEN DEPENDANCY, sitting right there, and its even on the friggin'
command line: 'rpm -Fvh *.rpm'!
If 'rpm -Fvh' worked correctly, things would be easier. But its OK, I
can do it manually. Red Hat is getting more like Microsoft every day.
According to the idiot in charge of maintaining rpm, in response to my bug
report about this issue, my suggestions for improvement, and expectations
for correct and reasonable behaviour of the tool, are not welcome.
I will be considering a move to another distro, and set of tools that
Further, since I have managed up to 150 machines by myself, I think client
access to such a read-only update repository mirror, from which they can
all do an 'rpm -Fvh *.rpm' has a certain network bandwidth good-citizen
type of cache effect.
But if the 'Package Manager' tool is defective, obviously, there will be
annoying and unnecessary problems.