From owner-freebsd-stable@freebsd.org Sun Aug 16 18:05:03 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 73EC09BB966 for ; Sun, 16 Aug 2015 18:05:03 +0000 (UTC) (envelope-from me@janh.de) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.13]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2049F19A5 for ; Sun, 16 Aug 2015 18:05:02 +0000 (UTC) (envelope-from me@janh.de) Received: from [192.168.178.36] ([87.174.244.233]) by mrelayeu.kundenserver.de (mreue104) with ESMTPSA (Nemesis) id 0LuLSB-1YknaQ25KB-011jK9; Sun, 16 Aug 2015 20:04:49 +0200 Subject: Re: libopie problems after upgrade to 10.2 To: Kimmo Paasiala , Chris Anderson References: <55D0CB2B.2010309@janh.de> Cc: stable-list freebsd From: Jan Henrik Sylvester X-Enigmail-Draft-Status: N1110 Message-ID: <55D0D0C0.2000605@janh.de> Date: Sun, 16 Aug 2015 20:04:48 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:ijHnHlNSx0QN/LHGlKhUcY4zW1P4NaAhLKT1Y4rYRIoXjiuiVOD liIzq1Ev9UXEUVnnAsJJZBu6gyg8m7WORAQIbt71rXmJcnNvh9bJuzTJa5DavU9dZQOLgIE BH9wT4B5LEwEEjREAd70SYWnq52l3olgDpocusjUs5dGD4ZrqGDaRw3Eo8/kIYxYRRfpBS1 aciUZgCc46RqG/HRTOO/w== X-UI-Out-Filterresults: notjunk:1;V01:K0:lbqeY1s2e7M=:5wlZpQzL2GI4PJUh1dmC3m eVv75HcFDijAAso2AXFTJHXm9Yth+xzq7qjXxTaAdVWbp2YO9dOnC75A/FEcv+xA/bQiyK5vk T6DUEWoDJDNE6J2gPOcx5R/IoBlTON9HzdljlvtwOXm1jO3wAgMag3s/1FgwCq5zcp4sQlSfT DK9XhfRU74HnIh8HNuO+5No5EgU9pVtMQeZGdbEHQSrfyuQwKQd0HWoV0lIwZ6kiQkCyyAIb+ zJRu0yOFWh+u6ckVPyuGmZGUiNx0E8r/QLN0AbK5ek/AqIX5XtUQp3UsTPxaw2LcoUtoLweV5 3jJo1VPgr+mMgix3YXTdutfKyBZunRoddjdO5QmHdvnMhtPbue58cKyF+uJ4XA6aNj7idyYb8 Ynev+NrsU3rJ79lzYP21dC0/DxXyc4xE7SvzSICDBHGCbuq7ihvb+Ia3Y2d7B1noeLNafhK+O dHUDSVCePXxfn0bOECatx7QzWgfU3O7DhGF96pZdmtUV1mBcU/oTbmjJnHkT5R+d3i6tszoE1 mcyTHeasJIBAui7KeAGs/BJKcbwE5wuvfKnF0IA00Ot6enPpjZ93ScKxnBVM+MnGU5PV1kLjJ eGhQRDFYCfCZmcNbv15fUJpzTPGnxx9sr4vxfLbhOHqmO1x6FI7BxV21TdjF7ZAaAJ+EiBPHa tJUDz9SeHX5JvgtruG3sSOKMCbBucN9/VCyf+NsrAthEeoB1ae/I5hFQgs7E/Vf+VDQwtsVgt 9rYIDZPp5SQ4coYGaKqnrtEi1NZSWEWZE2la+dfGcrXH6ImDqw8mpjKyRU91gIh7OKWzQu9IP dwSOEtzEIvVpg9zfvWNWuwNfcSDQ9gg7WaJ1Ssd/qO09ra15RN5bxFkvS3HMptD8u0rNX8w+X Z7HagbHKc5WsvCexQLPe1vmqa3DbUuQYx31SlKnpc= 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 18:05:03 -0000 On 08/16/2015 19:47, Kimmo Paasiala wrote: > 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. In general, you need 3 runs of "freebsd-update install", one for installing the kernel, one for installing the userland, and one for removing obsolete shared libraries (see install_files in freebsd-update). Of course, the third run is usually not needed during minor version upgrades, but it was needed between 10.1-RC2 and 10.1-RC3. Although you get a message about the necessary third run, you may forget about it anyhow. That was my speculation. Rethinking the problem, that is probably not it, since both libopie.so.7 and libopie.so.8 would be present in that case. Cheers, Jan Henrik