[pca] patchdiag.xref inconsistency
In today's patchdiag.xref, patch 119081-25 is suddenly marked as Obsolete. nut there is no sign by which patch it would have been obsoleted: usually, the synopsis (last column in xref file) contains a note Obsoleted by xx-xx. As there are two patches which require 119081-25 (namely 124628-14 and 124630-58) this leads to a situation, where patch dependencies can not be resolved. Don - can you check whether the obsoletion of 119081-25 was an error? Or maybe 124628-14 obsoletes 119081-25, but its README and patchinfo file contradict. Martin.
Re: [pca] patchdiag.xref inconsistency
Hi Martin, I'll investigate. In a nutshell the relationship between patches 119081-25 124628-14 is that patch 119081-xx was rejuvenated into patch 124628-xx. Patch rejuvenation is explained a the top of http://blogs.oracle.com/patch/entry/solaris_10_kernel_patchid_progression That said, something has happened to trigger 119081-25 being marked as obsolete (I suspect this is a result of an internal process). I can confirm that there is no patch that obsoletes 124628-xx. Stay Tuned! Best, -Don Martin Paul wrote: In today's patchdiag.xref, patch 119081-25 is suddenly marked as "Obsolete". nut there is no sign by which patch it would have been obsoleted: usually, the synopsis (last column in xref file) contains a note "Obsoleted by xx-xx". As there are two patches which require 119081-25 (namely 124628-14 and 124630-58) this leads to a situation, where patch dependencies can not be resolved. Don - can you check whether the obsoletion of 119081-25 was an error? Or maybe 124628-14 obsoletes 119081-25, but its README and patchinfo file contradict. Martin. -- Don O'Malley Manager,Patch System Test Revenue Product Engineering | Solaris | Hardware East Point Business Park, Dublin 3, Ireland Phone: +353 1 8199764 Team Alias: rpe_patch_system_test...@oracle.com
Re: [pca] Can pca check two different local sources?
Craig S. Bell wrote: Bonus: I like how it will never try MoS without a keyword -- that's exactly what I want for my clients. I can take user=dontask out of my client config file, since it will not unintentionally try MoS now. Ah, thanks for the reminder! The dontask keyword is not needed anymore, the only reason why it was added being to stop PCA trying to contact Oracle after the PCA proxy. Anyobdy using user=dontask can probably simply remove it now from pca.conf. I'm deprecating it in PCA by removing it from the documentation (but will still honor it for backward compatibility). Thank you so much, Martin. Just a week ago, I didn't know that I wanted this feature. =-) You're welcome :) and thanks for testing! Martin.
