From nobody Sun Nov 19 16:04:39 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 4SYFp42cPhz50ykn for ; Sun, 19 Nov 2023 16:04:44 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 4SYFp33KdQz3fxk for ; Sun, 19 Nov 2023 16:04:43 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm1 header.b=LkPMR7jA; dkim=pass header.d=messagingengine.com header.s=fm1 header.b=hi1kuqjt; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.29 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 6162A5C01D6 for ; Sun, 19 Nov 2023 11:04:42 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 19 Nov 2023 11:04:42 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm1; t=1700409882; x=1700496282; bh=ye ZrP4arUqW3y45RME0Ak7yt+w8YB5a3oLCfN7BjYsg=; b=LkPMR7jA21hZsTE3Xy dHeAXdRco3aHsSymSgqNh/YRbBJIpiask0twHXDajuHfX6JyysaWvGO097cHoDxy RYZgWtY25f+enYrNm0rIJ0/xcYnXgtrLPPQC1GneIEjuRDGw3Sr5QBghJXdMP0C/ C93YO0fkKFslHzdDfTyqBML4JuXUSLgyZl+PNOqkVAwCQl5fCaYHTGvDU866DH1a dl5fJVZch+WaBV3V0r0+snkgZb7KKHEWv8DP1vDwnvpVF/fRNHVjyPq9FFFsXMHO X1H1r6N+fwfTqx0BxOVOKM5N9gpB8DeMKm6BjpQLryPNyI275MGbDPY/yJi49tN3 aVBA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; t=1700409882; x=1700496282; bh=yeZrP4arUqW3y 45RME0Ak7yt+w8YB5a3oLCfN7BjYsg=; b=hi1kuqjtfHkB2ctOMmeLQy0t+oYL/ nw1DECwckDCdc1edjTUlVvhlIQu0GKyL4HO9YRcMNSpaIgtf7qJhecSkuJGqT/yx EhaAn1kaywxjzXd/Dyp5IJyvtT/hLZ1evO8QVcVL3Nmv5wJ7X2VaB1Tg/t/CADPE xytuWZPt2FagQkov7sh+eAyCHkXfuFIegX8GO/Wbp/5tMQRcjz+kii7Z/LCmQZpE p2zIBG8xZEeSbmIzWK00rV86g8ahbtwGPVCTvcT+rIKk8UI4U5CfvwAtm2dX/f9d M++Iu0+2VxiLEBrdTliMLDCTe2QEdjB5yUc2Xk4tB9SWrOVI5mBHB9sWQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudeggedgkeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvuffkfhggtggujgesthdtre dttddtvdenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnheptdfhheeuteejudffkefhtdfhfeekgedtvdeiteevgfejtdfgfeffhfeuie eltdeinecuffhomhgrihhnpehfrhgvvggsshgurdhorhhgnecuvehluhhsthgvrhfuihii vgeptdenucfrrghrrghmpehmrghilhhfrhhomhepvhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 19 Nov 2023 11:04:41 -0500 (EST) Date: Sun, 19 Nov 2023 16:04:39 +0000 From: void To: freebsd-arm@freebsd.org Subject: Re: pkgs for FreeBSD:14:aarch64 latest are stale compared to quarterly Message-ID: Mail-Followup-To: freebsd-arm@freebsd.org References: <49AAADF7-2A14-4922-AC56-B763EF0C6FB1@yahoo.com> 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 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <49AAADF7-2A14-4922-AC56-B763EF0C6FB1@yahoo.com> X-Spamd-Result: default: False [-4.88 / 15.00]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.88)[-0.876]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[66.111.4.29:from]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm1,messagingengine.com:s=fm1]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.29]; MIME_GOOD(-0.10)[text/plain]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.29:from]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-arm@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; ARC_NA(0.00)[]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MLMMJ_DEST(0.00)[freebsd-arm@freebsd.org]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; MIME_TRACE(0.00)[0:+]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Rspamd-Queue-Id: 4SYFp33KdQz3fxk X-Spamd-Bar: ---- Hi Mark, (have replied to your reply inline) I don't want to give the impression that I'm foot-tapping impatiently for the latest pkg builds. The reason behind the query was because there are several ports affected by vulns between say 31st Oct and now. I was looking to see if there were updates available in pkgs. Found there weren't, checked and the system was using "latest", so had to build directly from the ports tree which was suboptimal on this hardware. Nevertheless, they all built, the software is up-to-date and that problem is solved. Meanwhile, checked to find the timestamp of 'latest' and found it was 02 Nov, which was surprisingly ancient to me. I thought maybe there was something wrong with the/a builder? So checked this against quarterly, and found quarterly timestamped 2 weeks later than 'latest'. On Sun, Nov 19, 2023 at 06:28:18AM -0800, Mark Millard wrote: >On Nov 19, 2023, at 05:44, void wrote: > >> http://pkg.freebsd.org/FreeBSD:14:aarch64/latest/meta.txz is dated 2nd Nov >> http://pkg.freebsd.org/FreeBSD:14:aarch64/quarterly/meta.txz is dated 15th Nov > >Note: The below does not deal with time to distribute >packages after the overall build completes. The dates >show are start dates, so the start of the next build >gives about the time of the finish of the prior build. (snip) >So: For (only) 140releng-arm64 the finished-dates look like: > >31 Oct 2023 finish quarterly >02 Nov 2023 finish default (a.k.a. latest) >15 Nov 2023 finish quarterly >18 Nov 2023 finish default (a.k.a. latest) so, approx 3 days for a build, if the machine builds quarterly=>latest=>quarterly. Latest completed on the 18th. It's the 19th now (1533 UTC) and both http://pkg0.nyi.freebsd.org/FreeBSD:14:aarch64/latest/meta.txz and http://pkg0.fra.freebsd.org/FreeBSD:14:aarch64/latest/meta.txz are dated 02 Nov. How long would you expect it to take for pkgs to be distributed? >The relative offsets in timing need not be stable over time. >But having a range of days with weeks between the quarterly >and default (a.k.a. latest) most-recent builds of >140releng-arm64 is perfectly normal. I'm with you WRT days, and also days or weeks WRT quarterly lagging latest - but weeks where latest lags quarterly? Maybe my idea/usage of the terms 'quarterly' and 'latest' are different to FreeBSD's. In terms of time, my usage of 'quarterly' means 'about every three months'. So I'd think it reasonable to think that, in the context, 'quarterly' would mean a datestamp from now to three months ago. But never more than a few days more recent than latest, unless there was a problem in building or distributing packages. I thought there might be a problem, hence the original email. --