I have a different, but also possibly related, problem with Eclipse
packages from experimental. Though the package worked for a while, it is
now unable to access the new p2 update sites (update sites that no
longer support the old site.xml format, such as the Helios Discovery
Site). Here is the error:
org.osgi.framework.BundleException: The bundle "org.eclipse.equinox.p2.reconciler.dropins_1.1.2.R36x_v20110114 [81]" could not be resolved. Reason: Missing Constraint: Require-Bundle: org.eclipse.equinox.p2.touchpoint.eclipse; bundle-version="1.0.0"
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1317)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1301)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:319)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.resume(AbstractBundle.java:374)
at org.eclipse.osgi.framework.internal.core.Framework.resumeBundle(Framework.java:1067)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:561)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.resumeBundles(StartLevelManager.java:546)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.incFWSL(StartLevelManager.java:459)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.doSetStartLevel(StartLevelManager.java:243)
at org.eclipse.osgi.framework.internal.core.StartLevelManager.dispatchEvent(StartLevelManager.java:440)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:227)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:337)
This is the same error that appears at the top of the first poster's
log. It seems that the first bundle mentioned wants a version of the
second bundle that's different from the one on my system. It seems that
both are provided by eclipse-platform-data:
# locate org.eclipse.equinox.p2.touchpoint.eclipse
/usr/lib/eclipse/plugins/org.eclipse.equinox.p2.touchpoint.eclipse.source_2.0.3.R36x_v20101202.jar
/usr/lib/eclipse/plugins/org.eclipse.equinox.p2.touchpoint.eclipse_2.0.3.R36x_v20101202.jar
/usr/share/eclipse/plugins/org.eclipse.equinox.p2.touchpoint.eclipse.source_2.0.3.R36x_v20101202.jar
/usr/share/eclipse/plugins/org.eclipse.equinox.p2.touchpoint.eclipse_2.0.3.R36x_v20101202.jar
--
To UNSUBSCRIBE, email to debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Hi,
Could you double check you are not affected by #587657 ? That bug is
the root of many weird and silent failures.
~Niels
So, as far as I can tell, I don't have bug 587657. (In fact, I had
already installed and configured this version of Eclipse, from
experimental, several weeks ago, installed the stuff I needed, and
worked with it fine for a while. I only had a problem when, a couple
days ago, I tried to update existing plugins before adding some new ones.)
Before sending in my report yesterday, I had noticed that a few of my
plugins were complaining about not finding a sat4j dependency; that
error went away when I reverted to an older sat4j package.
After clearing out my .eclipse directory and reinstalling Eclipse
packages from experimental, the problem seems to have gone away. I
suppose this means the problem could have come from some of my locally
installed plugins. Also, for some reason my Install Software menus had
changed a bit--I'm not quite sure when--and now that I cleared out all
my local stuff in .eclipse, they're back to they way they've always been.
I did save my old configs and downloaded plugins from my .eclipse
directory; please let me know if there's something you'd like me to look
at from there. Hope this has been helpful, thanks, greetings.
El 21/07/11 05:53, Niels Thykier escribió: