On 03/20/12 17:59, Niall Power wrote:
Hi Brock,
On 21/03/2012 11:48, Brock Pytlik wrote:
On 03/20/12 17:15, Niall Power wrote:
Hi Brock,
On 21/03/2012 09:21, Brock Pytlik wrote:
On 03/19/12 23:50, Seth Goldberg wrote:
Hi,
I'm trying to figure out how to specify an explicit dependency
from a package in the install incorporation to a package in the
osnet incorporation.
When I add an explicit depend at a specific version, pkglint
outputs an error:
ERROR pkglint.manifest005.2 duplicate depend actions in
pkg:/install/[email protected],5.11-0.175.1.0.0.13.1820
system/library/boot-management
So the questions are: how can I realy see ALL of the packages
for which pkglint detected conflicting dependencies, and how can I
specify a minimum version for a package (boot-management in this
case) when other packages in the incorporation have had a
different version added via automatic dependency generation
(pkgdepend)?
--S
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
Hi Seth,
Can you point us to the manifest that's producing this error?
Repo:
ssh://[email protected]/hg/caiman/slim_uefi
File:
usr/src/pkg/manifests/install-installadm.mf
URL:
http://src.opensolaris.org/source/xref/caiman/slim_uefi/usr/src/pkg/manifests/install-installadm.mf
I haven't pushed the change to the manifest. The addition I am
attepmting is as follows:
depend type=require \
fmri=pkg:/system/library/[email protected],5.11-0.175.1.0.0.13
I think what this error message is saying is that you have two
require dependencies on system/library/boot-management.
The installadm package has a basic API and runtime dependency on
system/library/boot-management.
However, to ensure the correct functionality and feature support is
present, the boot-management version must be build 13 or greater.
So if we do a build without the manual dependency specified, it auto
generates a dependency on
system/library/[email protected],5.11-0.175.1.0.0.11 - the
version it detected on the build machine.
Then pkglint finds 2 dependencies on boot-management and bails out.
For the sake of comparison I tried the same process against
ssh://[email protected]/hg/caiman/slim_uefi whose installadm
has no dependencies on boot-management (the dependency is introduced
in the slim_uefi repo because installadm imports bootmgmt) and
there appeared to be no pktlint or pkg issues
Ok, here are your options then:
1) Upgrade your build machine to something running build 13, from an
ON build you did yourself for example
or 2) Disable automatic dependency for the action(s) which find a
dependency on system/library/[email protected],5.11-0.175.1.0.0.11
or 3) Mark either the manually added or generated dependency on
system/library/boot-management as linted so pkglint ignores the
duplicate dependencies.
1 is not really ideal for us because we want to explicitly want to
prevent a mix and match scenario where someone would try to use
installad from build 13+ on a build 12 or earlier system.
2: Can we disable a specific automatic dependency here or is it
applied to the entire package? If it's an entire/global action then it
would have some undesirable side effects.
How do I specify this?
The pkgdepend man page describes what you need to do in detail. At a
high level, you'll tag the action(s) which produce the dependency on
system/library/[email protected],5.11-0.175.1.0.0.11 (in your case,
at minimum the file action that delivers installadm since it imports
bootmgmt) so you'd do something like 'pkg.depend.bypass-generate=bootmgmt'.
3: I tried this (by adding the property pkg.linted=true to the depend
line above. It built and linted correctly however it resulted in 2
dependencies listed against boot-management
system/library/[email protected],5.11-0.175.1.0.0.11.0
system/library/[email protected],5.11-0.175.1.0.0.13
Will this double dependency be a problem?
I am not aware of any problems this causes, but you aren't in a well
tested space at this point I think. Perhaps someone else will feel
confident to state that it is not (or is) a problem.
Brock
[snip]
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
