Date: Wed, 17 Dec 2014 21:47:00 +0100 From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> To: olli hauer <ohauer@gmx.de> Cc: FreeBSD Security Advisories <security-advisories@freebsd.org>, freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:30.unbound Message-ID: <86k31qovgb.fsf@nine.des.no> In-Reply-To: <5491488E.4020405@gmx.de> (olli hauer's message of "Wed, 17 Dec 2014 10:10:38 %2B0100") References: <20141217083643.E0059421C@nine.des.no> <5491488E.4020405@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
olli hauer <ohauer@gmx.de> writes: > Is there an issue with freebsd-update or an special reason the update > wants to install lib32? Yes. The freebsd-update distribution for 10.1 was incorrectly built without lib32; as a result, freebsd-update deletes lib32 when upgrading from older releases (see https://bugs.freebsd.org/195302). The only way to fix that was to reintroduce lib32 in the next patch release. Unfortunately, freebsd-update is not able to tell that a newly created file belongs to a distribution which is not installed or disabled in freebsd-update.conf. We decided that this was the lesser of two evils. I will make an announcement later regarding this and the "rm /" issue. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86k31qovgb.fsf>