Update error: "No repository found containing..."

[sreed]

WindowBuilder Pro 7.0.0
Windows XP Pro sp3
Eclipse 3.4 sr2

When updating from Eclipse I get the following error.

An error occurred while collecting items to be installed
No repository found containing: com.instantiations.common.core/osgi.bundle/5.5.0.200906141053
No repository found containing: com.instantiations.common.help/osgi.bundle/5.5.0.200906141053
No repository found containing: com.instantiations.common.ui/osgi.bundle/5.5.0.200906141053
No repository found containing: com.instantiations.eclipse.debug/osgi.bundle/5.5.0.200906141053
No repository found containing: com.instantiations.eclipse.shared/org.eclipse.update.feature/5.5.0.200906141053
No repository found containing: com.instantiations.eclipse.startup/osgi.bundle/5.5.0.200906141053
No repository found containing: com.instantiations.eclipse.util/osgi.bundle/5.5.0.200906141053
No repository found containing: com.instantiations.tools/osgi.bundle/5.5.0.200906141053

It looks like the dependencies are garbled. Any help to fix this would be much appreciated.
Thanks,
Scott

[sreed]

I ran 'Eclipse -clean' and this problem disappeared.

[Eric Clayberg]

I ran 'Eclipse -clean' and this problem disappeared.

Simply waiting a few minutes and trying it again would also fix it.

You likely hit the updat site at the very moment it was being updated itself.

[sreed]

I am having a similar problem now with Eclipse 3.5. Running 'Eclipse -clean' didn't help and waiting and retrying definitely didn't help. I have tried several times and get the same error:
An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,org.eclipse.mylyn.pde.ui,3.2.0.I20090611-0300-e3x
Does anyone have any suggestions?

[Eric Clayberg]

I am having a similar problem now with Eclipse 3.5. Running 'Eclipse -clean' didn't help and waiting and retrying definitely didn't help. I have tried several times and get the same error:
An error occurred while collecting items to be installed
session context was:(profile=epp.package.jee, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,org.eclipse.mylyn.pde.ui,3.2.0.I20090611-0300-e3x
Does anyone have any suggestions?

None of those errors has anything to do with Swing Designer as we do not reference Mylyn in any way.

Eclipse 3.5 is offically coming out on June 24th, so I would guess that the Eclipse update sites are currently in flux.

[andig]

I can confirm the problem identified by sreed. For a couple of days now, Instatiations Updates keep failing:

An error occurred while collecting items to be installed
session context was:(profile=SDKProfile, phase=org.eclipse.equinox.internal.provisional.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,com.instantiations.common.core,5.5.0.200906240020
No repository found containing: osgi.bundle,com.instantiations.common.help,5.5.0.200906240020
No repository found containing: osgi.bundle,com.instantiations.common.ui,5.5.0.200906240020
No repository found containing: osgi.bundle,com.instantiations.css,7.0.0.200906240113
No repository found containing: org.eclipse.update.feature,com.instantiations.css.feature,7.0.0.200906240113
No repository found containing: osgi.bundle,com.instantiations.designer.core,7.0.0.200906240059
No repository found containing: osgi.bundle,com.instantiations.designer.core.api,7.0.0.200906240059
No repository found containing: osgi.bundle,com.instantiations.designer.core.apiImpl,7.0.0.200906240059
No repository found containing: osgi.bundle,com.instantiations.designer.core.databinding,7.0.0.200906240059
No repository found containing: org.eclipse.update.feature,com.instantiations.designer.core.feature,7.0.0.200906240059
No repository found containing: osgi.bundle,com.instantiations.designer.doc.user,7.0.0.200906240059
No repository found containing: osgi.bundle,com.instantiations.designer.gwt,7.0.0.200906240106
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.GWTExt,7.0.0.200906240106
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.doc.user,7.0.0.200906240106
No repository found containing: org.eclipse.update.feature,com.instantiations.designer.gwt.feature,7.0.0.200906240106
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.hosted,7.0.0.200906240102
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.hosted.1_4,7.0.0.200906240102
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.hosted.1_4.ie,7.0.0.200906240102
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.hosted.1_4.super,7.0.0.200906240102
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.hosted.1_5,7.0.0.200906240102
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.hosted.1_5.ie,7.0.0.200906240102
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.hosted.1_5.super,7.0.0.200906240102
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.hosted.1_6,7.0.0.200906240102
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.hosted.1_6.ie,7.0.0.200906240102
No repository found containing: osgi.bundle,com.instantiations.designer.gwt.hosted.1_6.super,7.0.0.200906240102
No repository found containing: org.eclipse.update.feature,com.instantiations.designer.gwtcore.feature,7.0.0.200906240102
No repository found containing: osgi.bundle,com.instantiations.designer.jdt.fragment,7.0.0.200906240059
No repository found containing: osgi.bundle,com.instantiations.designer.os,7.0.0.200906240059
No repository found containing: osgi.bundle,com.instantiations.designer.os.win32,7.0.0.200906240059
No repository found containing: osgi.bundle,com.instantiations.designer.rcp,7.0.0.200906240127
No repository found containing: osgi.bundle,com.instantiations.designer.rcp.databinding,7.0.0.200906240127
No repository found containing: osgi.bundle,com.instantiations.designer.rcp.databinding.emf,7.0.0.200906240127
No repository found containing: osgi.bundle,com.instantiations.designer.rcp.doc.user,7.0.0.200906240127
No repository found containing: org.eclipse.update.feature,com.instantiations.designer.rcp.feature,7.0.0.200906240127
No repository found containing: osgi.bundle,com.instantiations.designer.rcp.nebula,7.0.0.200906240127
No repository found containing: osgi.bundle,com.instantiations.designer.rcp.nebula.lib,7.0.0.200906240127
No repository found containing: osgi.bundle,com.instantiations.designer.rcp.swing2swt,7.0.0.200906240127
No repository found containing: osgi.bundle,com.instantiations.designer.runtime,7.0.0.200906240059
No repository found containing: osgi.bundle,com.instantiations.designer.swt,7.0.0.200906240112
No repository found containing: org.eclipse.update.feature,com.instantiations.designer.swt.feature,7.0.0.200906240112
No repository found containing: osgi.bundle,com.instantiations.eclipse.debug,5.5.0.200906240020
No repository found containing: org.eclipse.update.feature,com.instantiations.eclipse.shared,5.5.0.200906240020
No repository found containing: osgi.bundle,com.instantiations.eclipse.startup,5.5.0.200906240020
No repository found containing: osgi.bundle,com.instantiations.eclipse.ui,7.0.0.200906240034
No repository found containing: org.eclipse.update.feature,com.instantiations.eclipse.ui,7.0.0.200906240034
No repository found containing: osgi.bundle,com.instantiations.eclipse.util,5.5.0.200906240020
No repository found containing: osgi.bundle,com.instantiations.j2ee,7.0.0.200906240102
No repository found containing: osgi.bundle,com.instantiations.tools,5.5.0.200906240020

This is most likely not an issue with the Eclipse servers as e.g. PDT and Mylyn were successfully updating.

[Eric Clayberg]

I'm sorry, but you are incorrect on both counts.

The problem most recently reported by sreed did not even mention our products or any of their dependencies.

As to any temporary problem accessing our update site, simply wait 5 minutes, restart Eclipse and try it again. That can happen any time the update site itself is in the process of updating.

We are processing several thousand updates a day from that exact update site, so it is not a general issue and not an issue that occurs for more than a few minutes at a time.

And, yes, the same thing can and does happen on the Eclipse.org update sites when they update their bits. That is one of the known flaws of the update site process.

[sreed]

I may have not made it clear that I was updating ONLY Instantiations software when I had this problem in June. I do not have this problem with any other software and I do not see how Instantiations can be so certain that there isn't something about their update that is causing this. I experienced the same problem last week and today I tried again and got the same result. The defensiveness of Instantiations' response belies their willingness to investigate and resolve this.

I was finally able to complete the update, not by waiting and trying again but by updating the many modules of Instantiations software in pieces, one or two modules at a time. Perhaps that is a clue to why I see this problem only when updating Instantiations software.

If updating Instantiations software is referencing OSGI packages that they claim is not involved in their update, then perhaps they can figure out how to replicate and report the bug that is involving unrelated software in updating their software.

[Eric Clayberg]

No defensiveness at all. I am merely telling you the facts.

The problem you reported is very common with all Eclipse update sites (which a simple Google search would confirm). It is caused by a fundamental flaws in the Eclipse Update Site architecture and even affects the Eclipse.org Update Sites from time to time (as a Google search would show you).

I think you need to do some more research on how the Eclipse update process works. Even when you are updating just one plugin, the Update Manger will still try to resolve the entire configuration. If there are any problems with your configuration (whether they be with one of our plugins or someone else's, the update can fail). You likely had a problem with your Mylyn configuration (since those are the plugins that you mentioned in your post), so that was causing the update to fail. Simple logic on your part should make this quite clear - if our product does not reference Mylyn in any way, and your update fails because of a problem with Mylyn, maybe, just maybe, you are having a problem with your Mylyn configuration. As of this moment, you are the only user that has ever reported an update problem involving Mylyn, so we can be quite confident that the problem is not related to our product.

If you are having persistent problems updating any plugin, there might be a problem with your Eclipse p2 plugin cache. Starting with a clean Eclipse configuration is usually the best solution. Have you tried that?

Also, as I have stated several times, there can be temporary, transitory problems with our update site (and any update site) at the moment that its bits are being updated. The simple reason this happens is that the the update process itself is quite fragile. The Update Manager reads the site manifest and resolves all of the plugins it wants to download. This entire update process can take several minutes. If the bits on the server actually change (because a new update became available) during this process, the update will fail mid stream. Waiting 5 minutes and restarting Eclipse typically fixes the problem (restarting is necessary because the update manager seems to cache the site maps for the entire session).

You can argue all you want, but that will not change the basic facts or the basic problem with the Eclipse update process. We have investigated this quite thoroughly and understand its limitations quite well.