From nobody Thu Aug 31 05:58:22 2023 X-Original-To: freebsd-ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4Rbr7c23J3z4rmNb for ; Thu, 31 Aug 2023 05:58:36 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic315-8.consmr.mail.gq1.yahoo.com (sonic315-8.consmr.mail.gq1.yahoo.com [98.137.65.32]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Rbr7b65Zsz4JlY for ; Thu, 31 Aug 2023 05:58:35 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1693461513; bh=gNmVys39Zu9/4z1N3rLt1beKlBib1bZOFKBtaIwUu/I=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=nrIcXhLsbjlAFZLEDhxnUW7wG5XS69pH/vM9j7vXFrJGO08Agn2yi3dF5Yr33AL3UzAYiFRZjTK3TNQuqJ9rIAU4OEjoo8adwBUy9gCQ2R0dcud4TJT+EDQQRBDGhv/Yx/NR6DHedy0BSoBVZl/mi+sM5DJdKsmaUjreqa+v5rHxPo2+oLkpLI8uOEN3uKUwUujqFKbTgwnTSe/fyQfNSBr1PdktjfaFiFdoe1JQOJxi4QKhQrJK/sV3JVCnzmRfXG4rA6aRrmaS/bb1Dsu3pI7HNqUWPzRnruxYr/Z6RMqYmgdRlZaf7nmRCuap/nx8kMiuJg0zfYgUbY6mgSzgXA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1693461513; bh=Vcy/ry3uQjkoE0FGMX3hVUjNI0Ml3A77M6cxSPRcyw0=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=XLFFBHr8TgVFLNz81KkqWajUWTtqUd1/7nS9ekuVL9Eyi/ncLKfoFvRbCGXyoL70y4c5JCEPTrynFm7hHFCCr/FJ6Q58tTW4phporfYf9d/58S1iFjuIw/WHqTTSv9j+7sUbjWfF2uDOStem0QmxYtmZjqSUMDlzE3mp7zcN2Gqa0yep/9q3IvBOuCy8yuXg/1/U55VJDqs6iGTVLVS0csKaOc0fm69G4EsN24pmv92zL7zyExEijbh3B3t5VV1ErSxBXhSaXmhS/FpfQNdFDPaWqDKn8q683it2cOa6osM9QuhBVRyOvmgQrs/QlMnK/SHq3/SjD5JCUod5R1UWyQ== X-YMail-OSG: .N4rGVMVM1kqkatfUa9BBPQEL9dfJMgff2khjIlgYVVwG9heN9vh8AEwlzJRpj3 p0wseOeiizl9YIfc77rqW4magVaJoVVvrZKHl446rPYdZBYTUP_kpaOsWDz.3UgyKHSz0bYZp6Mb cROZqaBPm6bd4aRnCWdWVAQOMqzQPDQCOEtbQrGpbnRrqrCcOoqVr1QQeWiAAGw1ENJJzI9daSoG A1s.nrsxw.qcT3r4Jgghxqxn11T4_xe6_vTdMf6bFRbs0qht2cLbA8zwy1ACP1MmpLF0qSVMc7.G OHunrcyz68b2eQMzMnQWSZYLIyky_WJiMAKaZDex6VhQcOsoFWLgwKzF0mvkeJ0WovejXJ4gfmDW A_6z_3yLbB1tq5hU8UgC3McHgeUuvYuebpl2n3R33Ltk4rCmuLgZdHhe79I2dMcMVC6TGyf0wEks wo7ku98D2sIBUPWT_bGCHcyiUJddYtSGeMkTdirEvoFYL72bgXhyNWkYVcP6oY5LNcqrrQQ9ZK5a 6kvBKVKLBcKN1ZQ0z7QMbY3zpLIMKtv63uYh2q9UWTxYvLmYI0US5wv9lAwEiwW1h9JB0I_fJNaU TZRroCLnHqmxtNWI7S.r2BfgHSspeIQivBIIPKKmjRdAbz3IJuBg3jVt0FJrbNd9Jk9zNUM1GSDo f4OwpsD8iuKd2IYtE0LPP1DoP6GCkYsCSWJDhjcNeuiKJkkp0tWZPeyFvbCtR4J3Rg_QhrIl11Dz 0XLLVrWfQShci6YF1oVP57k3YBf9i.vgPOpYOIpsZRAPbon0caGJx5hXFgpnh2tO5StzdEy2HyVV ksVc9NBLtlvuIFO8.jy9lztQNfr8XFoZ3AeqzEVHd0Q54bLbTlPgBuBExXmvgyfyZBX4VjbvV71a TuiloaSuMgcq1DTtOpZAmTOEvMy2yl2Ces4f1qnqRlMe6yLcFYbkgc4Wy0_c4nvmuPsFiVm.Fp1b ZW1bW220LwZjSoR.D6tWugLcg56MjJ2W4R_Z20CFlS2cV0FZpdyzo9K.c843j_xF7DWOBRZ6YJPa 15PZvMsA8kl.M0MtpwyXcvGANWSGJsizP1FV60FBMRgA1vRdU0pQvOkMMZ284qV5apABQ_OPf0mw kp7odinE8UbjzvGI16T3.QwVbSwkQY.GVhkowhW09BnsL9HNcxV8KOn4YN0.NfxFgPCfsbajkNjY z45Y3OFb4iJZHv0oS.DNPeVLIbmVP.phu7xOmQasjictatovzJONuZlGnTHfOPw2i9mDd1t0Phll SkthEpPw8MoaSGNdQun33n5v2m0eZSlpDRjee3dW40NSswplSs.ux9gzjZchfm4zjT4CuXLJFjO7 uAIaDsNkSso159UU_t_TYMcpjzzCUrLrd6fzEp9SG7o0YUhlBRNobA2ZXuo.h9wSRNOdyq.1va1y Vdh7D5FrkKUNI3sd4bhP9wWEWT94LzJRzRbmpkRMYYz8qiHwE0QERvbVM5UhgRxnMDfsk7LFtfSA RR_LiCywwqjXMJchMGhYh9c5TjhMJGB_RWBv_QuqI0yaB2TUaYKpjJ1b9rICmnz2Lhc.FvT34Lqt kdwzySDSlDxaWY1dNj9th_PV2EACjXyv19kx5Y43uSxLXJmoxaC5lwkOK_jo2OOES9EzpI9fnTMw 5oOO.Q1yGTBAXR9sxlIgOkHKEYutXAgHfm9sKJdnH7bzjUxK4dRsyTcpP32aALzuB1GqkTOwchSb yN9BzuY7JNW6XUVxlm2ju8YQIHAZysMtNr7cscY7OI8ih_X7UhTE3_NzsJnhwBY8QAHzPJOpdbEv nQmDFXHuhPPLRIOPFTXVxO7s_Jci5218QgFdCkcGFvfkwLboOZ..ehuUoeTFdpqnSe1eCPTouriU 16v6BUZojsJxHxOE32uRyDfgV5UJsoI2LPw29Ol1tj19xLp.S8jObVeDVV3AMgorBD2f1dVL3SCh lXe0om5ph0olzzfkw1F0MpGsTRi48xJ6A5nE.Qol6bcpAjomul9dy_ElInD6Ftqkyckp.Wo4sPQf 6M0J9vbRRVyz5NzI4C6pLZPFQJp_4lZM0C4FWYUN2M5Et8cb4PZN_XLLnZObEwUjVSsw7yog3upX V3.BZRQwtbIK5zf6azvE6JySqa1BxmFlANPDZr5tS_fsGX4MYoxDFqDKUAHKaPt2guK7W4VVD.go nS65L016v964RfGqk.ryF.ZINBC59fHd965vvYKOdkeKRESOdEbTYlI3WYReH6GrQnxZMNaQZ4Dz P8ZiS2_r.EMy3kx8yiw1QXe4abl8U1qD5uA9TfjpTqhTMuny9Rg4N.AADz5P.sx_UGioWPxE4EUA z2KY- X-Sonic-MF: X-Sonic-ID: 524b92aa-d759-4049-a2f8-f2037c9bacb1 Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Thu, 31 Aug 2023 05:58:33 +0000 Received: by hermes--production-gq1-6b7c87dcf5-rj56s (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID a663985a0bc61c54e1de599e6c341ad7; Thu, 31 Aug 2023 05:58:32 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\)) Subject: Re: Bmake bad variable name From: Mark Millard In-Reply-To: Date: Wed, 30 Aug 2023 22:58:22 -0700 Cc: FreeBSD Mailing List Content-Transfer-Encoding: quoted-printable Message-Id: References: <9B530FC9-ED6B-4B75-A731-D8F7D7586A51.ref@yahoo.com> <9B530FC9-ED6B-4B75-A731-D8F7D7586A51@yahoo.com> <040CECBC-8A04-4049-91A7-0C1522000F5A@yahoo.com> <94FBA6B3-EA84-4B96-A87A-0A04C3E6EFE0@yahoo.com> To: bob prohaska X-Mailer: Apple Mail (2.3731.700.6) X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US] X-Rspamd-Queue-Id: 4Rbr7b65Zsz4JlY On Aug 30, 2023, at 21:16, bob prohaska wrote: > On Wed, Aug 30, 2023 at 06:08:06PM -0700, Mark Millard wrote: >>=20 >> http://www.zefox.net/~fbsd/poudriere_on_rpi4 looks unchanged >> just now, not just for this but for any changes. May be some >> other copy was changed or the old content is cached someplace? >>=20 > The file was updated =20 > -rw-r--r-- 1 fbsd fbsd 4076 Aug 30 17:34 poudriere_on_rpi4 > Possibly I hit send before saving the changes. If you don't see > the changes after reloading the page please tell me. I had to force a reload but that got the updated text. I probably forgot to try that before. I've not yet looked at the new text. The below is only about the text of the specific message. >>=20 >> But that buildworld buildkernel activity and rebooting to >> the new installed system and updating >> /usr/local/poudriere/poudriere-system should be done before >> even the "poudriere jail -c". The quoted material may be >> just out of order? >=20 > My question was where does the output of=20 > poudriere jail -c ... get written? I thought > it might be a dot file in /usr/ports or=20 > /usr/local/poudriere, but nothing is visible. Look under your: /usr/local/etc/poudriere.d/jails/main/ There should be the files suggested by: # ls -Tlod * -rw-r--r-- 1 root wheel uarch 14 Jun 27 17:48:11 2021 arch -rw-r--r-- 1 root wheel uarch 5 Jun 27 17:48:11 2021 method -rw-r--r-- 1 root wheel uarch 33 Jun 27 17:48:11 2021 mnt -rw-r--r-- 1 root wheel uarch 2 Jun 27 17:48:11 2021 pkgbase -rw-r--r-- 1 root wheel uarch 14 Jun 27 17:48:11 2021 srcpath -rw-r--r-- 1 root wheel uarch 11 Jun 27 17:48:11 2021 timestamp -rw-r--r-- 1 root wheel uarch 13 Aug 25 00:21:30 2023 version version contains the likes of: 15-CURRENT that is based on your jail creation. The other files are mostly similar records of the creation information, other than timestamp. This is all a simple delete or create deals with at deletion/creation time. (I'll not here get into if other contexts also update the version file.) The data in these files is used during various poudriere commands. /usr/local/poudriere/data/packages/main-default/.latest/ should have the files suggested by the likes of: drwxr-xr-x 4 root wheel uarch 12 Aug 27 14:26:57 2023 . drwxr-xr-x 3 root wheel uarch 14 Aug 27 14:26:57 2023 .. -rw-r--r-- 1 root wheel uarch 21 Aug 27 14:25:04 2023 .buildname -rw-r--r-- 1 root wheel uarch 13 Aug 27 14:25:04 2023 .jailversion drwxr-xr-x 2 root wheel uarch 533 Aug 27 14:26:31 2023 All drwxr-xr-x 2 root wheel uarch 3 Aug 26 11:00:00 2023 Latest lrwxr-xr-x 1 root wheel uarch 57 Aug 27 14:25:02 2023 logs -> = ../../../logs/bulk/main-default/2023-08-27_14h24m55s -rw-r--r-- 1 root wheel uarch 163 Aug 27 14:26:57 2023 meta.conf -rw-r--r-- 1 root wheel uarch 236 Aug 27 14:26:57 2023 meta.pkg -rw-r--r-- 1 root wheel uarch 236 Aug 27 14:26:57 2023 meta.txz -rw-r--r-- 1 root wheel uarch 142016 Aug 27 14:26:57 2023 = packagesite.pkg -rw-r--r-- 1 root wheel uarch 142016 Aug 27 14:26:57 2023 = packagesite.txz .jailversion is another place listing the likes of: 15-CURRENT But here it is about what it found in the jail as of the most recent bulk run. The /usr/local/etc/poudriere.d/jails/main/version and /usr/local/poudriere/data/packages/main-default/.latest/.jailversion are used to detect and handle changes, which can automatically force full rebuilds, for example for 14.0-CURRENT -> 14.0-ALPHA1 is a change, as would 13.2-RELEASE-p2 -> 13.2-_RELELASE-p3 be a change. During a poudriere bulk run there is a temporary directly in the list as well: .building/ . If the build fails to complete normally poudriere can leave what was fully built under .building/ for use in the next bulk run for the jail but --without having committed those materials. This can avoid some rebuilding activity. As for the /usr/ports/ binding, there is: /usr/local/etc/poudriere.d/ports/default/ There should be the files suggested by: # ls -Tloa total 3 drwxr-xr-x 2 root wheel uarch 6 Apr 18 02:05:47 2021 . drwxr-xr-x 3 root wheel uarch 3 Apr 18 02:05:47 2021 .. -rw-r--r-- 1 root wheel uarch 2 Apr 18 02:05:47 2021 created_fs -rw-r--r-- 1 root wheel uarch 5 Apr 18 02:05:47 2021 method -rw-r--r-- 1 root wheel uarch 11 Apr 18 02:05:47 2021 mnt -rw-r--r-- 1 root wheel uarch 11 Apr 18 02:05:47 2021 timestamp The data in these files is used during various poudriere commands. > The sequence was=20 I presume the sequence is only covering when there is a system version-text change involved, not the simpler case when ports are updated for the same system version-text as for the prior build. So, for example, now that you are at 15.0-CURRENT you will be rebuilding many times over likely 2 or more years before this procedure will be needed again for main, say, for 15.0-ALPHA1 . ( ??.?-RELEASE-p? change more often. When the .? part changes, it also changes for ??.?-STABLE . So these would get this style of handling port -> package updates more often than main if one was building such for RELEASE and/or STABLE instead [or as well as]. ) > 1. update, build and install world and kernel This involves /usr/src and doing a cd /usr/src . Reboot(s) here as well? > 2. create /usr/local/poudriere Was this . . . A) installation of ports-mgmt/poudriere-devel ? B) a poudriere command of some kind? (if yes, what kind?) C) A mkdir -p ? Once: /usr/local/poudriere/ /usr/local/poudriere/data/ /usr/local/poudriere/jails/ /usr/local/poudriere/ports/ exist in the normal way, they should not have to be recreated, presuming they are not explicitly deleted some way. Some poudriere commands do adjust some of the content under: /usr/local/etc/poudriere.d/ and: /usr/local/poudriere/ I'll note that use of /usr/local/poudriere/poudriere-system/ is instead of poudriere dealing with maintaining materials somewhere under /usr/local/poudriere/jails/ . Similarly, use of /usr/ports/ is instead of poudriere dealing with maintaining materials somewhere under /usr/local/poudriere/ports/ . (I would not manually put anything under /usr/local/poudriere/jails/ or /usr/local/poudriere/ports/ .) > 3. run in /usr/src the make commands to populate=20 > /usr/local/poudriere/poudriere-system > 4. run poudriere ports command (this is where I expected some write = activity See under: /usr/local/etc/poudriere.d/ports/default/ ("default/" presumes use of some defaults.) > 5. run poudriere jail command See under: /usr/local/etc/poudriere.d/jails/main/ ("main/" presumes use of some defaults.) This command should list the new system's version text as an argument, not the old one. This points out something I missed on reporting before . . . Before (showing ??. instead of a specific number, for example): # poudriere jail -c -j main -m null -M = /usr/local/poudriere/poudriere-system -S /usr/src -v ??.0-???? the old jail should probably be deleted. So the sequencing would be the pair of commands: # poudriere jail -d -j main # poudriere jail -c -j main -m null -M = /usr/local/poudriere/poudriere-system -S /usr/src -v ??.0-???? This is true any time the ??.0-???? text changes --but only when it changes is the sequence needed. > 6. use poudriere >=20 > In the event of step 1 re-run step 3 So (2) may be one-time-only and my questions/notes above for (2) may be partially/wholly covered by that? > In the event of major version change delete the jail=20 > and re-run step 5 with the new version number I expect this is just about indicating what the the one command line argument is like during step 5 for the new system version, not a 2nd run of step 5 for the new system version. Only one instance of step 5 is needed when the ??.?-???? text changes. > Does that make more sense? Yes. =3D=3D=3D Mark Millard marklmi at yahoo.com