From owner-freebsd-current@FreeBSD.ORG Wed Feb 1 02:35:22 2006 Return-Path: X-Original-To: current@freebsd.org 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 37F6316A420; Wed, 1 Feb 2006 02:35:22 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id E134943D45; Wed, 1 Feb 2006 02:35:21 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id C3AC61A3C20; Tue, 31 Jan 2006 18:35:21 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 29EDD51BFD; Tue, 31 Jan 2006 21:35:21 -0500 (EST) Date: Tue, 31 Jan 2006 21:35:21 -0500 From: Kris Kennaway To: Sean McNeil Message-ID: <20060201023521.GA20497@xor.obsecurity.org> References: Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vkogqOf2sHV7VnPd" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Cc: Daniel Eischen , Robert Watson , current@freebsd.org Subject: Re: MFC of bump in libcom_err.so another mistake? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2006 02:35:22 -0000 --vkogqOf2sHV7VnPd Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jan 31, 2006 at 06:28:14PM -0800, Sean McNeil wrote: >=20 > On Jan 31, 2006, at 6:25 PM, Daniel Eischen wrote: >=20 > >On Tue, 31 Jan 2006, Sean McNeil wrote: > >> > >>The point I am making is that this is in the -STABLE tree, not the - > >>CURRENT tree. There is no bump of libc and I don't see any reason > >>for the libcom_err.so revision bump in -STABLE. IMHO, it didn't make > >>sense. > > > >I don't think it was -stable at the time. It was probably > >6.0-current and the version bump occurred just before the > >release. As a -current user, you are expected to be able > >to deal with this and rebuild all your ports if necessary. >=20 >=20 > This is EXACTLY what I am saying. I am not a -current user, I am a -=20 > stable user and this happened about a week ago or so. It was =20 > libcom_err.so.2.1 until just recently. The confusion seems to be that you sent your email to the wrong mailing list. Kris --vkogqOf2sHV7VnPd Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (FreeBSD) iD8DBQFD4B5oWry0BWjoQKURAgHwAJ9XR8U6N760ZSued+9ChJVXsn/UGQCbBUeX U18ET9j+kEicshcYzO1qH78= =K1PB -----END PGP SIGNATURE----- --vkogqOf2sHV7VnPd--