Community
Participate
Working Groups
Using Oomph installer 1.1.0.v20150408-1708 (build id 1087?, can't go to Advanced mode anymore). I have updated my Oomph installer and it cannot connect anymore. I get a dialog that lets me configure the proxy, exit or retry. I verified the proxy settings and they are correct. I tried Manual, Native (my system settings are correct) and Direct (tried another network that doesn't require a proxy). I also tried a freshly extracted Oomph installer and it behaves the same way.
It looks to me like Oomph is downloading an HTML web page showing the catalog instead of the catalog, itself. Oomph is totally disabled (blocker severity IMO). See my forum post: https://www.eclipse.org/forums/index.php/t/1065555/
Update: the web access to git at eclipse.org seems to be broken. Perhaps this isn't an Oomph problem at all (except maybe that Oomph shouldn't be relying on the web front-end to access catalogs and other setup models?)
It looks to me like the "plain" git resource URLs are working again on Eclipse.org. My Oomph is working again. Marc-André, can you confirm?
I think this was a temporary network failure. This should be less likely when we stop using cGit directly. *** This bug has been marked as a duplicate of bug 462247 ***
(In reply to Christian W. Damus from comment #3) > It looks to me like the "plain" git resource URLs are working again on > Eclipse.org. My Oomph is working again. > > Marc-André, can you confirm? It works now. But I got a NPE when I clicked retry. I copy-pasted the stack but unfortunately, it didn't stay in my clipboard and I don't know where the workspace log is.
The installer has no workspace but the installer's log is in configuration/nnnnnnnn.log
(In reply to Eike Stepper from comment #6) > The installer has no workspace but the installer's log is in > configuration/nnnnnnnn.log Ah! Thanks. Opened bug 464308.
I think that Ed meant to mark this as a dup of bug 463967.
Dup of bug 463967. *** This bug has been marked as a duplicate of bug 463967 ***
I am still seeing this issue when I try to install eclispe using the Oomph installer (getting the same 'The catalog could not be loaded ........' message).
(In reply to Sumit Sharma from comment #10) > I am still seeing this issue when I try to install eclispe using the Oomph > installer (getting the same 'The catalog could not be loaded ........' > message). Likely this was a glitch in the Eclipse servers on the 16th. The catalog setups.zip 404, and then the git.eclipse.org server was overoaded.
