[Moved to pkg-discuss, as that's the appropriate venue for help on the pkg software]
Your results are expected, though admittedly complicated by your operational situation; see the notes at http://hub.opensolaris.org/bin/view/Project+pkg/rtinotes in particular, the note on Revision 1431 / 62b6033670e4, which is included in build 127. Dave Frank Allan wrote: > Does anyone know if I should be able to install a b127 repo on a machine > running b125. > > I have both the 125 and 127 repos, but the only option I have for booting > machines at the moment is b125 (since I only have sparc). > > I have tried on two different machines (V240 and T2000) and in both cases I > can setup a b125 repository successfully and install packages from it. > > However, using exactly the same process with b127 repo it fails on both > machines with a message saying (copied in as I have no network connectivity > form test systems to external network - blank lines for clarity only): > ______________________________________ > Executing start method ("/lib/svc/method/svc-pkg-depot start"). > option_ops: [ -d /repo127/repo -p 3333 -s 10 -t 60 > --cfg-file=/etc/repo127_cfg_cache --content-root=/usr/share/lib/pkg > --log-access=none -log-errors=stderr --ssl-cert-file=none > --ssl-dialog=smf:svc:/application/pkg/server:default --ssl=key-file=none] > > Dropping fork(2) and exec(2) privileges. > > Dropping net_privaddr privilege. > > ppriv -s > A=basic,-file_link_any,-proc_info,-proc_session,net_privaddr,-proc_fork,-proc_exec > > > -e /usr/lib/pkg.depotd --readonly -d /repo127/repo -p 3333 -s 10 -t 60 > --cfg-file=/etc/repo127_cfg_cache --content-root=/usr/share/lib/pkg > --log-access=none -log-errors=stderr --ssl-cert-file=none > --ssl-dialog=smf:svc:/application/pkg/server:default --ssl=key-file=none > > pkg.depotd: an error occurred while trying to initialize the depot > repository > directory structures: > The specified repository root '/repo127/repo' is not a valid repository. > ________________________________________ > > I have reloaded the 127 repo isos (both match the md5 sums) and problem is > consistent. I can switch back to the 125 repo and it works fine. > > It looks like the 127 repo can only be setup on a 127 system, but this > would > be crazy as you would have to have a 127 system first and to get that you > would need the repo. I am on a closed customer network so the only way to > upgrade is using the repo, so having to have an updated system to load the > repo is never going to work. > > Is it a requirement for the OS build to be equal or greater than the > repo it > hosts, or is there something else happening? I am sure I would have seen > something on the lists by now if the repo was bad, and I know I have a good > copy because the md5 sums match. However this is repeatable on two > different > systems and the things they have in common are SPARC and build 125. > > Cheers > Frank > > > _______________________________________________ > caiman-discuss mailing list > caiman-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
