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

[Dan McDonald]

On Sep 18, 2014, at 8:58 PM, Josef 'Jeff' Sipek <jeffpc at josefsipek.net> 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