On 12/23/11 14:05, David Sechrest wrote:
On Dec 23, 2011, at 2:01 PM, Brock Pytlik wrote:
On 12/23/11 08:42, David Sechrest wrote:
[snip]
'pkg fix' was quite busy but I was then able to upgrade to b165. I
then set trust-anchor-directory back to
/etc/certs/CA but got the same error. To upgrade to GA I had to
change it again.
I'm glad you were able to update.
The problem is with the xvm-4200m2-42.OpsCenter_cert.pem certificate.
Specifically, the cert file is empty. Indeed, several of the files in
the directory you sent me are empty. Obviously, pkg shouldn't
traceback in this situation, but it's also strange that you have
empty files there.
I'm not sure why they are there either as the system is used by
others. Would simply deleting them fix the issue?
thanks
Dave
It should.
Brock
Hth,
Brock
thanks
Dave
Setting the trust-anchor directory to an empty dir should get you
around the issue you're seeing above. I'd be interested to know if
pkg fix changed anything under /etc/certs/CA.
Assuming that this run of pkg fix didn't abort, you should be able
to safely update to build 165.
After you've updated to build 165, you should set your
trust-anchor-directory property back to being /etc/certs/CA.
I've filed bug 19114 for the issue that we traceback at all.
Hth,
Brock
thanks
Dave
After updating, you can then reset those policies to the default.
If I'm completely wrong about this, the above won't help at all.
-Shawn
---
David SechrestPhone: (408)276-5800 x15800
Systems Management Email: [email protected]
<mailto:[email protected]>
Oracle Corporation
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
