Scratch that last response.
The following URL *is* available:
http://pkg.glassfish.org/v3/dev/solaris-x86/
and it is in the list of repo URLs within the .org.../cfg_cache file:
<SNIP>
[authority_dev.glassfish.org]
origin =
http://repine.sfbay:16000/
ssl_key = None
ssl_cert = None
uuid = None
mirrors = []
prefix = dev.glassfish.org
origin-for-windows-i386 =
http://pkg.glassfish.org/v3/dev/windows/
origin-for-sunos-i386 =
http://pkg.glassfish.org/v3/dev/solaris-x86/
origin-for-sunos-sparc =
http://pkg.glassfish.org/v3/dev/solaris-sparc/
origin-for-linux-i386 =
http://pkg.glassfish.org/v3/dev/linux/
origin-for-darwin-universal =
http://pkg.glassfish.org/v3/dev/mac/
[authority_contrib.glassfish.org]
origin =
http://repine.sfbay:16000/
ssl_key = None
ssl_cert = None
uuid = None
mirrors = []
prefix = contrib.glassfish.org
origin-for-windows-i386 =
http://pkg.glassfish.org/v3/contrib/windows/
origin-for-sunos-i386 =
http://pkg.glassfish.org/v3/contrib/solaris-x86/
origin-for-sunos-sparc =
http://pkg.glassfish.org/v3/contrib/solaris-sparc/
origin-for-linux-i386 =
http://pkg.glassfish.org/v3/contrib/linux/
origin-for-darwin-universal =
http://pkg.glassfish.org/v3/contrib/mac/
</SNIP>
So it's not clear to me why your Solaris client is receiving the 404.
Can you access the Solaris repo URLs from a browser on the same Solaris
system?
Chris
Christopher Kampmeier wrote:
> Hi Kristian,
>
> It appears that the following repo URLs are not yet live for the v3
> dev builds:
>
> http://pkg.glassfish.org/v3/dev/solaris-x86
> http://pkg.glassfish.org/v3/dev/solaris-sparc
>
> Whereas Solaris x86 repo is live for Prelude (of course):
>
> http://pkg.glassfish.org/v3prelude/dev/solaris-x86
>
> So it's a repo set up issue on the back end.
>
> Separately, I'll ping the UC2 team to see if the error reporting has
> been improved at least to the extent of reporting the URL that is in use.1
>
> Thanks,
> Chris
>
>
> Kristian Rink wrote:
>> Hi Nolan, *;
>>
>> and first off, thanks a bunch for taking care of this...:
>>
>>
>> Nolan Luu schrieb:
>> [...]
>>
>>> Either the download server was down when you tried it or you would need
>>> to provide the proxy info.
>>>
>>
>> Hmmm, strange: While installing the updatetool works on my (Ubuntu)Linux
>> notebook, the 404 is reproducible on the Solaris server I am using, and a
>> proxy is not required on that machine. Is there a way to, in "updatetool"
>> installer script, to provide some additional $BOOTSTRAPPROPS to see
>> debugging info? Adding to that, which is the actual URL used by the tool to
>> get and install update manager? Maybe I will first off try accessing this
>> URL off the command line? Maybe an issue related to solaris updatetool?
>>
>>
>> Cheers & all the best,
>> Kristian
>>
>>
>>