From owner-freebsd-stable@FreeBSD.ORG Sat Dec 7 06:18:20 2013 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 F341BEB3; Sat, 7 Dec 2013 06:18:19 +0000 (UTC) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 7A14E168E; Sat, 7 Dec 2013 06:18:19 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1VpBGY-00079i-Ak; Sat, 07 Dec 2013 10:21:26 +0400 Date: Sat, 7 Dec 2013 10:21:26 +0400 From: Slawa Olhovchenkov To: Baptiste Daroussin Subject: Re: pkg repo for 9.2-RELEASE Message-ID: <20131207062126.GB80282@zxy.spb.ru> References: <20131204192228.GA47404@zxy.spb.ru> <20131206164112.GS76976@ithaqua.etoilebsd.net> <20131206204444.GA99055@zxy.spb.ru> <20131206221509.GV76976@ithaqua.etoilebsd.net> <20131206222842.GA80282@zxy.spb.ru> <20131206223205.GZ76976@ithaqua.etoilebsd.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131206223205.GZ76976@ithaqua.etoilebsd.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Dec 2013 06:18:20 -0000 On Fri, Dec 06, 2013 at 11:32:05PM +0100, Baptiste Daroussin wrote: > On Sat, Dec 07, 2013 at 02:28:42AM +0400, Slawa Olhovchenkov wrote: > > On Fri, Dec 06, 2013 at 11:15:09PM +0100, Baptiste Daroussin wrote: > > > > > On Sat, Dec 07, 2013 at 12:44:44AM +0400, Slawa Olhovchenkov wrote: > > > > On Fri, Dec 06, 2013 at 05:41:12PM +0100, Baptiste Daroussin wrote: > > > > > > > > > On Wed, Dec 04, 2013 at 11:22:29PM +0400, Slawa Olhovchenkov wrote: > > > > > > Where I can find corectly builded pkgNG packages for 9.2-RELEASE? > > > > > > Packages on official site (pkg0.bme.freebsd.org, for ex.) builded on > > > > > > incorrect, outdated FreeBSD verion (may be 9.1-RELEASE): > > > > > > freeradius3 build with libssl verion 90818f and can't be run on > > > > > > 9.2-RELEASE: > > > > > > > > > > > > # radiusd -X > > > > > > libssl version mismatch. Built with: 90818f Linked: 90819f > > > > > > > > > > The abi is compatible that should run of radius should be patched to to accept > > > > > both version. > > > > > > > > > > The freeradius3 should be informed to allow this to run. > > > > > > > > As I see in source freeradius3 use strict version check and don't have > > > > compatible lists. > > > > > > > > What is trouble to use latest FreeBSD RELENG to build pkgNG > > > > packages? > > > > > > > > 9.0-p7 and 9.1-p2 have openssl 90819f (r249029). > > > > > > > > Also, virtualbox-ose-kmod have strict version dependens to kernel. > > > > > > We have always build the packages on the lowest version of a release branch > > > because we ensure binary compatibility, kmods does not have a strict version > > > > In real world we have incompatibility for freeradius and freeradius3, > > for virtualbox-kmod, for filesystem modules (fuse and some others?) > > > > 20121224: > > The VFS KBI was changed with the merge of several nullfs > > optimizations and fixes. All filesystem modules must be > > recompiled. > > > > 20120106: > > A new VOP_ADVISE() was added to support posix_fadvise(2). All > > filesystem modules must be recompiled. > > > > > depends on the kernel, they should be loadable on newest kernel of the same > > > branch. > > > > In real world kmods of virtualbox loaded, but don't worked (kernel > > crashed). > > That is a major problem which doesn't only concern packaging > > That should not happen in a stable branch, and should have been reported and > prevented :( That is defeating lot of our policies and inpacted more than just > package building. > > All our actual policies for packaging are based on KBI and ABI stability over > the lifetime of a branch It's not always posible. And I think best way is correctly support last -SECURITY instead of obsolete -RELEASE.