On 01/28/11 01:12 PM, Rinaldo DiGiorgio wrote:
On Jan 28, 2011, at 2:53 PM, Shawn Walker wrote:
On 01/28/11 11:42 AM, Rinaldo DiGiorgio wrote:
Hi,
I was installing various versions of GlassFish. The next day I went to
do a pkg search *****
I get the following error message
-bash-4.0# pkg search rsh
pkg: Some repositories failed to respond appropriately:
contrib.glassfish.sun.com:
http protocol error: code: 503 reason: Service Unavailable
URL:
'http://pkg.sun.com/glassfish/v3/contrib/search/1/False_2_None_None_%3A%3A%3Arsh'.
-bash-4.0#
It was Solaris 11 and it was working properly earlier.
-bash-4.0# pkg authority
PUBLISHER TYPE STATUS URI
contrib.glassfish.sun.com (non-sticky, preferred) origin online
http://pkg.sun.com/glassfish/v3/contrib/
stable.glassfish.org (non-sticky) origin online
http://pkg.glassfish.org/v3/stable/
contrib.glassfish.org (non-sticky) origin online
http://pkg.glassfish.org/v3/contrib/
dev.glassfish.org (non-sticky) origin online
http://pkg.glassfish.org/v3/dev/
release.javaeesdk.sun.com (non-sticky) origin online
http://pkg.sun.com/javaeesdk/6/release/
-bash-4.0#
That concerns me. It requires previous knowledge of where you were pointing? I
guess I am asking if there is a way
to revert to safe mode.
What does "pkg -R / publisher" say?
It looks to me like you're using the image glassfish created.
bash-4.0# pkg -R / publisher
PUBLISHER TYPE STATUS URI
solaris (preferred) origin online
http://pkg.oracle.com/solaris/release/
JDS origin online
http://bursrotst07.east.sun.com/
-bash-4.0#
This is what I was expecting to see.
I don't understand what state I am in.
Okay, so you need to understand a few things.
1) In older builds (pre-155), pkg(1) would silently attempt to discover
images to use for packaging starting from the *current working
directory* and go up to '/' until it found an image. Once it found
the image, it would silently use that one. In 155+, it will exit
with an error and tell you to specify which image you wanted to use.
2) The glassfish team distributes their own user image which the
glassfish update center tool can be used to manage.
So the reason you're seeing this behaviour is because your current
working directory contains the image that glassfish was installed into.
If you want to manipulate the image for your system, then you either
need to specify 'pkg -R /' anytime you use pkg(1), or you need to cd to
'/' first.
Cheers,
-Shawn
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
