<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 2016-11-01 10:36 AM, Nahum Shalman
wrote:<br>
</div>
<blockquote
cite="mid:CAOc1FHjdLmNs2x8qtS-3s6aUGvXGSf1iXTg0SyQEzKmQAKgu=g@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Tue, Nov 1, 2016 at 1:32 AM, Geoff
Nordli <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:geoffn@gnaa.net" target="_blank">geoffn@gnaa.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">I am running OmniOS
v11 r151016<br>
</blockquote>
<div><br>
You didn't mention which quarterly release of pkgsrc you
were on. </div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">I tried to upgrade
pkgsrc using the steps outlined here:<br>
<br>
<a moz-do-not-send="true"
href="https://pkgsrc.joyent.com/install-on-illumos/"
rel="noreferrer" target="_blank">https://pkgsrc.joyent.com/inst<wbr>all-on-illumos/</a></blockquote>
<div><br>
</div>
<div>Note that those say:</div>
<div>"Upgrades aren't fully supported (we don't yet handle
major configuration changes) but this procedure may work
fine for many users and avoid having to re-bootstrap. If
in doubt ensure you have backed up your data and
configuration files. Make sure you use the same set that
was originally installed."</div>
<div><br>
</div>
</div>
</div>
<div class="gmail_extra">
<div class="gmail_quote">
<div>Upgrades from release to release on pkgsrc have always
been tricky. The general advice from Joyent when it comes
to e.g. running joyent-brand pkgsrc zones under SmartOS
has been "reprovision". That means make a note of which
software you use, perhaps with config management, and
start each time from scratch, that said, not all hope is
lost.</div>
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">when I tried to upgrade
pkgin it gives me this error:<br>
<br>
root@pc-oi1:~# /opt/local/sbin/pkg_add -U pkgin<br>
SSL support disabled<br>
pkg_add: Can't process <a moz-do-not-send="true"
href="https://pkgsrc.joyent.com:443/packages/SmartOS/2016Q3/x86_64/All/pkgin*"
rel="noreferrer" target="_blank">https://pkgsrc.joyent.com:443/<wbr>packages/SmartOS/2016Q3/x86_64<wbr>/All/pkgin*</a>:
Not owner<br>
pkg_add: no pkg found for 'pkgin', sorry.<br>
pkg_add: 1 package addition failed<br>
<br>
<br>
If I try to do a pkgin update:<br>
<br>
root@pc-oi1:~# /opt/local/bin/pkgin update<br>
reading local summary...<br>
processing local summary...<br>
SSL support disabled<br>
SSL support disabled<br>
SSL support disabled<br>
pkgin: Could not fetch <a moz-do-not-send="true"
href="https://pkgsrc.joyent.com/packages/SmartOS/2016Q3/x86_64/All/pkg_summary.gz"
rel="noreferrer" target="_blank">https://pkgsrc.joyent.com/pack<wbr>ages/SmartOS/2016Q3/x86_64/<wbr>All/pkg_summary.gz</a><br>
<br>
<br>
<br>
If I use wget, i can download the gz file OK, so
definitely the networking is working fine.<br>
<br>
Any thoughts?<br>
</blockquote>
<div><br>
</div>
<div>If you read through <a moz-do-not-send="true"
href="https://pkgsrc.joyent.com/changes/">https://pkgsrc.joyent.com/changes/</a>
for 2016Q3 you will notice that:</div>
<div>"The pkg_install tools now support HTTPS, and both
pkgin and pkg_add now fetch packages over HTTPS by
default."</div>
<div><br>
</div>
<div>That's a new feature for 2016Q3. Whatever quarterly
release you're currently on doesn't support HTTPS yet.</div>
<div><br>
</div>
<div>You may be able to use a <a class="moz-txt-link-rfc2396E" href="http://">"http://"</a> URL (rather than
<a class="moz-txt-link-rfc2396E" href="https://">"https://"</a>) to perform the initial upgrade procedure you
linked originally. After pkgin and the pkg_install tools
have been upgraded you should be able to switch back to
<a class="moz-txt-link-rfc2396E" href="https://">"https://"</a>.</div>
<div><br>
</div>
<div>All the same caveats about the upgrade process still
apply.</div>
<div><br>
</div>
<div>If you're upgrading a Postgres server I hope you've
dumped the database in advance of attempting such an
upgrade.</div>
<div><br>
</div>
<div>-Nahum</div>
</div>
</div>
</div>
</blockquote>
<br>
Hi Nahum.<br>
<br>
Yes, I had backups. <br>
<br>
There were only a few packages that needed to get upgrade and I know
that Joyents doesn't recommend to upgrade, but to re-provision. <br>
<br>
Jonathan Perkin gave me some guidance. <br>
<br>
In order to get back to a working state, first edit this file:
<br>
<br>
/opt/local/etc/pkg_install.conf
<br>
<br>
and change the PKG_PATH URL to use <a class="moz-txt-link-rfc2396E"
href="http://">"http://"</a> instead of <a
class="moz-txt-link-rfc2396E" href="https://">"https://"</a>.
<br>
You should then be able to follow the upgrade instructions.<br>
<br>
But I also needed to change http in:
/opt/local/etc/pkgin/repositories.conf <br>
<br>
Have a great day!!<br>
<br>
Geoff<br>
<br>
<br>
<br>
</body>
</html>