On 02/27/12 12:58, Alan Coopersmith wrote:
On 02/27/12 12:45 PM, Jan Parcel wrote:
OK, so the workaround is to uninstall entire then uninstall
onsolidation/userland/userland-incorporation.
You shouldn't need to do either, just:
pkg change-facet facet.version-lock.library/security/openssl=false
(This is possible because userland-incorporation contains facets on the
depend type=incorporate lines that allow users to disable them - you'll
find that ON for instance, only does so on a very limited number of
packages
so that you can't end up in a bad situation, such as having a kernel
& libc
mismatch.)
However, I do not think that updating openssl-1.0.0e to
openssl-1.0.0g should
force customers to remove those.
When the SRU is published to customers, the incorporations for that
SRU will
have the right versions. Customers only need to do icky things to their
incorporations if they want to use versions other than the ones that
Oracle
tested as a set & recommends for use.
OK, then the issue was only with the nightly builds under /support, I
assume.
In that case I'll try to update the wiki covering how to build/create
fixes for userland SRUs.
THANKS all!
_______________________________________________
userland-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/userland-discuss
