* James Carlson (James.D.Carlson at Sun.COM) wrote: > > > but somehow new versions of both sysiduilib and libnslib.so.1 > > > (which both depend on that file) weren't delivered into the image > > > you're using. > > But, why is this so? Won't they compile the entire gate for each > > build? > > > > And how do we correct this now? > > They're both delivered via SUNWadmap, so I'd suspect that a > misbegotten patch was applied here. > > Looking at patchstatus.sfbay, I see that CR 4649122 was delivered by > patch IDs 119081-11 and 119252-09. Looking at that latter one, I see > that it delivers /usr/sbin/sysiduilib but does *NOT* deliver the > /usr/snadm/lib/libnsnis.so.1 that was also changed. > > "Oops." I think 119252 needs to be fixed, and may need to be > bad-patched. It's broken. > > Surprisingly, even though this was broken back in the -09 version, the > -15 version still has the same problem. > > Another issue to resolve here is how this sort of an error could have > happened in the first place. Is the Install gate lacking the > 'protcmp' and 'wsdiff' tools? I don't know how patches are validated > there, but something slipped through the cracks.
I can't speak definitively for the patch gates (though I'm pretty sure what I'm about to say applies equally there as well) but the answer to your question is yes and yes. Certainly in the Nevada gate they don't exist. -- Glenn Lagasse KISS/Approachability Sun Microsystems, Inc. x21293, 781-442-1293
