On 10/13/10 04:49 PM, Vijay S Balakrishna wrote:
My base workspace (no code changes to newly created snv_149 rev workspace)
system/library manifest has
depend fmri=driver/crypto/dprov type=require
Don't see that in official bits @ ipkg.sfbay
http://ipkg.sfbay.sun.com/dev/manifest/0/system%2Flibrary%400.5.11%2C5.11-0.149%3A20100924T032738Z
I think it is causing my DC build failure (output below). Is this known
issue? Any workaround?
I see today ipkg.sfbay has snv_150 in system/library manifest doesn't
contain "depend fmri=driver/crypto/dprov type=require"? Why developer
build manifest is different?
Because your build depends on the developer crypto bits, which are
provided by dprov. The gatekeepers have special gatekeeping keys to
sign their bits with, so they don't need this Oracle-internal package.
This is expected, and as designed. The only way to avoid having a dprov
dependency is to build with the ON gatekeeper crypto binaries.
However, dprov is available only in your ON repo.extra because it isn't
a redistributable package.
The easiest way to resolve this is to add the repo.extra from the same
directory as your repo.redist into the additional publisher list for DC.
liane
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
