On 11/09/11 18:17, Dan Mick wrote:
On 11/ 9/11 06:13 PM, Dan Mick wrote:
On 11/ 9/11 05:48 PM, Brock Pytlik wrote:
On 11/09/11 17:26, Neal Pollack wrote:
I have a large shared server that a number of people share,
and it is sitting at NV build 144. I was told by several people
that we should be able to do a two-step upgrade now, first
from build 144 to 151a, and then from 151a to Solaris 11 GA (175b).
BUT, I can't find any specific details on how to make that work.
I would need to know what pkg repo and publisher syntax to use
for the first step going from 144 to 151a. And then the next step.
The release notes for 151a were no help. My publishers are a little
messed up and need to start fresh;
root@zcube:~# pkg publisher
PUBLISHER TYPE STATUS URI
solaris (preferred) origin online
[1]http://ipkg.sfbay.sun.com/dev/solaris/
opensolaris.org (non-sticky) origin online
[2]http://ipkg.sfbay/dev/
opensolaris.org (non-sticky) origin online
[3]http://ipkg.sfbay/release/
root@zcube:~# uname -a
SunOS zcube 5.11 snv_144 i86pc i386 i86pc Solaris
Any help?

References

1. http://ipkg.sfbay.sun.com/dev/solaris/
2. http://ipkg.sfbay/dev/
3. http://ipkg.sfbay/release/
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
I've not tried this particular sequence, so I'd start by taking a clone of the
current BE in case everything goes badly.

So, after taking that clone, the first step is to remove the opensolaris.org
publishers:
pkg unset-publisher opensolaris.org

Next, set your solaris publisher to the release repo:
pkg set-publisher -G http://ipkg.sfbay.sun.com/dev/solaris -g
http://ipkg.us.oracle.com/solaris11/release solaris

Next try:
pkg update -nv

That's "image-update" at 144. And it didn't work; tries to update 'pkg' and fails with ips-incorporation constraints; adding '-f' doesn't help, nor does specifying the 151 version (both 151 and 175 are in the release repo now, so specifying the versions is probably going to be necessary for all this, I'm
guessing).
Sorry, build 144 was a long, long time ago (16 months or so).

Please provide the errors that happen when it tries to update pkg, and when you try w/ the -f option.

Trying to remove ips-incorporation fails because of a bunch of things that depend on it. I don't remember the way out of this one, but I remember it being
painful.

And see what it does. If it looks like it's taking you to build 151a bits, great. If it doesn't, try uninstalling all the packages from opensolaris.org:
pkg uninstall 'pkg://opensolaris.org/*'

I can try this in the test BE; it's removing a wad of stuff, and when it's done I'll try "install [email protected]" next. I worry that it will have lost
all the system configuration by doing that, though.

lots of errors about lost+found files, and finally a stack trace:
1800 packages still installed from opensolaris.org.

Huh, I had assumed that the image had moved to solaris as the source of its system packages, like core-os. Is that not the case?

1800 packages from opensolaris.org is way more than most people have installed.


Traceback (most recent call last):
  File "/usr/bin/pkg", line 3802, in handle_errors
    __ret = func(*args, **kwargs)
  File "/usr/bin/pkg", line 3779, in main_func
    return func(img, pargs)
  File "/usr/bin/pkg", line 1320, in uninstall
    return __api_execute_plan(op, api_inst)
  File "/usr/bin/pkg", line 831, in __api_execute_plan
    api_inst.execute_plan()
File "/usr/lib/python2.6/vendor-packages/pkg/client/api.py", line 727, in execute_plan
    self.__img.imageplan.execute()
File "/usr/lib/python2.6/vendor-packages/pkg/client/imageplan.py", line 1132, in execute
    p.execute_removal(src, dest)
File "/usr/lib/python2.6/vendor-packages/pkg/client/pkgplan.py", line 326, in execute_removal
    src.remove(self)
File "/usr/lib/python2.6/vendor-packages/pkg/actions/user.py", line 244, in remove
    pw = PasswordFile(root, lock=True)
File "/usr/lib/python2.6/vendor-packages/pkg/cfgfiles.py", line 238, in __init__
    self.lockfile()
File "/usr/lib/python2.6/vendor-packages/pkg/cfgfiles.py", line 304, in lockfile
    self.lockfd = file(fn, 'w')
IOError: [Errno 2] No such file or directory: '/mnt/etc/.pwd.lock'
Haven't seen that one before.

I assume you've read through the relevant sets of release notes from the 144-151a time frame and you're not hitting any of the special cases called out in them? I don't see anything that leaps out, but I also don't remember anyone trying this particular leap.

Brock


pkg: This is an internal error. Please let the developers know about this problem by filing a bug at http://defect.opensolaris.org and including the above traceback and this message. The version of pkg(5) is '1e2b423ee045+'.




and trying the update again. Once you get to the 151a bits, you should be able to move forward to 175b by following the release notes. (You may need to
uninstall packages from opensolaris.org to move forward.)

Hth,
Brock
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss



_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

Reply via email to