From owner-freebsd-pkgbase@freebsd.org Tue Jun 14 07:37:51 2016 Return-Path: Delivered-To: freebsd-pkgbase@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 6CB25AF26C0 for ; Tue, 14 Jun 2016 07:37:51 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 4DC192735 for ; Tue, 14 Jun 2016 07:37:51 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 49083AF26BD; Tue, 14 Jun 2016 07:37:51 +0000 (UTC) Delivered-To: pkgbase@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 48A30AF26BA for ; Tue, 14 Jun 2016 07:37:51 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: from mail-wm0-x232.google.com (mail-wm0-x232.google.com [IPv6:2a00:1450:400c:c09::232]) (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 D5A582734; Tue, 14 Jun 2016 07:37:50 +0000 (UTC) (envelope-from woodsb02@gmail.com) Received: by mail-wm0-x232.google.com with SMTP id n184so108405033wmn.1; Tue, 14 Jun 2016 00:37:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+23Bc5YKDMR3SV6r10b394IyMDRGevrWbOlGbohdchk=; b=cjPlhLvxh+KmHa5PyuTL5jucusPMnWr+vWxO9/VzjYWhEeXVGnyx70LzKumR8UYgk+ jxtnIcMef0O5lr5X7qXBUBP6wjpb+fMYWYKjjb4j1a8UyjYvlDxlsvP3GiwnIUJfTtYR fueh8uBKH/9JQ5UZyRXP4OrUeuq5riKflnyoX/xc5xEQ2p/ygNCNRvXIcA87q/2NEj2j 9JG2Ul+UztCAEiUgiwjiy8vCGEKUNu1D5qpxT7VGc1Pzx6/0/mFQ+znP5mfJDj5Mw6ty ZbY2mF/Ax5AUBUPfYU96GaQVqn0GjAgjAj+Th61dRuwl5y28vsJsJL5bqsmZekCevO3A Jc9w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+23Bc5YKDMR3SV6r10b394IyMDRGevrWbOlGbohdchk=; b=jB5YmwXIrg6UcDtVzkYnnW+XuvR5FXqBkXlfEKujrC2OktM1bYufoVgveHjB55HcuF TN/QMTt4jYaUCqp6VBazKL/Bs8OJCG5KKcJJVn2cstxAsp/0te2Xs0/E4IZl/WiyWegU B7muHysK+PSV/N/3rdny2HrbMlLIi5anAI2x5ic+qxZCIHNXy8vMPPDlKP2qiKvcObjC TMhFfro7360iHKbxvKxFw5WAjgF1JHGjlWdbsOTUR98REfmsl4SLM2fOfp0X42UjXe8M eMRy/3+PdItfHuQ+RwJNuSuUjQXtgWgo9TFjTEiyrrL+PJB0a/0TilGvs5Fqq7z8g/kI qZJQ== X-Gm-Message-State: ALyK8tJiSM9c1O7MsgFRsjyYl4tgL3BNBQ0XjV4OiFP02oG7ERRmW1PWOABm+1+zhtZH/LtJ2F3MqheqKTog+A== X-Received: by 10.194.67.101 with SMTP id m5mr5109224wjt.129.1465889869357; Tue, 14 Jun 2016 00:37:49 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.222.228 with HTTP; Tue, 14 Jun 2016 00:37:48 -0700 (PDT) In-Reply-To: References: From: Ben Woods Date: Tue, 14 Jun 2016 09:37:48 +0200 Message-ID: Subject: Re: libpam.so lost in update to 11.0-ALPHA3 To: =?UTF-8?Q?Ren=C3=A9_Ladan?= , "Michael W. Lucas" Cc: pkgbase@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jun 2016 07:37:51 -0000 On 14 June 2016 at 09:11, Ren=C3=A9 Ladan wrote: > Hi, > > I updated my pkgbase installation (11.0-amd64 from a few weeks ago) to > 11.0-ALPHA3. Building and installing went fine but it turns out that > libpam.so* is lost in the update (both the symlink and the actual so, > currently so.6) : > > # pkg upgrade > # pkg autoremove > < version lower) > << yes, I forgot to run mergemaster>> > # reboot > < > Is this a known bug? > > Regards, > Ren=C3=A9 > Michael Lucas mentioned on twitter a few days ago that pam was broken recently in FreeBSD current. Michael: was this a problem with libpam.so going missing? Were you using pkgbase, or is this an issue with the normal build/install system also? Regards, Ben -- From: Benjamin Woods woodsb02@gmail.com