From owner-freebsd-questions@freebsd.org Sun Nov 17 15:31:16 2019 Return-Path: Delivered-To: freebsd-questions@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 DAAD91C2C83 for ; Sun, 17 Nov 2019 15:31:16 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from kicp.uchicago.edu (kicp.uchicago.edu [128.135.20.70]) by mx1.freebsd.org (Postfix) with ESMTP id 47GGJg3tzwz4SB9; Sun, 17 Nov 2019 15:31:15 +0000 (UTC) (envelope-from galtsev@kicp.uchicago.edu) Received: from [IPv6:2607:fb90:a22a:2891:f0a4:9aa7:a960:7c04] (unknown [172.58.139.75]) (Authenticated sender: galtsev) by kicp.uchicago.edu (Postfix) with ESMTPSA id 7E36F4E657; Sun, 17 Nov 2019 09:31:14 -0600 (CST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\)) Subject: Re: consequences with pkgs of freebsd-update upgrade? From: Valeri Galtsev In-Reply-To: <6b12048c-6ad5-0acc-ced5-92cf9f8b92d0@FreeBSD.org> Date: Sun, 17 Nov 2019 09:31:12 -0600 Cc: freebsd-questions@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <75B695E3-B9EE-49B9-82CC-1FF3C7B59E0F@kicp.uchicago.edu> References: <20191116173351.GA19947@bastion.zyxst.net> <1C961C3D-06ED-4D06-AEFB-E97F795C973C@kicp.uchicago.edu> <6b12048c-6ad5-0acc-ced5-92cf9f8b92d0@FreeBSD.org> To: Matthew Seaman X-Mailer: Apple Mail (2.3601.0.10) X-Rspamd-Queue-Id: 47GGJg3tzwz4SB9 X-Spamd-Bar: + Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="No valid SPF, No valid DKIM" header.from=uchicago.edu (policy=none); spf=none (mx1.freebsd.org: domain of galtsev@kicp.uchicago.edu has no SPF policy when checking 128.135.20.70) smtp.mailfrom=galtsev@kicp.uchicago.edu X-Spamd-Result: default: False [1.83 / 15.00]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; DMARC_POLICY_SOFTFAIL(0.10)[uchicago.edu : No valid SPF, No valid DKIM,none]; RECEIVED_SPAMHAUS_PBL(0.00)[75.139.58.172.khpj7ygk5idzvmvt5x4ziurxhy.zen.dq.spamhaus.net : 127.0.0.10]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MV_CASE(0.50)[]; MIME_GOOD(-0.10)[text/plain]; MIME_TRACE(0.00)[0:+]; NEURAL_HAM_MEDIUM(-0.37)[-0.373,0]; IP_SCORE(0.13)[ip: (0.37), ipnet: 128.135.0.0/16(0.18), asn: 160(0.15), country: US(-0.05)]; RCPT_COUNT_TWO(0.00)[2]; RCVD_IN_DNSWL_NONE(0.00)[70.20.135.128.list.dnswl.org : 127.0.10.0]; NEURAL_SPAM_LONG(0.48)[0.476,0]; R_SPF_NA(0.00)[]; RCVD_NO_TLS_LAST(0.10)[]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:160, ipnet:128.135.0.0/16, country:US]; MID_RHS_MATCH_FROM(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 17 Nov 2019 15:31:17 -0000 > On Nov 17, 2019, at 3:03 AM, Matthew Seaman = wrote: >=20 > On 16/11/2019 18:31, Valeri Galtsev wrote: >> yes to everything. Basically, you first need to upgrade poudriere >> machine to the latest base system using freebsd-update, and upgrade = all >> packages on it (poudriere being one of them). Then rebuild all = packages >> you maintain using poudriere. Then upgrade the other system, and >> re-install all packages on it. >>=20 >> Experts will chime in if I=E2=80=99m missing something. >=20 > Actually, for the most part, this isn't true. Your poudriere build = box > does not have to exactly match the installed version(s) of your client > machines. >=20 > The actual requirements on your poudriere machine are: >=20 > * Same major version as the clients you want to support > * A supported version of the OS > * Not newer than any of the clients. >=20 With all due respect, this is quite different from what I know about = poudriere. And the difference is in the fact that poidriere builds = everything in jails. Therefore, here is what I have (Note, that all my = machine run RELEASE): 1. host system is the highest version of the RELEASE 2. for poudriere buld the same major/minor versions RELEASE jails are = created, collections of packages for each minor/major version is built = in jail the base of which is exacly the same as minor/major version as = the system you build packages for. In other words, Matthew, you don=E2=80=99t need to have separate host = running FreeBSD 11.3-RELEASE, packages for FreeBSD 11.3-RELEASE can be = build on FreeBSD 12.1-RELEASE in jail which has base FreeBSD = 11.3-RELEASE That is the beauty of pouderiere, it is designed to have everything = built on one machine. So, here is what my poudriere box is today: host system: FreeBSD 12.1-RELEASE jails packages are built in have base system as the machines packages = will be installed on: Jail1: FreeBSD 12.1-RELEASE Jail2: FreeBSD 12.0-RELEASE Jail3: FreeBSD 11.3-RELEASE =E2=80=A6 The simple explanation why it is appropriate is: when built in jail = everything is as on the system of level the jail base is, so appropriate = libraries are linked etc. The necessity to run highest version on pourdiere host stems from the = fact that you can not run jail of higher version than that of host = system. I hope, everything is clear now. Valeri > Thus a 12.0 poudriere machine can be used to maintain packages on a = mix > of 12.0, 12.1 and 12-STABLE machines. However for the 11.x branch, > you'ld need to be running at lease 11.3-RELEASE in your poudriere > builder, due to recent changes in the versions supported by the ports. >=20 > If you follow these rules you will be able to build and successfully > serve pkgs of the vast majority of the available ports. There are a = few > exceptions though. These are certain loadable kernel modules, which > need to be compiled against the same kernel version as you are running > -- or at least a kernel with the same KBI version. >=20 > Cheers, >=20 > Matthew >=20 >=20 > Thus a 12.0 poudriere machine can be used to maintain packages on a = mix > of 12.0, 12.1 and 12-STABLE machines. However for the 11.x branch, > you'ld need to be running at lease 11.3-RELEASE in your poudriere > builder, due to recent changes in the versions supported by the ports. >=20 > If you follow these rules you will be able to build and successfully > serve pkgs of the vast majority of the available ports. There are a = few > exceptions though. These are certain loadable kernel modules, which > need to be compiled against the same kernel version as you are running > -- or at least a kernel with the same KBI version. >=20 > Cheers, >=20 > Matthew >=20 >=20 ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++