Created attachment 521221 [details]
eclipse --consolelog --debug
The eclipse-pydev environment is excluded by Eclipse after update. Root cause is determined to be related to the different versions of eclipse-pydev included.
the plugin eclipse-pydev.x86_64, version 1.6.5 is upgraded to eclipse-pydev.noarch, version 2.2.1. Pydev no longer loads in the eclipse (Helios or eclipse-pde.x86_64, version 3.6.2) environment.
Steps to Reproduce:
On an x86_64 based system use the following steps:
1: yum groupinstall "Fedora eclipse"
run Eclipse, pydev will not load. see attached pydev_debug.txt gathered from eclipse console log.
3: yum remove eclipse-pydev.noarch
4: yum install eclipse-pydev.x86_64
run eclipse . pydev will load.
So what you're saying is that when the new, noarch eclipse-pydev package is installed (and the arch-specific one is *not* installed), it fails to load but when it's the opposite situation, it works fine?
I don't think that is exactly what i am saying. I mean that no matter what. The eclipse-pydev.noarch is not working with the eclipse-pde.x86_64 at all. The eclipse-pydev.x86_64 is neither installed for an existing eclipse-pde.x86_64 nor preserved during an upgrade.
I can uninstall the pydev.noarch and install the pydev.x86_64, but i must blacklist the later pydev.noarch to prevent future replacement.
So quick questions: Should the eclipse-pydev.noarch update the eclipse-pydev.x86_64? I did not think it appropriate.
Why is the 2.2.1 version not available in a .x86_64 version?
Looking at eclipse-pydev's changelog, I see this entry explaining the move to noarch:
* Mon Apr 4 2011 Alexander Kurtakov <firstname.lastname@example.org> 1:2.0.0-1
- Update to upstream version 2.0.0.
- Make the package noarch. It was arch only for psyco which seems to be dead now(no longer available in Fedora).
So it appears that the noarch package should be the only package available.
Would you please try moving away your ~/.eclipse and attaching the output of eclipse -consolelog -debug -clean . Clean switch forces to reconciler to revalidate the bundles and thus prints more detailed information even if it has a cashed failure and no other fs change happened after that.
[davdunc@davdunc-xps ~]$ cd
[davdunc@davdunc-xps ~]$ mv .eclipse ~/dot_eclipse
[davdunc@davdunc-xps ~]$ eclipse -consolelog -debug -clean | tee output.log
Performed and uploading the output.log for review.
Thanks to Andrew for reminding me that I could look in the changelog for answers.
FYI on my Java environment:
[davdunc@davdunc-xps ~]$ alternatives --display java
java - status is auto.
link currently points to /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java
/usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java - priority 16000
...<**snipped out the slave settings**>
/usr/lib/jvm/jre-1.5.0-gcj/bin/java - priority 1500
...<**snipped out the slave settings**>
Current `best' version is /usr/lib/jvm/jre-1.6.0-openjdk.x86_64/bin/java.
Created attachment 522038 [details]
eclipse --consolelog --debug -clean
Please paste here the output of:
rpm -qaV eclipse-*
Is there a chance eclipse was run as the root user at any point? I'm concerned that things have been modified in /usr/lib64/eclipse and that's breaking the run-time reconciliation of newly-installed plugin RPMs
[davdunc@davdunc-xps ~]$ rpm -qaV eclipse-*
[davdunc@davdunc-xps ~]$ rpm -qi eclipse-pde
Name : eclipse-pde
Epoch : 1
Version : 3.6.2
Release : 5.fc15
Install Date: Sun 28 Aug 2011 09:39:27 PM CDT
Group : Text Editors/Integrated Development Environments (IDE)
Size : 96261559
License : EPL
Signature : RSA/SHA256, Thu 28 Apr 2011 05:26:40 AM CDT, Key ID b4ebf579069c8460
Source RPM : eclipse-3.6.2-5.fc15.src.rpm
Build Date : Wed 27 Apr 2011 04:22:34 PM CDT
Build Host : x86-18.phx2.fedoraproject.org
Relocations : (not relocatable)
Packager : Fedora Project
Vendor : Fedora Project
URL : http://www.eclipse.org/
Summary : Eclipse Plugin Development Environment
Eclipse Plugin Development Environment. This package is required for
developing Eclipse plugins.
Would you please give us the output of
rpm -qV icu4j-eclipse
rpm -qV tomcat5-jasper-eclipse
rpm -qa|grep jpp
[root@davdunc-xps ~]# rpm -qV icu4j-eclipse
[root@davdunc-xps ~]# rpm -qV tomcat5-jasper-eclipse
[root@davdunc-xps ~]# rpm -qa | grep jpp
I am going to attach an sos report for you.
Created attachment 522308 [details]
sosreport from affected machine.
Created attachment 522309 [details]
md5 sum for sosreport
This message is a notice that Fedora 15 is now at end of life. Fedora
has stopped maintaining and issuing updates for Fedora 15. It is
Fedora's policy to close all bug reports from releases that are no
longer maintained. At this time, all open bugs with a Fedora 'version'
of '15' have been closed as WONTFIX.
(Please note: Our normal process is to give advanced warning of this
occurring, but we forgot to do that. A thousand apologies.)
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen
this bug and simply change the 'version' to a later Fedora version.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we were unable to fix it before Fedora 15 reached end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora, you are encouraged to click on
"Clone This Bug" (top right of this page) and open it against that
version of Fedora.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here: