* On 2015-03-12 at 10:21 GMT, Jim Klimov wrote:

> 11 марта 2015 г. 17:01:01 CET, Jonathan Perkin via illumos-discuss 
> <[email protected]> пишет:
>
> > It's a lot later than I'd planned, but I'm pleased to finally announce
> > the pkgsrc-2014Q4 binary package sets for illumos are now available.

> Hello Jonathan, 
>
> if you'd pardon my sort of stupid question - I've installed pkgsrc
> on onmios some time ago. How do I properly upgrade it? ;)

Hi Jim,

There are no stupid questions.

> 'pkgin update' says there are no news in database 2013Q3 that i have
> here... how do I bump it to the new 2014Q4 release?

Ordinarily you may be able to get away with updating the package path
URLs in:

  /opt/local/etc/pkg_install.conf
  /opt/local/etc/pkgin/repositories.conf

and performing:

  $ pkg_add -U pkg_install pkgin
  $ rm -rf /var/db/pkgin
  $ pkgin update
  $ pkgin full-upgrade

or similar.  However, the 2014Q4 release is very different from
previous releases, and includes signed packages by default.  In order
to support these packages, the 2014Q4 bootstrap kits include our PGP
public key and add support for them to pkg_install.conf.  The default
is to verify the signatures, and that will fail unless you have the
necessary keys and config.

I had a play with upgrading a 2014Q3 OmniOS install to 2014Q4, this is
what worked for me:

  : Update 2014Q3 -> 2014Q4
  $ vi /opt/local/etc/pkg_install.conf

  : Upgrade just pkg_install.  Do this first to get one which supports
  : inline PGP verification.
  $ pkg_add -U pkg_install

  : Grab the newer bootstrap and unpack to a temporary directory.
  $ curl -Os 
http://pkgsrc.joyent.com/packages/SmartOS/bootstrap/bootstrap-2014Q4-i386.tar.gz
  $ tar zxf bootstrap-2014Q4-i386.tar.gz

  : Copy the pkg_install.conf and PGP key
  $ mkdir -p /opt/local/etc/gnupg
  $ cp opt/local/etc/pkg_install.conf /opt/local/etc/
  $ cp opt/local/etc/gnupg/pkgsrc.gpg /opt/local/etc/gnupg

  : Now we can upgrade pkgin
  $ pkg_add -U pkgin
  $ cp opt/local/etc/pkgin/repositories.conf /opt/local/etc/pkgin/

  : At this point we can use pkgin to upgrade.  It's highly
  : recommended to start with a clean pkgin database.
  $ rm -rf /var/db/pkgin
  $ pkgin update
  $ pkgin full-upgrade

> Is it same as installation (pull a bootstrap)? Would this inherit
> and later help update the pkgsrc packages i've installed earlier?

As you can see from above, upgrades can occasionally be tricky,
especially if we have changed the infrastructure.  Therefore we always
recommend reprovisioning, as there is no way to be 100% confident that
an upgrade won't break something, and we'd rather be upfront and
honest about that.

You may get away with just unpacking the latest bootstrap over the top
instead of the first 5 steps above, but will want to add an
additional:

  $ pkg_admin rebuild

prior to running the pkgin step.  You'll also lose any changes you may
have made to the /opt/local/etc config files that are included in the
bootstrap.

> Can I change the arch along the way (x86_64 to multiarch for
> example)?

Not using the above method, at least without not being _extremely_
careful about it.  If you're going to change arch then I'd strongly
recommend provisioning a clean /opt/local and migrating your package
list and /opt/local/etc configs back across.

> Does multiarch offer something like isaexec to also provide 64-bit
> binary programs where deemed beneficial over 32-bit quickness?

It does.  Not all packages have 64-bit binaries, we primarily
concentrate on providing libraries, but when they do you can easily
switch between them using the $ABI environment variable, e.g.:

  $ ABI=32 python -c 'import sys; print sys.maxint'
  2147483647

  $ ABI=64 python -c 'import sys; print sys.maxint'
  9223372036854775807

Hope that's helpful,

-- 
Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com


-------------------------------------------
illumos-discuss
Archives: https://www.listbox.com/member/archive/182180/=now
RSS Feed: https://www.listbox.com/member/archive/rss/182180/21175430-2e6923be
Modify Your Subscription: 
https://www.listbox.com/member/?member_id=21175430&id_secret=21175430-6a77cda4
Powered by Listbox: http://www.listbox.com

Reply via email to