Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cross-project-issues-dev] It worked!

Do we have a mechanism to remove the mirrors? Other than removing them all by removing the mirrorsURL.

 

BTW, I’m moving my main dev environment to this build. Should be able to exercise the bits pretty well.

 

Doug Schaefer, QNX Software Systems

Eclipse CDT Project Lead, http://cdtdoug.blogspot.com

 


From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
Sent: Thursday, March 09, 2006 3:16 PM
To: Cross project issues
Cc: Cross project issues; cross-project-issues-dev-bounces@xxxxxxxxxxx
Subject: RE: [cross-project-issues-dev] It worked!

 


main we should test the various mirrors and temporarily remove the ones that do not have all the files. What do you think?

"Richard Gronback" <Richard.Gronback@xxxxxxxxxxx>
Sent by: cross-project-issues-dev-bounces@xxxxxxxxxxx

03/09/2006 03:03 PM

Please respond to
Cross project issues

To

"Cross project issues" <cross-project-issues-dev@xxxxxxxxxxx>

cc

 

Subject

RE: [cross-project-issues-dev] It worked!

 

 

 




Downloading from main site now (looks OK, but will take a while).  Tried using OSU:
 
java.io.IOException: Server returned HTTP response code: "404 Not Found" for URL: http://ftp.osuosl.org/pub/eclipse//callisto/releases/plugins/org.eclipse.birt.report.engine.emitter.html_2.1.0.M20060303-0920.jar.
at org.eclipse.update.internal.core.UpdateManagerUtils.checkConnectionResult(UpdateManagerUtils.java:557)
at org.eclipse.update.core.ContentReference.getInputSize(ContentReference.java:201)
at org.eclipse.update.core.FeatureContentProvider.asLocalReference(FeatureContentProvider.java:211)
at org.eclipse.update.internal.core.FeaturePackagedContentProvider.getPluginEntryArchiveReferences(FeaturePackagedContentProvider.java:165)
at org.eclipse.update.internal.operations.UpdateUtils.downloadFeatureContent(UpdateUtils.java:627)
at org.eclipse.update.internal.ui.wizards.InstallWizard2.download(InstallWizard2.java:408)
at org.eclipse.update.internal.ui.wizards.InstallWizard2.access$3(InstallWizard2.java:397)
at org.eclipse.update.internal.ui.wizards.InstallWizard2$3.run(InstallWizard2.java:350)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:58)
 

 



From: cross-project-issues-dev-bounces@xxxxxxxxxxx [mailto:cross-project-issues-dev-bounces@xxxxxxxxxxx] On Behalf Of Bjorn Freeman-Benson
Sent:
Thursday, March 09, 2006 2:49 PM
To:
Cross project issues; eclipse.org-planning-council; Eclipse WebMaster (Denis Roy)
Subject:
[cross-project-issues-dev] It worked!

 
Wow, it worked. I was able to install the entire Callisto set with a single update manager wizard (from the eclipse.org servers).

Webmaster Matt tells me that they had installed a fifth node at eclipse.org last week (just before Callisto M5) and that that fifth node appeared to be the culprit. He has disabled that node from the rotation and, ta da, the 403 errors have gone away, at least for me.  What about the rest of you?

Shall we declare that the Callisto M5 is ready for people to install and test and try?

- Bjorn_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev


Back to the top