[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openjdk-distro-pkg-dev
Subject:    RE: IcedTea source archive is inaccessible
From:       "Nishchint Raina (nisraina)" <nisraina () cisco ! com>
Date:       2017-01-31 19:16:10
Message-ID: 372374afe5ca404d9e2c37e8a7274dd1 () XCH-RCD-015 ! cisco ! com
[Download RAW message or body]

Hi Mark,

Thanks for reaching out. 

We managed to located the source tarball in one of our teammates' development machine \
and added that to our internal mirror. Glad to know that the issue has been fixed.  

− • − •   • • • •   •   •   • − •   • • •   − − • • − −   /   − •   • •   • • •   • • \
• •   − • − •   • • • •   • •   − •   −   Cheers,
Nishchint


-----Original Message-----
From: Mark Wielaard [mailto:mark@klomp.org] 
Sent: Tuesday, January 31, 2017 8:01 AM
To: Nishchint Raina (nisraina) <nisraina@cisco.com>
Cc: distro-pkg-dev@openjdk.java.net
Subject: Re: IcedTea source archive is inaccessible

On Fri, 2017-01-06 at 23:25 +0000, Nishchint Raina (nisraina) wrote:
> Hi,
> 
> I am trying to fetch the source tarball for icetea – the icedtea.wildebeeset.org \
> site is timing out. 
> nisraina-ub-14> wget 
> nisraina-ub-14> http://icedtea.classpath.org/hg/release/icedtea7-fores
> nisraina-ub-14> t-2.1/archive/f89009ada191.tar.bz2
> --2017-01-06 15:22:07--  
> http://icedtea.classpath.org/hg/release/icedtea7-forest-2.1/archive/f8
> 9009ada191.tar.bz2 Resolving proxy-wsa.esl.cisco.com 
> (proxy-wsa.esl.cisco.com)... 173.36.240.174 Connecting to 
> proxy-wsa.esl.cisco.com (proxy-wsa.esl.cisco.com)|173.36.240.174|:80... connected.
> Proxy request sent, awaiting response... 302 Found
> Location: 
> http://icedtea.wildebeest.org/hg/release/icedtea7-forest-2.1/archive/f
> 89009ada191.tar.bz2 [following]
> --2017-01-06 15:22:07--  
> http://icedtea.wildebeest.org/hg/release/icedtea7-forest-2.1/archive/f
> 89009ada191.tar.bz2 Reusing existing connection to 
> proxy-wsa.esl.cisco.com:80.
> Proxy request sent, awaiting response...504 Gateway Timeout
> 2017-01-06 15:24:37 ERROR 504: Gateway Timeout.
> 
> I tried accessing it from browser – same result.

And then you got stuck in the mailinglist moderation queue.
Sorry. Both issues were my fault. But they should have been resolved now. The gateway \
machine got replaced and I had forgotten that machine was behind it...

Please do reach out if you have trouble getting at the source (or the
mailinglist) in the future.

Thanks,

Mark


[prev in list] [next in list] [prev in thread] [next in thread]