Oracle Blog

OpenSolaris, Fault Management, etc.

Friday Mar 05, 2010

With the switch to IPS packages in being build directly in ON (and it's been a while since I did an ON build), I tried out the new build/test sequence. All in all, pretty smooth. After building my workspace, I went the route of using pkg.depotd and stood up a package repository for the repo.redist area of my workspace. The steps for this are described nicely in README.pkg. As are the pkg commands to setup the publisher.

The rest of this should be old-hat to folks that have done image-updates before. The actual upgrade:

Given when I cloned the gates, I'm running an snv_135 base, plus a few pushes. When build 136 rolls around, I plan to return to updating from the development repository and keep all the consolidations up to date.

Monday Feb 22, 2010

Build 133 of OpenSolaris released last week. Last Friday I went to perform my update, but hit a problem - Update Manager told me that my current boot environment couldn't be updated. It was late in the day and I didn't muster the energy to tackle the problem. Refreshed from the weekend, today I did.

For debugging, I switched to the pkg CLI. I started with what (more or less) the GUI is doing:

# pkg image-update --be-name opensolaris_133
WARNING: pkg(5) appears to be out of date, and should be updated before
running image-update. Please update pkg(5) using 'pfexec pkg install
SUNWipkg' and then retry the image-update.

A reasonably new issue, but I'd been fortunate not to hit it before. Prior to last week, the only package I had installed from /contrib was dmidecode which I ported. But I'd recently added a few packages. Thankfully, the bug report includes a command to find installed packages that depend on "entire":