* Robert Harryman <robert.harryman at SUN.COM> [2009-01-16 18:25]:
> I tried an update all from the opensolaris.osl.re.sfbay repository and
> got the following detail:
>
> pkg: the following package(s) violated constraints:
> Package pkg:/SUNWjavadb at 10.4.2.1,5.11-0.105 conflicts with
> constraint in installed pkg:/entire:
> Pkg SUNWjavadb: Optional min_version: 10.4.2.1,5.11-0.101 max
> version: 10.4.2.1,5.11-0.101 defined by: pkg:/entire
>
> Is this something that will eventually heal itself?
There are a couple of possibilities here:
1. pkg:/entire is the Build 101 version, and so the -0.105 version of
SUNWjavadb is constrained. Since backtracking isn't implemented
yet, you can work around it by using
pfexec pkg install SUNWjavadb at 10.4.2.1-0.101
to install the Build 101 version. (Since you mention using Update
All, I'm surprised that entire wasn't updated to the Build 105
version.)
2. pkg:/entire is the Build 105 version, but incorrectly constrains
SUNWjavadb to -0.101. That's easy to check on the
http://osol-re.sfbay/ repo (which is currently identical to
http://pkg.opensolaris.org/dev/), using pkg(1):
$ pkg contents -r -m entire at 0.5.11-0.105 | grep javadb /tmp/io
depend fmri=SUNWjavadb at 10.4.2.1-0.105 type=incorporate
So the Build 105 entire package is correct.
We can confirm that it's the first case but showing the output of
$ pkg info entire
on your system. If so, then we may have found an issue in whatever
program was issuing "update all".
- Stephen
--
sch at sun.com http://blogs.sun.com/sch/
