Steven Acres wrote:
On Sat, Sep 26, 2009 at 2:53 PM, Brandon High <bh...@freaks.com
<mailto:bh...@freaks.com>> wrote:
What's the correct procedure for updating to a specific branch
revision? I've got a system that's at snv_111 which I would like to
update to snv_118. I would like to avoid 121-123 due to the raidz
checksum bugs.
My understanding is that I need to create a new BE, then update that
BE with the new packages.
I can create a new package with:
# beadm create snv_118@"$(date)"
but how do I tell pkg to update the new BE? A command like:
# pkg install ent...@0.5.11-118
will update the current BE, which is not what I want.
-B
--
Brandon High : bh...@freaks.com <mailto:bh...@freaks.com>
Always try to do things in chronological order; it's less confusing
that way.
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
<mailto:opensolaris-discuss@opensolaris.org>
Hey Brandon,
beadm create new_be_118 ; beadm mount new_be_118 /mnt ; \
pkg -R /mnt set-authority -P http://pkg.opensolaris.org/dev dev
<http://opensolaris.org/dev> ; \
It should really be:
pkg -R /mnt set-publisher -O http://pkg.opensolaris.org/dev opensolaris.org
In other words, the publisher should always be "opensolaris.org" if
you're pointing at opensolaris.org/dev or opensolaris.org/release. In
the future, the client will enforce this.
Cheers,
--
Shawn Walker
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
