From owner-freebsd-current@FreeBSD.ORG Wed Feb 1 11:14:33 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 6CFAB16A429; Wed, 1 Feb 2006 11:14:33 +0000 (GMT) (envelope-from past@ebs.gr) Received: from fly.ebs.gr (dslcustomer-239-113.vivodi.gr [83.171.239.113]) by mx1.FreeBSD.org (Postfix) with ESMTP id 654E143D48; Wed, 1 Feb 2006 11:14:31 +0000 (GMT) (envelope-from past@ebs.gr) Received: from ebs.gr (root@hal.ebs.gr [10.1.1.2]) by fly.ebs.gr (8.12.9p1/8.12.9) with ESMTP id k11BETSg020810; Wed, 1 Feb 2006 13:14:29 +0200 (EET) (envelope-from past@ebs.gr) Received: from [10.1.1.158] (ajax.ebs.gr [10.1.1.158]) by ebs.gr (8.13.3/8.12.11) with ESMTP id k11BFNst062450; Wed, 1 Feb 2006 13:15:23 +0200 (EET) (envelope-from past@ebs.gr) Message-ID: <43E09814.8080707@ebs.gr> Date: Wed, 01 Feb 2006 13:14:28 +0200 From: Panagiotis Astithas Organization: EBS Ltd. User-Agent: Thunderbird 1.5 (X11/20060116) MIME-Version: 1.0 To: Sean McNeil References: <1138476952.86610.1.camel@triton.mcneil.com> <20060131235035.B95776@fledge.watson.org> <7B0411F5-FCBC-40BC-94CA-2B8AA13FA783@mcneil.com> In-Reply-To: <7B0411F5-FCBC-40BC-94CA-2B8AA13FA783@mcneil.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: 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 11:14:33 -0000 Sean McNeil wrote: > > On Jan 31, 2006, at 3:52 PM, Robert Watson wrote: > >> >> On Sat, 28 Jan 2006, Sean McNeil wrote: >> >>> I was wondering if this was on purpose. Seems like there is no good >>> reason that it was done on -STABLE and it has really messed up >>> everything here for me. >>> >>> libcom_err.so.2 bumped to libcom_err.so.3. >> >> It was on purpose, but not necessarily for a good reason. Could you >> be more specific about "really messed up everything here for me", >> which sounds a lot to me like "and all hell broken loose"? I assume >> there's some sort of library and application versioning problem, but >> some details would be helpful. > > I had several big packages that depended on kerberos and they all broke > because: > > 1) libcom_err.so.2.1 was moved to /usr/local/lib/compat/pkg/ > 2) The symlink libcom_err.so.2 was removed and nothing was placed in > compat. > > I finally got smart and just added an entry to libmap.conf and so I'm > not "really messed up...". That was not accurate in the first place :) > >> In principle, other than potentially requiring compat libs to run old >> binaries even though that may not strictly have been necessary, it >> seems likely that a binary depending on the old libcom_err depends >> also on an old libc. On the other hand, I consider library version >> number interactions to be mysterious, and likely have missed the >> point. :-) > > 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. Do you, by any chance, have security/heimdal installed? If so, this seems like a portupgrade job. Cheers, Panagiotis