On 02/19/10 02:49 PM, Will Fiveash wrote:
> Using our internal pkg repo I saw a bunch of errors when I ran from a BE
> running snv_129:
>
> nice -n 10 pkg image-update -v --be-name opensolaris_133
>
> Note that the first time I ran that it told me I needed to update the
> pkg utility so I ran:
>
> nice -n 10 pkg install SUNWipkg
>
> which succeeded then I reran:
>
> nice -n 10 pkg image-update -v --be-name opensolaris_133
...
> ------------------------------------------------------------
> No entry found for driver (clone) in file (/tmp/tmpIOJ_lL/etc/minor_perm).
> ------------------------------------------------------------
...
That warning can be ignored, see the release notes.
> ------------------------------------------------------------
> No entry found for driver (clone) in file (/tmp/tmpIOJ_lL/etc/minor_perm).
> ------------------------------------------------------------
> Removal Phase 10664/317832Action removal failed
> for 'etc/apache2/2.2/conf.d/fcgid.conf'
> (pkg://opensolaris.org/SUNWapch22m-fcgid):
> OSError: [Errno 2] No such file or directory:
> '/tmp/tmpIOJ_lL/etc/apache2/2.2/conf.d/fcgid.conf'
...
> OSError: [Errno 2] No such file or directory:
> '/tmp/tmpIOJ_lL/etc/apache2/2.2/conf.d/fcgid.conf'
To quote Danek's response to another:
"You're likely running into
14570 file install logic discommoded by excessive cleverness if
preserve=rename*
because you've modified this file which was tagged with
preserve=renamenew. Move the file aside (so as not to lose the
contents), and then run "pkg fix SUNWapch22m-fcgid" which will put the
original contents of the file back in place, and the upgrade should
work. Afterwards, you can put your contents back."
> Is it safe for me to boot the 133 BE or do I need to fix something?
No, you need to apply the workaround above.
Cheers,
--
Shawn Walker
