From owner-freebsd-pkgbase@freebsd.org Mon Apr 6 13:01:53 2020 Return-Path: Delivered-To: freebsd-pkgbase@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DD23E2AFA1B for ; Mon, 6 Apr 2020 13:01:53 +0000 (UTC) (envelope-from slw@zxy.spb.ru) 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 48wrKD5bzHz41gT for ; Mon, 6 Apr 2020 13:01:52 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1jLRNo-0008ZX-NX; Mon, 06 Apr 2020 16:01:44 +0300 Date: Mon, 6 Apr 2020 16:01:44 +0300 From: Slawa Olhovchenkov To: Guido Falsi Cc: Grzegorz Junka , freebsd-pkgbase@freebsd.org Subject: Re: FreeBSD-base and poudriere Message-ID: <20200406130144.GG8012@zxy.spb.ru> References: <8c4f0ffe-6961-f119-0034-0becf860b616@gjunka.com> <649a0a62-1ae4-6ec8-308a-4dadc234126a@gjunka.com> <98f5a68c-90d1-1f9f-4199-aed87d6aabc3@madpilot.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <98f5a68c-90d1-1f9f-4199-aed87d6aabc3@madpilot.net> User-Agent: Mutt/1.5.24 (2015-08-30) 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 X-Rspamd-Queue-Id: 48wrKD5bzHz41gT X-Spamd-Bar: / Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of slw@zxy.spb.ru has no SPF policy when checking 195.70.199.98) smtp.mailfrom=slw@zxy.spb.ru X-Spamd-Result: default: False [0.25 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.60)[-0.602,0]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_GOOD(-0.10)[text/plain]; RCVD_TLS_LAST(0.00)[]; DMARC_NA(0.00)[zxy.spb.ru]; AUTH_NA(1.00)[]; NEURAL_HAM_LONG(-0.12)[-0.122,0]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_SPF_NA(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:5495, ipnet:195.70.192.0/19, country:RU]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(0.08)[asn: 5495(0.38), country: RU(0.01)]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-pkgbase@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Packaging the FreeBSD base system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Apr 2020 13:01:53 -0000 On Mon, Apr 06, 2020 at 12:59:13PM +0200, Guido Falsi via freebsd-pkgbase wrote: > On 06/04/20 11:56, Grzegorz Junka wrote: > > > > On 06/04/2020 09:42, Guido Falsi wrote: > >> On 06/04/20 11:24, Grzegorz Junka wrote: > >>> Is it possible to create a poudriere jail using FreeBSD-base packages? > >>> > >>> I am thinking about a scenario where I build kernel/world and base > >>> packages on the host, then create a poudriere jail to build packages on > >>> the exact same kernel/world that was build on the host. > >> I'm doing a similar thing on head. What I do is run normal svn up; make > >> buildworld; make buildkernel; make packages on the poudriere machine. I > >> the upgrade that machine with the new base packages. > >> > >> After that I perform: > >> > >> poudriere jail -j ${j} -u -t 359154 > >> > >> where 359154 is the subversion revision I have just compiled in /usr/src. > >> > >> So I get packages for that exact head revision. > >> > >> Hope this answers your question. > >> > >> BTW I have found no way to create a jail with a fixed svn revision from > >> the get go. When I need to do that, I resort to temporarily modifying > >> poudriere code at jail.sh:563, adding -r option. I then revert the > >> change. > >> > > > > Thanks, that's interesting. So, poudriere will build the jail from > > sources from that specific revision? > > Yes, since it will "svn up -r " it's source tree for that jail. > > It will also invalidate and remove all packages if __FreeBSD_version has > changed. > > > > > But I think it still won't solve the problem where the base packages > > have been build with modified kernel configuration. Can you supply a > > custom kernel configuration in your method? > > No I can't, but really a modified kernel configuration should not impact > on ports, do you have a specific scenario? > > At most ports interact with kernel sources, whatever the configuration. NOINET6 don't change __FreeBSD_version but affect all inet-related modules, for example.