All, * Glenn Lagasse ([email protected]) wrote: > Hi Brock, > > * Brock Pytlik ([email protected]) wrote: > > I'm not sure why this is happening. The best way I can think of to > > attack this problem would be to find a package that was installed in > > the second image-update that wasn't in the first, then go back to > > the original be and install (with the -v option) that package plus > > entire and the other consolidations all with the explicit version > > listed that you expected the image-update to take you to. > > Presumably, that will fail and we might be able to figure out what > > went wrong from the output it shows. > > Ok, something really odd is going on. After struggling all day on > friday to try and diagnose this problem I came in yesterday and > magically upgrades started working the way I expected (without any code > changes in my workspace). After building sparc and x86 archives fresh > last night, today upgrades fail again.
So, thanks to some help from Danek it appears that the reason my upgrades aren't working today is that my built ON repo doesn't contain an osnet-incorporation. Now, I've been doing full builds of this workspace using nightly with options -ACDlmprfztn and the output from nightly is clean (no flagged errors/warnings). When I look through the nightly log, I see the following for osnet-incorporation: glaga...@praetorian> grep osnet-incorporation nightly.log Processing synthetic manifest osnet-incorporation.mf Skipping dependency generation for osnet-incorporation The same search in a build workspace of onnv-clone: (glaga...@indiana-build:/export/home/glagasse/onnv-clone/log/log.2010-07-31.17:12)$ grep osnet-incorporation nightly.log Processing synthetic manifest osnet-incorporation.mf Skipping dependency generation for osnet-incorporation Publishing osnet-incorporation to redist repository [31/Jul/2010:15:57:18] pkg://on-nightly/consolidation/osnet/[email protected],5.11-0.146:20100731T215544Z Publishing osnet-incorporation to redist repository [31/Jul/2010:17:08:59] pkg://on-nightly/consolidation/osnet/[email protected],5.11-0.146:20100731T230723Z So clearly something is amiss. However, there is no information I can find in the nightly log for my build workspace on why osnet-incorporation (or osnet-redist or osnet-extra) failed to be published. If anyone is curious, that log can be found at: /net/praetorian.us.oracle.com/backup_tank/glagasse/ONNV_SNAP_BUILD_AREA/onnv-clone/log/log.2010-08-02.17:53/nightly.log Any hints on how to proceed gratefully accepted. Thanks, Glenn _______________________________________________ on-ips-dev mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
