Robin Axelsson wrote: > I did quite exactly that but in the normal boot environment, but since > you insisted that I should do all this in maintenance mode I ran 'beadm > destroy <new-BE>', added '-s', booted the original image in maintenance > mode and executed exactly the same commands you just listed. But still, > there are unfixed errors (although they are fewer now).
Given the nature of the problems you're running into (I'm guessing; I still haven't seen any of the pkg verify output), running "pkg fix" with the older bits is unlikely to correct the problem. Running "pkg fix" with the newer bits is more likely to do so. That's why I'm suggesting that you run "pkg fix" while running the upgraded BE. Because one of the packages is SUNWcs, then "pkg fix" will fail unless you do it on an alternate BE, which is why I suggested creating a new BE to operate on. Maintenance mode isn't necessary, but if the system won't come up further, then it can be a useful place to start. > The faulty packages are now: > pkg://opensolarisdev/library/python-2/pyopenssl-26 > pkg://opensolarisdev/library/desktop/gtk2 > pkg://opensolarisdev/library/SUNWcs > pkg://opensolarisdev/library/system/boot/real-mode > pkg://opensolarisdev/library/system/library > pkg://opensolarisdev/library/gnome/preferences/control-center It would be worth seeing the output of this. If it's long, you can post it to some site and give us the URL. Danek
