Date: Mon, 16 Jun 2014 09:22:59 -0400 From: Paul Mather <freebsd-lists@gromit.dlib.vt.edu> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: freebsd-stable@freebsd.org, Dave Duchscher <daved@nostrum.com> Subject: Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-14:03.pkg Message-ID: <38C93122-E8E6-45DB-80AA-E305C630F228@gromit.dlib.vt.edu> In-Reply-To: <20140616115928.GL4747@ivaldir.etoilebsd.net> References: <201405140000.s4E002sO029919@freefall.freebsd.org> <D4810186-8CB0-450B-8C32-6E180DB6E7A8@nostrum.com> <20140616115928.GL4747@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 16, 2014, at 7:59 AM, Baptiste Daroussin <bapt@FreeBSD.org> =
wrote:
> 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?)
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:
echo "FreeBSD: { enabled: no }" > =
/usr/local/etc/pkg/repos/FreeBSD.conf
as it instructs in the /etc/pkg/FreeBSD.conf repo file that is=20
installed.
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.
Cheers,
Paul.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38C93122-E8E6-45DB-80AA-E305C630F228>