* Danek Duvall ([email protected]) wrote: > Glenn Lagasse wrote: > > > That doesn't look nearly correct enough. Where are all the other > > updates from on-nightly that should be applied? > > pkg install -nv $(pkg list -H consolidation/\*-incorporation | awk > '{print $1}') > > save the output to a file, and look for FAIL: in there. If you need help > interpreting, stick the log up on cr.os.o and point us at it.
Not terribly interesting, other than to point out that I missed a step that onu performs (uninstall entire) r...@praetorian> cat /tmp/update.txt Solver: [ Variables: 2499 Clauses: 18665 Iterations: 8 State: Succeeded] Timings: [phase 1: 0.384, phase 2: 0.803, phase 3: 0.002, phase 4: 0.000, phase 5: 0.822, phase 6: 0.004, phase 7: 0.046, phase 8: 5.322, phase 9: 0.000, phase 10: 1.713, phase 11: 0.092] Maintained incorporations: pkg://opensolaris.org/[email protected],5.11-0.143:20100706T174929Z Package version changes: No updates necessary for this image. I uninstalled entire in the new BE and then tried the image-update again. This time, the output was much more verbose. However, it mostly showed packages being upgraded to build 145 (the latest in ipkg.sfbay/dev presumably). There were two packages listed to be updated for 146: r...@praetorian> grep 146 /tmp/update.txt pkg://opensolaris.org/developer/build/[email protected],5.11-0.143:20100706T035323Z -> pkg://on-nightly/developer/build/[email protected],5.11-0.146:20100803T000233Z pkg://opensolaris.org/developer/opensolaris/[email protected],5.11-0.143:20100706T040218Z -> pkg://on-nightly/developer/opensolaris/[email protected],5.11-0.146:20100803T000233Z But nothing else. I ran the command you suggested and the output looks fairly similar to what image-update spit out (once I'd uninstalled entire). There weren't any FAIL messages and there weren't any references to packages from 146. I've uploaded that output at: http://cr.opensolaris.org/~glagasse/generic_data > > If I try to install my new beadm package from on-nightly I get: > > > > [1] r...@praetorian> pkg -R /a install -v install/beadm > > Creating Plan /Planning for install failed: > > > > > > pkg: No matching version of install/beadm can be installed: > > pkg://on-nightly/install/[email protected],5.11-0.146:20100803T000245Z: This > > version is excluded by installed incorporation > > pkg://opensolaris.org/consolidation/install/[email protected],5.11-0.143:20100706T015509Z > > > > Now, this doesn't make any sense. Yes, beadm is listed in the > > install-incorporation in build 143. But, that was removed in build 144 > > which ipkg.sfbay/dev knows about (which is my configured opensolaris.org > > publisher). > > If the build 143 version of install-incorporation is installed, and you're > not attempting to upgrade it at all, then whatever constraints it includes > are in force. If you were to run "pkg install > [email protected]", then it would drag the install > consolidation forward to build 144, possibly leaving beadm behind, which > you could then upgrade freely. (Though I can't say I understand why it's > not constrained in any way.) It will be constrained when I integrate into ON. It'll be constrained by the osnet-incorporation. Since we're moving beadm/libbe out of slim_source and into ON (and thus between consolidations/incorporations) I had to unconstrain it from it's old incorporation in a build prior to it showing up in the osnet-incorporation (which happened in 144). Thanks, Glenn _______________________________________________ on-ips-dev mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
