From owner-freebsd-ports@freebsd.org Tue Mar 8 14:49:54 2016 Return-Path: Delivered-To: freebsd-ports@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 2F04EAC798E for ; Tue, 8 Mar 2016 14:49:54 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 1BF64B94 for ; Tue, 8 Mar 2016 14:49:54 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: by mailman.ysv.freebsd.org (Postfix) id 1750FAC798D; Tue, 8 Mar 2016 14:49:54 +0000 (UTC) Delivered-To: ports@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 16E63AC798C for ; Tue, 8 Mar 2016 14:49:54 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (elsa.codelab.cz [94.124.105.4]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D216BB93 for ; Tue, 8 Mar 2016 14:49:53 +0000 (UTC) (envelope-from 000.fbsd@quip.cz) Received: from elsa.codelab.cz (localhost [127.0.0.1]) by elsa.codelab.cz (Postfix) with ESMTP id 91E252842F; Tue, 8 Mar 2016 15:49:50 +0100 (CET) Received: from illbsd.quip.test (ip-86-49-16-209.net.upcbroadband.cz [86.49.16.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by elsa.codelab.cz (Postfix) with ESMTPSA id CE71D2842B; Tue, 8 Mar 2016 15:49:48 +0100 (CET) Message-ID: <56DEE68B.5070007@quip.cz> Date: Tue, 08 Mar 2016 15:49:47 +0100 From: Miroslav Lachman <000.fbsd@quip.cz> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:35.0) Gecko/20100101 Firefox/35.0 SeaMonkey/2.32 MIME-Version: 1.0 To: Vick Khera , FreeBSD Ports List CC: jnlin@freebsd.cs.nctu.edu.tw Subject: Re: google authenticator / missing UPDATING entries References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 Mar 2016 14:49:54 -0000 Vick Khera wrote on 03/08/2016 15:08: > Today I upgraded pam_google_authenticator from 20140826_1 to > 1.01.20160208,1 and discovered that it no longer worked. Remote login just > closed connection. > > It turns out that the necessary shared PAM library moved > from /usr/local/lib/pam_google_authenticator.so > to /usr/local/lib/security/pam_google_authenticator.so > > There is no note in UPDATING file about this at all. This should be very > loudly noted in the package upgrade and in the UPDATING file that the pam > configurations need to be modified. It seems UPDATING is overlooked by maintainers. It is not the first time this year where pkg upgrade is causing breakage without prior notice of users through UPDATING. I have UPDATING in RSS, have my own scripted notifications (by diffing UPDATING file) and I use 'pkg updating' before each 'pkg upgrade'... still beaten by upgrades with not compatible changes. :( For example Postfix with missing VDA. (I already submitted PR 207684) Miroslav Lachman