On Fri, Feb 19, 2010 at 03:21:44PM -0600, Will Fiveash wrote: > On Fri, Feb 19, 2010 at 03:06:14PM -0600, Shawn Walker wrote: > > On 02/19/10 02:49 PM, Will Fiveash wrote: > > > 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." > > For some reason I don't remember I had renamed fcgid.conf to > fcgid.conf-broken a while back. I did the pkg fix SUNWapch22m-fcgid > which installed the original file, did beadm destroy on the broken > opensolaris_133 BE and I am now rerunning: > > nice -n 10 pkg image-update -v --be-name opensolaris_133
Aside from the known clone permission update failed errors I am now seeing: Action install failed for 'export' (pkg://opensolaris.org/compatibility/ucb): OSError: [Errno 30] Read-only file system: '/tmp/tmpcLPIRb/export' The running system has not been modified. Modifications were only made to a clone of the running system. This clone is mounted at /tmp/tmpcLPIRb should you wish to inspect it. pkg: Could not complete the operation on /tmp/tmpcLPIRb/export: read-only filesystem Is this known and is it safe for me to boot the new BE? -- Will Fiveash Sun Microsystems Inc. http://opensolaris.org/os/project/kerberos/ Sent from mutt, a sweet text MUA
