Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [egit-dev] Dightlt build problems

2011/7/25 Robin Rosenberg <robin.rosenberg@xxxxxxxxxx>
Hi,

I have not been able to instal a nightly build for a while. Here is the
error.

An error occurred while collecting items to be installed
session context was:(profile=""> phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=,
action=""> Artifact not found: osgi.bundle,org.eclipse.egit,1.1.0.201107190912.
http://download.eclipse.org/egit/updates-nightly/plugins/org.eclipse.egit_1.1.0.201107190912.jar
Artifact not found: osgi.bundle,org.eclipse.egit.core,1.1.0.201107190912.
http://download.eclipse.org/egit/updates-nightly/plugins/org.eclipse.egit.core_1.1.0.201107190912.jar
Artifact not found: osgi.bundle,org.eclipse.egit.doc,1.1.0.201107190912.
http://download.eclipse.org/egit/updates-nightly/plugins/org.eclipse.egit.doc_1.1.0.201107190912.jar
Artifact not found:
org.eclipse.update.feature,org.eclipse.egit,1.1.0.201107190912.
http://download.eclipse.org/egit/updates-nightly/features/org.eclipse.egit_1.1.0.201107190912.jar
Artifact not found: osgi.bundle,org.eclipse.egit.ui,1.1.0.201107190912.
http://download.eclipse.org/egit/updates-nightly/plugins/org.eclipse.egit.ui_1.1.0.201107190912.jar
Problems downloading artifact:
osgi.bundle,org.eclipse.jgit,1.1.0.201107141110.
MD5 hash is not as expected. Expected: 55cde7ec35670e3fbc4c1890fa9c0458
and found a2c75a8062876a3724c9b96e5eb9c69e.
Problems downloading artifact:
org.eclipse.update.feature,org.eclipse.jgit,1.1.0.201107141117.
MD5 hash is not as expected. Expected: 960772c53b4e52f08814332f5055d96a
and found 387a126440b6346091c14f7d8b0bbbce.

(just returned from vacation)

Since a while the egit build is failing since it fails to delete files from the last deployment
due to some permission problems. I tried deleting them manually but I can't despite
the fact that my permission groups and file permissions say I should be able to.
I contacted webmaster to resolve this issue. When this is fixed the next build
should deploy a fresh new p2 repo, hopefully this will work then.

--
Matthias

Back to the top