lucia lai wrote:
Hi,
We have a bunch of packages that we want to constraint to a certain
opensolaris build. For example, if our packages are build with
opensolaris build 108, we want them to be installed only on
opensolaris 2009.6 build 108. I tried a few things with creating an
incorporate package for this purpose:
TEST 1:
Create an incorporate package, minimal-incorp, that contains all of
our packages, plus the "entire" incorporate package. Note some of our
packages have a "required" dependent type to opensolaris packages like
SUNWcsl. Here is what the minimal-incorp contains (to make it simple,
I only include a few packages):
# pkg contents -m minimal-incorp
set name=fmri
value=pkg:/[email protected],5.11-0.108:20090429T022705Z
[ snip ]
depend [email protected],5.11-0.108 type=incorporate
depend [email protected] type=incorporate
# pkg contents -m SUNWscz | grep SUNWcsl
depend [email protected] type=require
I installed [email protected],5.11-0.108 along with other
packages on a node with build 108. I then build these packages again
with build 111, and I can see the newer packages (2009.6,5.11-01.11)
in our repository. When I tried to do "image-update" to a new build
that is build with b111, it failed with:
# pkg image-update -n
Creating Plan /
pkg: pkg: the following package(s) violated constraints:
Package pkg:/[email protected],5.11-0.111 conflicts with
constraint in installed pkg:/entire:
Pkg SUNWcsl: Optional min_version: 0.5.11,5.11-0.108
max version: 0.5.11,5.11-0.108 defined by: pkg:/entire
# pkg install -n entire
No updates available for this image.
Is this expected? After I uninstall the minimal-incorp package,
"image-update" works fine.
Yep, that's expected. You've installed minimal-incorp which prevents any
forward movement of entire. If you published another minimal-incorp
pacakge in 111 with a dependency on ent...@111, then image-update would
work (I think).
TEST 2:
I then removed "entire" from minimal-incorp, and re-did the above
test. Everything is same except "minimal-incorp" does not contain
"entire". But the same error is reported:
# pkg image-update -nv
[ snip ]
+pkg:/[email protected],5.11-0.111:20090427T003658Z
+pkg://re.sfbay/[email protected],5.11-0.111:20090418T200225Z
+pkg:/[email protected],5.11-0.111:20090427T003551Z
pkg: pkg: the following package(s) violated constraints:
Package pkg:/[email protected],5.11-0.111 conflicts with
constraint in installed pkg:/entire:
Pkg SUNWcsl: Optional min_version: 0.5.11,5.11-0.108
max version: 0.5.11,5.11-0.108 defined by: pkg:/entire
However, "pkg install entire" will get the new
[email protected],5.11-0.111 installed. Is those expected behave? I'd
appreciate if someone can confirm if these are expected or not, so we
can define what to do with our incorporate package.
This doesn't match my expectations. I'd ask to see the output of 'pkg
contents -m minimal-incorp' to make sure that the package installed
doesn't contain the entire incorporation.
Also, can you provide the manifests for
[email protected],5.11-0.111? I haven't seen that anywhere.
Besides above questions, I also have another few other questions that
are related to above usage of incorporate package:
- Does "pkg image-update" install the packages with newest version
string? Is there a way to let "image-update" to install the packages
with a specific version? E.g., the newest version in the repository is
0.5.11,5.11-0.111. I installed build 108, but I want to use
"image-update" to get to build 109. Is this do-able with "image-update"?
Not currently, we know we need to provide this functionality at some
point though.
- Does "pkg install [email protected],5.11-0.111" take the node to the
same state as "pkg image-update" does? The version is same, but is the
system really the same?
Not necessarily. Among other things, image-update would update things
not in entire (like virtual box for example).
Thanks a lot for your help,
- Lucia
Thanks,
Brock
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
