[OmniOS-discuss] Bloody release (r151011) has been toxic since mid/late-August

[Dan McDonald]

Yeah, you'll have to start from your previous BE to get to 012 or 013.  You can use beadm(1M) to clone a new BE from the old one, then use pkg -R.  Eg.

beadm create -e oldbe newbe
beadm mount newbe /mnt
pkg -R /mnt set-publisher....
pkg -R /mnt update 

The only gotcha is any data from your current BE SHOULD be migrated to "newbe".

Dan

Sent from my iPhone (typos, autocorrect, and all)

> On Sep 19, 2014, at 4:34 PM, Richard PALO <richard at netbsd.org> wrote:
> 
> 
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Le 19/09/14 04:44, Dan McDonald a écrit :
>> 
>> On Sep 18, 2014, at 8:58 PM, Josef 'Jeff' Sipek
>> <jeffpc-PM1Ls4bqFqUFEYicpp4bmg at public.gmane.org> wrote:
>> 
>>>> On Thu, Sep 18, 2014 at 08:40:47PM -0400, Dan McDonald wrote:
>>>> I've been getting r151012 ready to ship, but while doing so, I
>>>> discovered some bad news that, thankfully, will not affect
>>>> r151012 from a user's point of view.. unless you wished to
>>>> upgrade from bloody (r151011) to r151012 or the new r151013
>>>> bloody.
>>>> 
>>>> As of the update of CherryPy to 3.5.0 (which was subsequently
>>>> ripped out of omnios-build, but lingers in the bloody repo),
>>>> the http://pkg.omniti.com/omnios/bloody/ repo is toxic.  If
>>>> you've upgraded your bloody machine and have CherryPy 3.5.0
>>>> (pkg list -v cherrypy), your BE is toxic as well.
>>>> 
>>>> If you have a BE where the installed CherryPy is not 3.5.0
>>>> (e.g. if you last updated on the August 9th bump), you can
>>>> actually upgrade safely to r151012 or the new bloody, r151013.
>>>> Otherwise, you'll have to reinstall your bloody box with
>>>> r151012 or the r151013 version of bloody off a CD, USB, etc.
>>> 
>>> Uninstalling it isn't an option?
>> 
>> It's a rat's nest of dependencies, since pkg.depotd depends on
>> CherryPy directly (and its requirement of a specific version or
>> earlier is how I discovered the mess in the first place).
>> Godawful, trust me.
>> 
>> Old BEs before the CherryPy update are your best bet.
>> 
>> Dan
>> 
> Dan, if I understand correctly... if my current BE has:
>> pkg://omnios/library/python-2/cherrypy@3.5.0,5.11-0.151011:20140902T192935Z
> 
> but
>> 
> a previous BE
>> pkg://omnios/library/python-2/cherrypy@3.2.2,5.11-0.151011:20140723T191919Z
> 
> the
>> 
> only recourse is to boot the previous BE and upgrade to lastest.
> No other way?
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
> 
> iQEcBAEBAgAGBQJUHJNtAAoJECAB22fHtp27wckH/ikDZ1ioqNC9AToEf3Ex2fhS
> 1I9JNRUcWtYyraw7hKxIDBqPxFnDa64GiiMESAWOd23lV7/UbtNc6miX9Q+5Ob7R
> pLo5QBx2oU+kijCq6bshktgbvbTUpaHT2R3budnwZDFZ6retuiH4GCR3qR1gxl9q
> wuMQ8+5X5OQ+zNdf5+dYAzpcZzsK000ji686btS02nwjRJTFRwgRNRWNR4ZPVgS8
> aKw1rdAEh/7M7wvR5jnfSuxvng0GxfxqHGhDbvb2C/jDdDZKft7Cxwf6dsiYuE6k
> OnuSWP3pJOnsmOlq4h8IYKlUBwfpaJDR4/pHni8MvDkDbplvb6AQhGOhQkG3Qks=
> =sG4A
> -----END PGP SIGNATURE-----
> 
>