From owner-freebsd-stable@freebsd.org Tue Sep 19 08:32:33 2017 Return-Path: Delivered-To: freebsd-stable@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 8D537E04B10 for ; Tue, 19 Sep 2017 08:32:33 +0000 (UTC) (envelope-from prvs=0435da476c=ari@ish.com.au) Received: from fish.ish.com.au (ip-2.ish.com.au [203.29.62.2]) (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 56F1E70E16 for ; Tue, 19 Sep 2017 08:32:32 +0000 (UTC) (envelope-from prvs=0435da476c=ari@ish.com.au) Received: from ip-170.ish.com.au ([203.29.62.170]:56448) by fish.ish.com.au with esmtpsa (TLSv1.2:AES128-SHA:128) (Exim 4.82_1-5b7a7c0-XX) (envelope-from ) id 1duDxC-00086A-1q; Tue, 19 Sep 2017 18:32:26 +1000 X-CTCH-RefID: str=0001.0A150206.59C0D61A.00BE:SCFSTAT42589845, ss=1, re=-4.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 Subject: Re: ABI changes within stable branch To: Kurt Jaeger Cc: freebsd-stable References: <1b07bf49-508a-c6b4-e805-df7d43230f81@ish.com.au> <20170919081532.GB2170@home.opsec.eu> From: Aristedes Maniatis Message-ID: <21c1d954-8bdf-0d16-f1ca-176cd6df7a60@ish.com.au> Date: Tue, 19 Sep 2017 18:32:26 +1000 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:56.0) Gecko/20100101 Thunderbird/56.0 MIME-Version: 1.0 In-Reply-To: <20170919081532.GB2170@home.opsec.eu> Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 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, 19 Sep 2017 08:32:33 -0000 On 19/9/17 6:15PM, Kurt Jaeger wrote: > Hi! > >> Now that we are on a faster upgrade policy for minor branches, it is expected that we'll upgrade from 11.0 to 11.1 to 11.2 much faster than in the old days. I can cope with that, but it appears that functional changes are also being made within the stable branch as seen here: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=221672 >> >> A new fdatasync() method is available in 11.1 but not in 11.0 which means that I now need to maintain separate ports trees for each minor update. I've never done this before, assuming (correctly for me until now) that all ports build on the latest minor release within the stable branch would work on older releases until I was ready to upgrade them. > > I think it was the other way around: All ports build on the .0 of > a RELEASE work on all later .x of that RELEASE. Which makes it a bit > difficult, if a .0 is no longer supported/patched by the secteam. > > A pointer to the official policy would be nice 8-} Then we have a problem since https://pkg.freebsd.org/freebsd:11:x86:64/latest/All/ has been built on 11.1, not on 11.0 (I just tested it with csync2 which I know fails). Packages there may fail to run on 11.0, but there is no clear indication, just random failures at runtime. Maybe we'd need specific 11.0, 11.1, 11.2 releases instead of quarterly releases? Ari -- --------------------------> Aristedes Maniatis CEO, ish https://www.ish.com.au GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A