From owner-freebsd-current@FreeBSD.ORG Mon Apr 28 11:09:06 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6604C37B401; Mon, 28 Apr 2003 11:09:06 -0700 (PDT) Received: from MX4.estpak.ee (ld1.estpak.ee [194.126.101.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id AE8A143F93; Mon, 28 Apr 2003 11:09:04 -0700 (PDT) (envelope-from kalts@estpak.ee) Received: from kevad.internal (80-235-38-44-dsl.mus.estpak.ee [80.235.38.44]) by MX4.estpak.ee (Postfix) with ESMTP id 8F22A1D0010; Mon, 28 Apr 2003 21:09:02 +0300 (EEST) Received: (from vallo@localhost) by kevad.internal (8.12.9/8.12.9/Submit) id h3SI919N001113; Mon, 28 Apr 2003 21:09:01 +0300 (EEST) (envelope-from vallo) Date: Mon, 28 Apr 2003 21:09:01 +0300 From: Vallo Kallaste To: "Jacques A. Vidrine" , Lowell Gilbert , freebsd-current@FreeBSD.org Message-ID: <20030428180901.GA1009@kevad.internal> References: <20030428075916.GA53857@myhakas.internal> <20030428190209.A21656@dilbert.robbins.dropbear.id.au> <20030428075916.GA53857@myhakas.internal> <20030428080505.GA1474@chihiro.leafy.idv.tw> <20030428075916.GA53857@myhakas.internal> <20030428105521.GB2676@madman.celabo.org> <20030428111859.GA2923@madman.celabo.org> <44n0iallyq.fsf@be-well.ilk.org> <20030428144846.GA29465@madman.celabo.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030428144846.GA29465@madman.celabo.org> User-Agent: Mutt/1.5.4i-ja.1 Subject: Re: Somethings still up with new NSS? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kalts@estpak.ee List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Apr 2003 18:09:06 -0000 On Mon, Apr 28, 2003 at 09:48:46AM -0500, "Jacques A. Vidrine" wrote: > > > So until I add logic to pwd_mkdb(8) to recognize and deal > > > appropriately with this situation, it is best to run pwd_mkdb once > > > manually after the NSS commit. > > > > Wouldn't an easy solution be to put a comment into master.passwd > > itself? It can serve as a warning, and it will change the CVS tag > > (thus, mergemaster will offer to rebuild the database after a proper > > merge). > > I don't think this would give very good coverage ... usually one does > not merge master.passwd. Clever thought, nonetheless. > > Anyway, I've already committed a workaround to pwd_mkdb. I'm beating the dead horse now, but what has happened to idea of tracking such events in the UPDATING file? I did remember the NSS update when I updated my system and specifically looked into UPDATING to get some clues beforehand, but found nothing. This has two sides, of course, it had probably saved my ass but the bug remained. -- Vallo Kallaste