From owner-freebsd-security@FreeBSD.ORG  Thu Mar  5 12:30:48 2015
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 2810E304;
 Thu,  5 Mar 2015 12:30:48 +0000 (UTC)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (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 D1BEFE02;
 Thu,  5 Mar 2015 12:30:47 +0000 (UTC)
Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1YTUvI-000O8n-Qp; Thu, 05 Mar 2015 15:30:40 +0300
Date: Thu, 5 Mar 2015 15:30:40 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Dag-Erling =?koi8-r?Q?Smorgrav?= <des@des.no>
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-15:05.bind
Message-ID: <20150305123040.GB90978@zxy.spb.ru>
References: <201502250629.t1P6TSid007902@freefall.freebsd.org>
 <CAHcXP+cSUNVtkZWKQJb_ux5v=BLYnBmUhFO44AyishssMQWdBw@mail.gmail.com>
 <54ED7C7C.3070202@delphij.net> <20150225124710.GA70915@zxy.spb.ru>
 <868ufea2dk.fsf@nine.des.no> <20150303133119.GL48476@zxy.spb.ru>
 <86wq2v7j9c.fsf@nine.des.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <86wq2v7j9c.fsf@nine.des.no>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
Cc: freebsd-security <freebsd-security@freebsd.org>,
 Xin Li <delphij@delphij.net>, Bartek Rutkowski <robak@freebsd.org>,
 so@freebsd.org
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Mar 2015 12:30:48 -0000

On Thu, Mar 05, 2015 at 12:53:35PM +0100, Dag-Erling Smorgrav wrote:

> Slawa Olhovchenkov <slw@zxy.spb.ru> writes:
> > I see same message for may setup (track -STABLE) for base component.
> 
> You can't run freebsd-update on a system that tracks -STABLE (i.e. is
> built from source).

No, I don't run freebsd-update on a system that tracks -STABLE.
I run freebsd-update FOR track -STABLE (i have private
freebsd-update-server and build update to -STABLE for freebsd-update).