Community
Participate
Working Groups
Created attachment 121638 [details] Error log from the software update I20090106-0800 I start up eclipse with a new workspace, set Preferences>General>Network Connection to Direct (instead of Native) and restart. Then I go Help>Install New Software. I select Eclipse SDK releng tools, the EMF SDK, and the Graphical Modelling SDK from the list of available packages, and go through the Next>Next>agree to license, etc. It fails saying it cannot find many of the plugins in the repository. I believe this problem was introduced between I1216-0800 and I1217-1605. I will run the same test on clean copies of this build and post my results. PW
Created attachment 121664 [details] Error log from I20081217-1605 I was able to do a clean install and update on I20081216-0800 but it failed with the error log on I20081217-1605 PW
Deleting all sites, and then adding back http://download.eclipse.org/releases/ganymede http://download.eclipse.org/eclipse/updates/3.4 allows the build to be updated. Susan suggested this was bug 236437 resurfacing. PW
Created attachment 122569 [details] Error log on initial install
Created attachment 122571 [details] Repos Configure
Created attachment 122572 [details] Repos Metadata
Yeah, I'm seeing this too. I deleted both repos and added the ganymede back in with a trailing slash works. (don't know why I thought that that would make a difference, but it sound like just adding the same repos back in works as well?) I found that I needed to start with a unique keyring to avoid getting a different error (this profile is in use). If I do a clean install and try to grab say EMF SDK, I get No Repository found. Error log and .settings attached.
Forgot.. This is Build id: I20081211-1908 under MacOS Cocoa. Clarification: I had to change keyring from default to reproduce original error. In order to accomplish workaround all I need to do is fresh install, remove repos from settings and add it back in.
This isn't bug 236437. I just had the error and the artifact repository is still present in my metadata. It's possible there is something wrong with the site itself, or one of its mirrors.
Looking at changes between I1216-0800 and I1217-1605, there were several changes made in core.net between these two builds: UnixyProxyProvider, ProxyBypass, ProxyProviderUtil, ProxyType, StringUtil, WinHTTPCurrentUserIEProxyConfig. I didn't see any changes in p2 between these two builds that look related, so I suspect it is these proxy changes that are causing the problem.
I'm adding Pawel to comment on it.
Proxy code in I20090106-0800 seems to work well, at least Direct setting. Also, like Paul said in comment 2, deleting all sites, and then adding them back allows the build to be updated. This suggest it has nothing to do with proxy settings. I noticed that the problem disappeared in 3.5M5, not sure why though. Could anybody confirm it?
Changing abstract, the old value was "Error updating through proxy". And moving to back to p2.
Paul, are you still experiencing a problem here?
(In reply to comment #13) > Paul, are you still experiencing a problem here? > no, I just did an update from the default URLs provided with I20090217-2200 and it worked. We can probably close this now. PW
Thanks Paul. Please reopen if you encounter a problem again. It looks like there was possibly a regression introduced and then fixed.
