From nobody Sat Oct 21 23:45:54 2023 X-Original-To: freebsd-arm@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 4SCdPw4f8kz4xk2G for ; Sat, 21 Oct 2023 23:46:12 +0000 (UTC) (envelope-from marklmi@yahoo.com) Received: from sonic313-20.consmr.mail.gq1.yahoo.com (sonic313-20.consmr.mail.gq1.yahoo.com [98.137.65.83]) (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 4SCdPv37q5z3b4N for ; Sat, 21 Oct 2023 23:46:11 +0000 (UTC) (envelope-from marklmi@yahoo.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=yahoo.com header.s=s2048 header.b=AdXdgUAV; spf=pass (mx1.freebsd.org: domain of marklmi@yahoo.com designates 98.137.65.83 as permitted sender) smtp.mailfrom=marklmi@yahoo.com; dmarc=pass (policy=reject) header.from=yahoo.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1697931968; bh=3lW+k902mq4HLeUCqccC1BLrE82NqPYO4qmfBostn+I=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From:Subject:Reply-To; b=AdXdgUAVfa/ObDBMsQAhNti0kIY+N3MkgOOY5UFTmfnAyOaUQz4+leL89FOm7wepKH5NgeR6vuAE+x7hHYmXdaJM2LeqLdmXpgYriDxDnJmbvvEhkyBRvEB1jnJ9nzMWUawSkv8Dckfz7Eibaiv8WA2avRz70mkGPLLJYyMVypHxBoLU5AlDHTAhn7yXeq3B5i2qGb6xrQuxC7dx8JujwQD4xN6VNMhRJtSDkYp8pMMkeZR31HtPete8oueTDONizzci61qV+JIdoar1JTBImBEZh0176Wf5GQvdOLltshfbV3HfT0Mt+mie6Y4FgeK+aJ94Xq4k0By8SGrEQT8fAA== X-SONIC-DKIM-SIGN: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1697931968; bh=z6B9DXiimDX9J20rb41NXcTp4C/QgOoX83Dl/AfFsB4=; h=X-Sonic-MF:Subject:From:Date:To:From:Subject; b=Cm9ZF5G87kNFjT/9S3oDSne4q3TvGyNEpaxsukKywg0yN+EqxI4CDJ/knUDCVsgKgZ/EoqYxjAzblv1p0HJiPPCiZvm2L/RPYd1kfEg3hWn8tdDjtv12H0x+fYyZeYpNG6USXT56N7D/0WLTfujQawtb0mTr1yM4D8ObuvHwnOOkoZvvtT2gxOK4Qhl3Gq+hlFvpOMGYWvz8dZOTAcf/PyWT0gD5bAMq/gvsgYDCF5UUbe4URj18VzpYnNQlVw2pMGTWGTxoz63TskkTF2inPKIf01l5xcKEL9epq2TFWF3lPCWdVj4nLEpHqTmdscow9VmzugO7il7NrvjAxahrEA== X-YMail-OSG: qDKVF1oVM1nhfivf4Al9m_epM10jkma5XPDvtd.HZ_zJ8gRnFYK3pLVnJpSDRBv RazpxgUjW0O3Dy0vu7pPe32QOUIfGttDXNjkOk71MNNGosdCoECARKtL8.DgbVlqWHiEQqU8CrI1 nASQ0zd8xfLw6RcxAb53eh.BqT91jenXfGx3ckX2fYXTKAuTe9QWdxm19hKZ1Jm4FlUZ1guY8mtu HfKOVQhWoJ66eSnRbcgn_PFa3ej4wvhUgDeE4AinhYLcMBB9G7kQDtVtPcPAhoHYI56ZpHnxJxxe xJjSkEhg1tAGHUwmIO42q6ZIY78CmQDiUHQC_6Ymj9UkNby6WJDslkXlGM4jrPL7BmxsrVdDIuaG UXyfXoS5VVRi39fPWkyS8JL81_5h8uM71i8WLWCPu4infEt9Vv_I.lpZWtG2NeR2ROtj.B_J5iEZ lrX4oXt8hkJJwbijr9VrGdwG9Kfd6KwOHd.x.uzh8zECBr2QCVTE0eDqDiVmEROq6VBmfkZ561ee MmdnI9OMce8znDPBA514LIQQr8WnuwgsgYQv2QGsQdkj62aObG6Rh_ZdIRfVyBurvR1.4sBLoaMO svz_4vch11QNHnlJSEBINlk9avOvjHqyrDL90WjlRQrNaV0KRfP.DkltZqcBZR2RKE58j.pp9m4K gXdcWjiRBxC89VPRdTfgin51BITC_uoEff42aOiEvpPC7PlUZFOV51bSiU_oP8JJhV49TuVizIwE h.ancTp47_f05xPbr7KF5g2B3A7uE1YumndsKH8XqBILgLOVfQnxrAv.T6dfhbHmYvGRRyOmN5Tk s9blGL0IA1C70he8kUu7B7.KsR48Uy28MaJMN6GmFFot.YsgKkH3WsyPyR7Auqy1YcB3YYWPeZeF GA_UasiYFB08nE3q_gk90RfVXb9b_D2_BS1imxhj0XXh8ZaS6rfz0PLTz4IRNMAtPhWDqzKMD9Ar 8fhho6QXDOVoua1zkdNFIJK.seXDGQXpB2A.wF_yPvlCs2tx1Vt3KWw_AJLipqBDzJsazYeLdbm1 izWoU0m_R6UxxThuqGx8DlGHp2p5R3fjVOVJkhl0cWTfMZ6_1bNDdo.x1wyOajU1CRhhpIM8JyTM jffXVb4Jo1JapNJY2tMYyKCws8ZoFnsXsGQh.2TX0J.3buCfCjTPBOuHiN9uvjHG5InXCLIsFDc8 2gvqxu7eUfpUWCquv1Tn8MFQHJopSV5VnrRRIY5m2kColmP91yDRH7LiYjQ3F74WTs4Q1znu7WPT _Z9aJ5IBgqlCMJSyyfs1MGawxLXNygRaLxrz8a7hgipNUgnegTe9wweACz4nECoJdMZ_lec3DHtV uuXfztd7vbRj4B7LzWB6SrfC9P_PU40JheKCtwJ2UquDK.E4W0DxDYaaAtZWyCZrB2eAdnJ1AcVO 7m1GzZAm2MKIIevOvpM6z6Gza7b5zNfe0_xopC5cv7g.wPvDJ9Mxnp2_9aIi7ON1T3EAH9k739JG Y2W.Tz1AIoSdvDIWhzKpjee3fbbioL1DoGfc3YjIWYBilP4yuCCQVE0oZpdPKVa1xsCzNvwUs.nT gy9ID1e_8KI4rV8zzTuHppmui1X9FjV4FnMTXyiAM8j._djGU5Y7pXfmXxpI0hZxzVmGeeL0A7NK .eaYNNpIyq62ltjtYsYD2IpDcsR.C_OOocguPBFt4Mxv_CHbNpkjF0by2wh1b2l3Rn_EuHiK86E2 Z2FtNCshFeZHnplE6_Oz9LWPZk1fUJYW5j9eHa0No1jJqbc57yt6Ht_2v1LOFPm0pWTqpUnPAgq7 p_JUmz_hhKSKblN0JpK1t.8zkvguWwp8SUPyzNldpUJvmcAaBOhUWeIOGjwwAHykH6rqM9y3K8dK rTC6N8TXezlIfqlY8o9Qt6j5fErEJlX2CV2Qcq5xLBy2OL70hAg82rId8TnWj63fvek7gyWuKrb9 xkRbjimTsGPOFzHjwzuWZzdRXBRWLdaCPSQyzIonGizUI3W1nOhSurycKZCj19Fgb__wactcfJhp ycnVcN67gQ4568D0dMBUty4Vag3B9WO6LT.VlYws.kyKxNzMkEj8WMMGPL1NBozi62eiN_iIaxHn Dyr49RtAjcGrQoFZ9DVqw63DQszryPmCsdwCjZcs691Av29ujAQ9ZfI88CKLdpwPTM5GBtrb.TGv gClfT.NgJ7CQIVwXzE22Jb9YmgHQMOB1u8.NXq3RhT7vb9siMfyi3ar2gkdZe4YewubKNI0Ls7MJ xSnIf.V.rr3RG80aR9ncaCoLwcTEAPa2aIVtLqr5ysuU0dQQjObawL2MsmhaH49Io82L9iIPInlG IzA-- X-Sonic-MF: X-Sonic-ID: 6ec235c3-fe9d-421c-bc3b-9fdd2e3efbc6 Received: from sonic.gate.mail.ne1.yahoo.com by sonic313.consmr.mail.gq1.yahoo.com with HTTP; Sat, 21 Oct 2023 23:46:08 +0000 Received: by hermes--production-gq1-59f5fd4df5-487zq (Yahoo Inc. Hermes SMTP Server) with ESMTPA ID aba0d1a624ac655bee3d503c44307ff1; Sat, 21 Oct 2023 23:46:05 +0000 (UTC) Content-Type: text/plain; charset=us-ascii List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.100.2.1.4\)) Subject: Re: rust 1.72.0 in poudriere-devel keeps getting rebuilt From: Mark Millard In-Reply-To: Date: Sat, 21 Oct 2023 16:45:54 -0700 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <057159E4-7E05-49A3-8520-3E2815C4A6A0@yahoo.com> References: To: void X-Mailer: Apple Mail (2.3774.100.2.1.4) X-Spamd-Bar: --- X-Spamd-Result: default: False [-3.50 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.998]; DMARC_POLICY_ALLOW(-0.50)[yahoo.com,reject]; MV_CASE(0.50)[]; R_DKIM_ALLOW(-0.20)[yahoo.com:s=s2048]; R_SPF_ALLOW(-0.20)[+ptr:yahoo.com]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DWL_DNSWL_NONE(0.00)[yahoo.com:dkim]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; RCVD_IN_DNSWL_NONE(0.00)[98.137.65.83:from]; MID_RHS_MATCH_FROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[yahoo.com]; RWL_MAILSPIKE_POSSIBLE(0.00)[98.137.65.83:from]; DKIM_TRACE(0.00)[yahoo.com:+]; FREEMAIL_FROM(0.00)[yahoo.com]; TO_DN_SOME(0.00)[]; ASN(0.00)[asn:36647, ipnet:98.137.64.0/20, country:US]; RCPT_COUNT_TWO(0.00)[2]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_TO(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Rspamd-Queue-Id: 4SCdPv37q5z3b4N On Oct 20, 2023, at 11:06, void wrote: > Hello arm@ >=20 > What can I do to stop rust being rebuilt all the time in my = poudriere-devel on rpi4? >=20 > 1. the version on pkg.freebsd.org at present is 1.72.0 >=20 > 2. the Makefile in the ports tree also says 1.72.0 >=20 > 3. poudriere is not building it in its filelist of ports-to-build, but = as a dependency >=20 > 4. rust cannot build on a bigger faster machine with poudriere & qemu = for arm64.aarch64=20 > because rust will not build under qemu-user-static >=20 > 5. I've tried running a build with no make.conf for the poudriere to = use. It still > tries to build locally, instead of just downloading the binary like it = downloads other unchanged binaries. No options for rust have been = locally set, for the poudriere instance. >=20 > Is there a workaround that allows one to add the precompiled package = so poudriere will use it to compile packages that need it? poudriere(-devel) is explicit why it rebuilds rust in my context. For example (from a recent test): . . . [00:00:04] Deleting curl-8.3.0_1.pkg: new version: 8.4.0 . . . [00:00:05] Deleting rust-1.72.0.pkg: missing dependency: curl-8.3.0_1 . . . So the curl that rust-1.72.0.pkg had previously been built with no = longer has a matching curl *.pkg . So rust is rebuilt based on the new version of curl [via curl's new *.pkg version]. poudriere has no clue if or when or where its builds will be used for later installation activity. It can not use that kind of context to guide its actions as things are. Having deleted rust-1.72.0.pkg poudriere rebuilds rust based on the new curl dependency (version), even if rust would end up not being = reinstalled automatically due to a lack of a version number change. rust and/or curl would be ready to be installed as needed. (curl is just the dependency that happened to occur in my test. Any special properties of curl as a dependency are not the point here: it is just one example.) The ports structure and poudriere do not do detailed analysis of if the update to curl in this example would actually lead to a behaviorial change or incompatibility for the detailed way curl is used by rust. Similar points could be made for other dependencies that sometimes might lead to rebuilding rust (but not necessarily automatically installing = the rebuilt rust: lack of a rust version number change, for example). I'll note that there is a time between when the port curl goes from 8.3.0_1 to 8.4.0 and when a rust-1.72.0 package is available from the FreeBSD servers that is based on rust built with curl 8.4.0's package involved. During that period the only way to be consistent with the updated ports tree is to build rust (and curl) locally. Otherwise one would have to check out the port tree as it was at an earlier time to match the packages currently available via pkg. (But that tends to omit recent security fixes and such in parts of the ports tree.) (Again: curl is just an example of a dependency, one that happened to show up in my test. Any special properties of curl as a dependency are not the point here.) "... add the precompiled package so poudriere will use it to compile packages": So you want a rust to be used that does not track the actual ports tree being built: allow the rust used to be out of sync with the ports source tree for rust's dependencies, despite that the rust version number does not indicate that full ports-source context. I'll note that this specific wording is not explicitly asking that an updated rust not be built at all. The difference between what is installed/used vs. what is built is being mixed in an unclear manor for the specific wording. Looks like you actually have a 2 component request overall: A) use of a prebuilt rust and at the same time: B) lack of doing any build of rust in the bulk run (even if the build is not used: otherwise the time would not be avoided) If rust has a version update (judged strictly by version numbering changes?) that is not available as a prebuilt package yet, the intent for handling the ports-source vs. prebuilt mismatch is not clear to me. Some number of rust dependencies could update during such an interval, but the eventual pre-built rust could well be for an earlier combination until an even later rebuild becomes available as pre-built. (But what may have changed over that 2nd interval?) You might what to be more explicit about what is acceptable when (or other type of context). =3D=3D=3D Mark Millard marklmi at yahoo.com