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

[Dan McDonald]

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.

I haven't yet gone and ripped things out of the bloody repo, but I'm planning on just replacing it with a brand new set of r151013 packages once r151012 is out the door and the r151013 ISO & USB get burned.

Sorry if this causes you any inconvenience, but since it is the bloody repo, sometimes things will get messy.

Thanks,
Dan