From owner-freebsd-stable@freebsd.org Sun Aug 16 17:47:08 2015 Return-Path: Delivered-To: freebsd-stable@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id DDA209BB63F for ; Sun, 16 Aug 2015 17:47:08 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AA98A103F for ; Sun, 16 Aug 2015 17:47:08 +0000 (UTC) (envelope-from kpaasial@gmail.com) Received: by iodv127 with SMTP id v127so113531983iod.3 for ; Sun, 16 Aug 2015 10:47:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PeBP9JuEUsmzWK8zV6TwXQqgu1gKpYQpVXWdR7G3GRo=; b=kC64O4414Cdbn+bEWd1MLhfIFO+Q9LnrOMNODIVete931XuNZCSJNbFV3BsTopgcQ1 XeWuQBdd4e+KlGaCYf1YNIryQywYnS5yaCx7iXDPGOVB6xzqYcJRBT9PDBWZzoNC+LCU a4beb6Zm7pkou9i75Q9GMSVSHaty0Mqbsscsoc2YSAl7i4IGIuX3WvrbZ3zL2JjifJ9T hl+yBunRQJsB9K1q2lCwpUjVa0Dhur0LAYjuS1BkRYG6KmXx4jqmJVXgSrp0HrOayPTt sV0mpbrnM9qWSgjy4qcbSVFJZIAIxAUA5fz62NoT4Bzu/S6Q8PRXHM229io/WPhtU+kV nXLw== MIME-Version: 1.0 X-Received: by 10.107.164.41 with SMTP id n41mr476420ioe.197.1439747228073; Sun, 16 Aug 2015 10:47:08 -0700 (PDT) Received: by 10.107.131.163 with HTTP; Sun, 16 Aug 2015 10:47:08 -0700 (PDT) In-Reply-To: <55D0CB2B.2010309@janh.de> References: <55D0CB2B.2010309@janh.de> Date: Sun, 16 Aug 2015 20:47:08 +0300 Message-ID: Subject: Re: libopie problems after upgrade to 10.2 From: Kimmo Paasiala To: Jan Henrik Sylvester Cc: Chris Anderson , stable-list freebsd Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Aug 2015 17:47:09 -0000 On Sun, Aug 16, 2015 at 8:40 PM, Jan Henrik Sylvester wrote: > On 08/15/2015 20:47, Chris Anderson wrote: >> just upgraded from 10.1-RELEASE-p16 to 10.2-RELEASE using freebsd-update. >> >> after the upgrade, I began getting errors because pam_opie.so.5 has an >> unsatisfied link to libopie.so.7 (my system only has libopie.so.8). >> >> I notice a fresh install of 10.2-RELEASE does indeed contain libopie.so.7, >> so I'm curious how I managed to get into this state in the first place and >> whether it is anything I should worry about. This machine has only been >> upgraded using freebsd-update and I'm pretty sure it started from >> 10.0-RELEASE. > > I did the same update using freebsd-update and I do not have > libopie.so.8 that should not be in any 10.X-RELEASE. > > libopie.so.8 was in stable/10 shortly after 10.0-RELEASE, but was set > back again to libopie.so.7 between 10.1-RC1 and 10.1-RELEASE: > > https://svnweb.freebsd.org/base/releng/10.1/lib/libopie/Makefile?view=log&pathrev=273169 > > Your problem was probably not introduced during the 10.1-RELEASE to > 10.2-RELEASE upgrade but earlier. > > I have a system that had just about every BETA, RC, and RELEASE starting > from 9.0-RC1 using freebsd-update binary upgrades only, including some > BETA or RC of 10.1 with libopie.so.8... that system has only > libopie.so.7 now as it should have. Maybe you forgot the "removing of > old libraries" step of "freebsd-update install" after "freebsd-update > upgrade" around 10.1-RC3, because you did not expect it on a stable branch? > > Cheers, > Jan Henrik As far as I know freebsd-update(8) should handle the obsolete files automatically, it's only when you're building from source you have to remember to do 'make delete-old delete-old-libs'. If freebsd-update(8) fails to delete the obsolete files it's a flaw in it that should be reported with a PR. -Kimmo