From owner-freebsd-stable@FreeBSD.ORG Tue Jun 17 13:02:01 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 322D4977; Tue, 17 Jun 2014 13:02:01 +0000 (UTC) Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 062BF2D02; Tue, 17 Jun 2014 13:02:00 +0000 (UTC) Received: from [10.0.1.13] (r74-192-37-226.vctrcmta01.vctatx.tl.dh.suddenlink.net [74.192.37.226]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id s5HD1vpg002942 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 17 Jun 2014 08:01:59 -0500 (CDT) (envelope-from daved@nostrum.com) X-Authentication-Warning: raven.nostrum.com: Host r74-192-37-226.vctrcmta01.vctatx.tl.dh.suddenlink.net [74.192.37.226] claimed to be [10.0.1.13] Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.2\)) Subject: Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-14:03.pkg From: Dave Duchscher In-Reply-To: <38C93122-E8E6-45DB-80AA-E305C630F228@gromit.dlib.vt.edu> Date: Tue, 17 Jun 2014 08:01:57 -0500 Content-Transfer-Encoding: quoted-printable Message-Id: References: <201405140000.s4E002sO029919@freefall.freebsd.org> <20140616115928.GL4747@ivaldir.etoilebsd.net> <38C93122-E8E6-45DB-80AA-E305C630F228@gromit.dlib.vt.edu> To: Paul Mather X-Mailer: Apple Mail (2.1878.2) Cc: Baptiste Daroussin , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Jun 2014 13:02:01 -0000 On Jun 16, 2014, at 8:22 AM, Paul Mather = wrote: >=20 > On Jun 16, 2014, at 7:59 AM, Baptiste Daroussin = wrote: >=20 >> On Sun, Jun 15, 2014 at 07:12:21AM -0500, Dave Duchscher wrote: >>> I have had a few surprises with FreeBSD over the years and with the = new ports system has provided quite a few of them but this update takes = the cake. We have our own package repository with custom options. We = liked and adopted pkgng early. We also have a lot of automation. With = this update, all of a sudden, we have a new repository configured on our = system (/etc/FreeBSD.conf). Lets say, I was very surprised. It is true = that mistakes happen. Maybe its ours for not fully understand what was = being done. In any event, this definitely caused lots of issues for us = and has wasted a lot of my time. >>>=20 >>> Dave >>>=20 >>=20 >> I'm really sorry to hear that, how could we have improved our = communication to >> reduce the inpact on users like the one you had? (what would you have = expected?) >=20 >=20 > It would have been nice if the Errata Notice had contained information=20= > about disabling the newly-enabled FreeBSD repo. In my case, I was=20 > already aware of the issue, because I have some FreeBSD 10 systems. =20= > For my FreeBSD 8 and 9 systems, the workaround after installing the=20 > FreeBSD-EN-14:03.pkg Errata was simply a matter of doing this: >=20 > echo "FreeBSD: { enabled: no }" > = /usr/local/etc/pkg/repos/FreeBSD.conf >=20 > as it instructs in the /etc/pkg/FreeBSD.conf repo file that is=20 > installed. >=20 > I use my own pkg repo, built via Poudriere (thank you, Bapt!), which = is=20 > why I elected to disable the newly-installed FreeBSD repo. It's not=20= > clear to me how multiple repos interact under pkgng, or how you can=20 > assign priorities to repos or protect packages installed from one repo=20= > from being upgraded by packages from another. That's the main reason=20= > in my case why I normally disable the default FreeBSD repo and just = use=20 > my Poudriere-maintained one. >=20 > Cheers, >=20 > Paul. This is pretty much my feelings on this particular issue. I will add = that the notice should have been more direct and warn that this new repo = may conflict with private repos that may be installed. Communication is = hard and sometimes you just have to hit us busy people over the head. Dave