Date: Tue, 31 Jan 2006 18:28:14 -0800 From: Sean McNeil <sean@mcneil.com> To: Daniel Eischen <deischen@freebsd.org> Cc: Robert Watson <rwatson@freebsd.org>, current@freebsd.org Subject: Re: MFC of bump in libcom_err.so another mistake? Message-ID: <ED92AAA4-F610-4DC1-A8C5-FDF646D083AF@mcneil.com> In-Reply-To: <Pine.GSO.4.43.0601312122360.4643-100000@sea.ntplx.net> References: <Pine.GSO.4.43.0601312122360.4643-100000@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jan 31, 2006, at 6:25 PM, Daniel Eischen wrote: > 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. This is EXACTLY what I am saying. I am not a -current user, I am a - stable user and this happened about a week ago or so. It was libcom_err.so.2.1 until just recently.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ED92AAA4-F610-4DC1-A8C5-FDF646D083AF>