Bart,
With the new incorporation logic in place, I'm seeing some new behavior;
is this expected?
Consider these packages:
[EMAIL PROTECTED] has in its manifest:
depend fmri=pkg:/[EMAIL PROTECTED] type=incorporate
[EMAIL PROTECTED] has:
depend fmri=pkg:/[EMAIL PROTECTED] type=incorporate
[EMAIL PROTECTED] has:
depend fmri=pkg:/[EMAIL PROTECTED] type=incorporate
The idea here is that when [EMAIL PROTECTED] is installed, an image-update
should
bring it up to the 1.1 level. And future updates along the 1.x line
will also be brought in with an image-update. If the user wants to go
to the 2.x level, they do a "pkg install [EMAIL PROTECTED]". This then brings
in
the 2.0 version, and image-updates from that point will bring in later
versions of 2.0.
Before the recent incorporation changes, this worked as described.
With the changes, the image-update part works as expected, but the
upgrade to the 2.0 version is producing the following error:
$ pkg install [EMAIL PROTECTED]
Creating Plan -
pkg: the following package(s) violated constraints:
Package pkg:/[EMAIL PROTECTED],5.11 conflicts with constraint in
installed
pkg:/jsf:
Pkg jsf: Optional min_version: 1,5.11 max version:
1,5.11 defined by: pkg:/jsf
Is this expected?
It would seem that the constraints that are defined by the packages that
one is explicitly trying to update should be ignored.
A "pkg uninstall jsf" followed by a "pkg install [EMAIL PROTECTED]" does work.
Thanks.
Tom
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
