It looks like there was an old errant hg process holding onto onnv/onnv-gate, so it never got unmounted (and thus remounted).
I've killed it now, which forced the remount, and it looks like it should be serving the correct onnv-gate now. cheers, steve On Thu, May 03, 2007 at 08:36:16PM -0700, Mike Kupfer wrote: > >>>>> "Rich" == Richard Lowe <[EMAIL PROTECTED]> writes: > > Rich> Note that due to what appears to be yet another autofs quirk, this > Rich> is still not visible as done when pulling from onnv-gate. > > Hmm. I just updated my local copy, and I only see one changeset that is > tagged with "onnv_64***", plus a changeset for the tagging: > > changeset: 4143:7631e6224d41 > user: [EMAIL PROTECTED] > date: Mon Apr 30 23:50:39 2007 -0700 > summary: Added tag onnv_64*** for changeset 0d7fa83a8b00 > > changeset: 4142:0d7fa83a8b00 > tag: onnv_64*** > user: michen > date: Mon Apr 30 17:48:25 2007 -0700 > summary: 6548196 Multiple memory corruption vulnerabilities in > nscd(1M) > > Is this what you see? > > Rich> Mike, Are you able to (or do you know who *is* able to) kick > Rich> things such that we're seeing reality? > > I've pinged the ops list. I thought someone had taken over ownership > while Steve is away, but we'll see what they say. > > mike -- stephen lau // [EMAIL PROTECTED] | 650.786.0845 | http://whacked.net opensolaris // solaris kernel development _______________________________________________ tools-discuss mailing list [email protected]
