* Glenn Lagasse ([email protected]) wrote: > 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
Just to follow up, this turned out to be caused by 6945225 which was fixed in 147 by 6974588. Once I updated my workspace with that change, a rebuild and upgrade worked just as I expected them to. Thanks all, Glenn _______________________________________________ on-ips-dev mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/on-ips-dev
