Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation from update site fails with No repository found message #488

Open
khatchad opened this issue Jun 7, 2017 · 22 comments
Open
Assignees

Comments

@khatchad
Copy link

khatchad commented Jun 7, 2017

I am receiving the following error when my Eclipse installation does an update:

An error occurred while collecting items to be installed
session context was:(profile=_home_rk1424_eclipse_rcp-latest-released_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
No repository found containing: osgi.bundle,com.gradleware.tooling.client,0.19.0.v20170412105839
No repository found containing: osgi.bundle,com.gradleware.tooling.model,0.19.0.v20170412105839
No repository found containing: osgi.bundle,com.gradleware.tooling.utils,0.19.0.v20170412105839
No repository found containing: osgi.bundle,org.eclipse.buildship.branding,2.0.2.v20170420-0909
No repository found containing: osgi.bundle,org.eclipse.buildship.core,2.0.2.v20170420-0909
No repository found containing: osgi.bundle,org.eclipse.buildship.stsmigration,2.0.2.v20170420-0909
No repository found containing: osgi.bundle,org.eclipse.buildship.ui,2.0.2.v20170420-0909
No repository found containing: osgi.bundle,org.gradle.toolingapi,3.5.0.v20170412105839
No repository found containing: org.eclipse.update.feature,org.eclipse.buildship,2.0.2.v20170420-0909
@donat
Copy link
Contributor

donat commented Jun 7, 2017

Can you please try to disable the other update sites in your Eclipse preferences and rerun the update?
screen shot 2017-06-07 at 15 46 29

@khatchad
Copy link
Author

khatchad commented Jun 7, 2017

I was actually able to install the update by:

  1. Removing the buildship update site from the preferences.
  2. Going to the Eclipse Marketplace page for buildship.
  3. Selecting "update" on the button.

The update site has also reappeared in the list but now I don't get any errors (presumably because I now have the update).

@donat donat changed the title Update error Installation from update site fails with No repository found message Jul 17, 2017
@donat donat added this to the Buildship 2.1.3 milestone Jul 17, 2017
@donat
Copy link
Contributor

donat commented Jul 17, 2017

This has been reported multiple times but I was never able to reproduce it locally. It seems this problem is not Buildship-specific and but a general problem with P2.

If somebody encounters this problem, please try installing with my recommendation from Jun 7:

Can you please try to disable the other update sites in your Eclipse preferences and rerun the update?

@donat
Copy link
Contributor

donat commented Jul 20, 2017

I opened a Bugzilla ticket for the investigation.

@donat donat self-assigned this Jul 20, 2017
@AJNeufeld
Copy link

AJNeufeld commented Jul 27, 2017

I'm getting this error:

An error occurred while collecting items to be installed
   session context was:(profile=C__opt_eclipse_jee-latest_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
   No repository found containing: osgi.bundle,com.gradleware.tooling.client,0.19.2.v20170713071601
   No repository found containing: osgi.bundle,com.gradleware.tooling.model,0.19.2.v20170713071601
   No repository found containing: osgi.bundle,com.gradleware.tooling.utils,0.19.2.v20170713071601
   No repository found containing: osgi.bundle,org.eclipse.buildship.branding,2.1.1.v20170713-0944
   No repository found containing: osgi.bundle,org.eclipse.buildship.core,2.1.1.v20170713-0944
   No repository found containing: osgi.bundle,org.eclipse.buildship.stsmigration,2.1.1.v20170713-0944
   No repository found containing: osgi.bundle,org.eclipse.buildship.ui,2.1.1.v20170713-0944
   No repository found containing: osgi.bundle,org.gradle.toolingapi,3.5.0.v20170713071601
   No repository found containing: org.eclipse.update.feature,org.eclipse.buildship,2.1.1.v20170713-0944

Disabled all repositories but Buildship: same error
Disabled all repositories but Buildship, Oxygen, and Oxygen 201706281000: same error

Solution from @khatchad works like a charm.

@m0squito
Copy link

I was getting the same errors as @AJNeufeld and fixed the problem by changing the update site for Buildship in Preferences from:
http://download.eclipse.org/buildship/updates/e46/releases/2.x

to:
http://download.eclipse.org/buildship/updates/e47/releases/2.x

After this change, the update went through without any problems.

@donat
Copy link
Contributor

donat commented Sep 15, 2017

@scompo
Copy link

scompo commented Jan 6, 2018

Has the site chaged to e48?
I was having the same problem and changed to this version, it's now updating fine.

@SpraxDev
Copy link

Has the site chaged to e48?

It hasn't according to https://projects.eclipse.org/projects/tools.buildship/downloads
I edited the update-sites to e48 causing the updater to loop and changes it back to the release-URL from that download-page. Now it's working. I don't know what the problem was. Maybe Eclipse has cached some files and these were overwritten after "removing" it's e47 URL?

@Rolf-N
Copy link

Rolf-N commented Feb 13, 2018

I get this error when trying to install Java 9 JDT to Eclipse.
I tried to remove the update site "http://download.eclipse.org/eclipse/updates/none" but for some reason it continues reapperaing by itself.

I used only the update sites in preferences as marked in the picture from donat above - No help.
I removed buildship and reinstalled it - no help.

Here are the details to the error as reportet by Eclipse:

`eclipse.buildId=4.7.2.M20171130-0510
java.version=1.8.0_131
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
Framework arguments: -product org.eclipse.epp.package.php.product -product org.eclipse.epp.package.php.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.php.product -data file:/C:/Users/Rolf/eclipse-workspace/ -product org.eclipse.epp.package.php.product

org.eclipse.equinox.p2.metadata.repository
Error
Tue Feb 13 09:49:26 CET 2018
No repository found at http://download.eclipse.org/eclipse/updates/none.
`

@alanradley
Copy link

I have the exact same problem - cannot install the Java-9 update from the eclipse site - and I find it incredible that the authors of Eclipse claim that it is Java-9 compatible when many people are having this problem - and nobody seems to know how to fix it. This is very unprofessional.

@gabrieljeremiahcampbell
Copy link

Hello everyone, I just found a work around for the problem. What I did was to uncheck all default update sites and create a new update site: with the URL http://download.eclipse.org/eclipse/updates/4.7. I then selected all the updates and let eclipse update everything that it could.

When it completed I saw that Java 9 tools were installed:

java9

@tuannv0898
Copy link

tuannv0898 commented Mar 17, 2018

Hi. I am using lubuntu( like ubuntu) and i found that when i install ccs, i used sudo cmd, so some file can't be changed by another user, that's why the problem comes up. So in the place i installed ccs, i run the cmd:

sudo chown -R username:groupname * 

with username and groupname are the same as my computer account.
Hope it solve your problem.

@folterj
Copy link

folterj commented Mar 14, 2019

I've had the same issue since mid 2018. Performing a search, this issue has been reported since 2011.
I'm surprised workarounds are proposed for this. And these don't even work, the only fix is to completely reinstall Eclipse.

We're in 2019 now, surely there is a way to fix this recurring issue? How can there not be a simple fix i.e. if repo URL not found: skip and continue with next URL / update (without aborting as critical error and preventing any other update)?

OS: Windows 10 64-bit
Eclipse: Windows, 64-bit; Latest version since mid 2018

@aleskiewicz
Copy link

It happened to me just now, changing update site from e410 to e411 fixed the issue. I am using

Spring Tool Suite 4
Version: 4.2.2.RELEASE
Build Id: 201905232009

I did regular update and it showed STS 4.2.2 with some other packages and Buildship 3.1 (from 3.0.1). After changing the update site, update was executed without any issues

@KPrzychodzki
Copy link

Changing link to source of buildship might cancel some caching as someone before mentioned. In my case after first fail it did not seem to even actually retrieve data from web - it was immediately failing. Changed source of buildship from e48 back to e47 - took some time but otherwise - worked smoothly. Altered it back to e48 - no more issues.
Using marketplace update did not work for me, probably because it was still going for the same source from e48.

@ghost
Copy link

ghost commented Jul 19, 2019

Happend also on my eclipse 2019-03, running on Win10 pro 64bit.
An error occurred while collecting items to be installed session context was:(profile=[*replaced*]_eclipse_java-2019-03_eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). No repository found containing: osgi.bundle,org.eclipse.buildship.branding,3.1.1.v20190701-1623 No repository found containing: osgi.bundle,org.eclipse.buildship.core,3.1.1.v20190701-1623 No repository found containing: osgi.bundle,org.eclipse.buildship.stsmigration,3.1.1.v20190701-1623 No repository found containing: osgi.bundle,org.eclipse.buildship.ui,3.1.1.v20190701-1623 No repository found containing: osgi.bundle,org.gradle.toolingapi,5.5.0.v20190701-1623 No repository found containing: osgi.bundle,com.google.guava,27.1.0.v20190517-1946 No repository found containing: org.eclipse.update.feature,org.eclipse.buildship,3.1.1.v20190701-1623

An upgrade to 2019_06 doesn't fix it neither, but this method worked for me:

I was actually able to install the update by:

1. Removing the buildship update site from the preferences.

2. Going to the Eclipse Marketplace page for buildship.

3. Selecting "update" on the button.

The update site has also reappeared in the list but now I don't get any errors (presumably because I now have the update).

Thanks @khatchad

@dariok
Copy link

dariok commented Aug 1, 2019

Sorry for intruding, but I came across this while having the same problem with some other update in Eclipse 2019-06.
Building on the ideas here, what worked for me was to

  1. go to „Available Software Sites“
  2. change the affected URL (e.g. by adding/removing a / at the end)
  3. Apply and Close
  4. re-open „Available Software Sites“
  5. undo the above change
  6. select „Reload“ while the affected repo is still selected

After that, the update went through like a charm. Not sure whether simply clicking „reload“ will help – I think I did that before to no avail, but that was yesterday ;)

@emilycrutcher
Copy link

Same problem as others here. For me, navigating to eclipse marketplace and hitting update from there worked...

@jamestomk
Copy link

Just like others suggest (thanks!):

  1. removed the update site from Eclipse Available sw sites
  2. went to marketplace and found package, ran Update from marketplace with no problems
    I see update site was re-added to Available sws

@o2themar
Copy link

o2themar commented Dec 5, 2019

For me what worked was after adding the trailing / to all the update sites I then went Window > Preferences > Install/Update > Available Software Sites and then selected all the sites and did an export as an xml file. I then opened the xml file in a text editor and did a find on /" and replaced it with " so as to remove all the trailing backslashes. Then I did an import on that xml file and went through each update site and reloaded them. You can only do the reload for one site at a time. After that I was able to update successfully.

@AndrewH2O
Copy link

I had this today with eclipse 2019-12 followed advice of @donat re commented on Jun 7, 2017:

  1. clicked on install new software under windows/preferences
  2. then clicked on manage, located 'buildship' and removed it
  3. went back into market place and was prompted to install new marketplace installer
    Install/updates worked ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests