From nobody Wed Jan 03 16:35:13 2024 X-Original-To: freebsd-hackers@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 4T4wLx61KTz56DLY for ; Wed, 3 Jan 2024 16:35:37 +0000 (UTC) (envelope-from dan@langille.org) 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 4T4wLx0qxSz4hgd; Wed, 3 Jan 2024 16:35:37 +0000 (UTC) (envelope-from dan@langille.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=langille.org header.s=fm2 header.b=VokGZRY+; dkim=pass header.d=messagingengine.com header.s=fm2 header.b="E q0JnZL"; dmarc=pass (policy=none) header.from=langille.org; spf=pass (mx1.freebsd.org: domain of dan@langille.org designates 66.111.4.29 as permitted sender) smtp.mailfrom=dan@langille.org Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailout.nyi.internal (Postfix) with ESMTP id CCDCC5C0127; Wed, 3 Jan 2024 11:35:35 -0500 (EST) Received: from imap42 ([10.202.2.92]) by compute7.internal (MEProxy); Wed, 03 Jan 2024 11:35:35 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=langille.org; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1704299735; x=1704386135; bh=OBclzwjNR99ozde1gooUQ5EH389s7OAWgo9Spyp1awI=; b= VokGZRY+R/fBBiFLFReNICs4x4x9PcdtTFZK5Zlq0qP114GXtpbDMxcWF5sp03TC q3TPSx1lVQ1zUAoRMR3QZfoRyNj7gu8ykOG5TXyxQdrvvN5c6YtQwcflXDcJ4sGM pY7oF9oMV70f8Gd3km5NgjaZVyYc6xAqUcJVTjxFaAJBFa0PSa6KnYYjzR7Xd3xl alpS2OGjvHw2GP718C6D4qotzwkgMqgkP6zg3rrln8KOmjGE5ckggmiDsJXcf1iK ZpnLUtys2lSF1Qxm4A2RrRKa1uO6OQ0uaY5g5Uo1Y9R+z7zFM6TAVWt2k5CbLr/l RixMHxCVs6Y+ZPl6kiXKsw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :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:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1704299735; x= 1704386135; bh=OBclzwjNR99ozde1gooUQ5EH389s7OAWgo9Spyp1awI=; b=E q0JnZLTKqi0HkiFynqVnyDAEaXICztL1otZ2vdTDCEACIUZMsSNxUbQYcLGdooFD TRclVn4GSZlO/NoXrzZ9ZNcd12wqVvKAHQiqP3Aoop54Ct1qgHORFv157zaD17d0 RzPxQ81LPxl6+N+A128tSCSac/hBRju6tQOsFRUMpZhrdV10IBSXrIU/LoSg1JNz OTcrtnMVsS097s5Kay5B+K+fEf1fZsq3zaWu2NzCEB//dKjvZaw+Lu9qtli0Nd5f DEXsjNFCRJ991NIhQ9Yb22Xx2NyiuSYIAo27Vn6h1upOyBsuI/TBnHB6Xy0Jonob UA/gkYiGLuciZHPBIR8ew== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrvdeghedgledtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvfevufgtgfesthhqredtreerjeenucfhrhhomhepfdff rghnucfnrghnghhilhhlvgdfuceouggrnheslhgrnhhgihhllhgvrdhorhhgqeenucggtf frrghtthgvrhhnpeduveeihfffgeethefgueelgffggfegvdekhfdtfeejueejgfefudet keevfeeugeenucffohhmrghinhepuggrnhgprghtpghlrghnghhilhhlvgdrohhrghdpfh hrvggvsghsugdrohhrghdpfhhrvghshhhpohhrthhsrdhorhhgpdhgihhthhhusgdrtgho mhenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegurg hnsehlrghnghhilhhlvgdrohhrgh X-ME-Proxy: Feedback-ID: ifbf9424e:Fastmail Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6F404BC007D; Wed, 3 Jan 2024 11:35:35 -0500 (EST) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.9.0-alpha0-1364-ga51d5fd3b7-fm-20231219.001-ga51d5fd3 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Message-Id: <284b50b2-4e3a-4ca2-8433-dd6a2e3ec31f@app.fastmail.com> In-Reply-To: References: Date: Wed, 03 Jan 2024 11:35:13 -0500 From: "Dan Langille" To: "Philip Paeps" , "Mark Millard" Cc: "FreeBSD Hackers" Subject: Re: list of valid ABI combinations Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.21 / 15.00]; NEURAL_HAM_SHORT(-0.72)[-0.717]; DMARC_POLICY_ALLOW(-0.50)[langille.org,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[66.111.4.29:from]; R_DKIM_ALLOW(-0.20)[langille.org:s=fm2,messagingengine.com:s=fm2]; 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]; XM_UA_NO_VERSION(0.01)[]; ARC_NA(0.00)[]; DWL_DNSWL_NONE(0.00)[messagingengine.com:dkim]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; FREEFALL_USER(0.00)[dan]; MIME_TRACE(0.00)[0:+]; RCVD_TLS_LAST(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; FROM_EQ_ENVFROM(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_TO(0.00)[freebsd.org,yahoo.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_ALL(0.00)[]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; DKIM_TRACE(0.00)[langille.org:+,messagingengine.com:+] X-Rspamd-Queue-Id: 4T4wLx0qxSz4hgd On Tue, Jan 2, 2024, at 10:46 AM, Dan Langille wrote: > On Tue, Jan 2, 2024, at 12:45 AM, Philip Paeps wrote: >> On 2024-01-02 12:38:47 (+0800), Mark Millard wrote: >>> [FYI: My internet access is limited to a cellphone for some number o= f=20 >>> days.] >>> >>>> On Jan 1, 2024, at 19:26, Philip Paeps wrote: >>>> >>>> =EF=BB=BFOn 2023-12-07 23:03:33 (+0800), Mark Millard wrote: >>>>> Dan Langille wrote: >>>>>> My goal is to automatically maintain this table, from which=20 >>>>>> FreshPorts fetches package information: >>>>>> >>>>>> freshports.dev=3D# select * from abi order by name; >>>>>> id | name | active >>>>>> ----+----------------------+-------- >>>>>> 9 | FreeBSD:12:aarch64 | t >>>>>> [...] >>>>>> 53 | FreeBSD:15:riscv64 | t >>>>>> (31 rows) >>>>> >>>>> The name list in the middle (/bin/sh context): >>>>> >>>>> # fetch https://pkg.freebsd.org/index.html >>>>> index.html 3606 B 103=20 >>>>> MBps 00s >>>>> >>>>> # grep FreeBSD: index.html | sed -e 's@.*\(FreeBSD:[^ <]*\).*@\1@'= |=20 >>>>> sort >>>>> FreeBSD:12:aarch64 >>>>> [...] >>>>> FreeBSD:15:powerpc64le >>>>> >>>>> There might be issues at times with=20 >>>>> https://pkg.freebsd.org/index.html not >>>>> being in sync. As far as I can tell, that page is manually=20 >>>>> maintained. >>>> >>>> clusteradm updates that page to match what we're actually=20 >>>> distributing. If it doesn't reflect reality, that's a bug, and we'= d=20 >>>> like to know please. :-) >>> >>> Does that include the =E2=80=9Conly ??? Is updated=E2=80=9D sorts of= notes? >> >> Yes. Please let clusteradm know if the notes don't appear to reflect=20 >> reality. >> >> clusteradm maintains the pkgsync infrastructure, which includes the=20 >> index page on the mirrors. pkgmgr is responsible for scheduling the=20 >> builds. (And ports committers are responsible for making sure packag= es=20 >> are even buildable). >> >>> For example, FreeBSD:13:armv6 Latest dates back to 2021-Jan-25 but=20 >>> there is no note about quarterly only. Various FreeBSD:15:* do not=20 >>> have notes about Latest only, despite having no quarterly at all. So= me=20 >>> other cases have notable but shorter differences in the Latest vs.=20 >>> Quarterly time frames, suggesting only one is being updated but no=20 >>> fixed difference is definitive for that status. >> >> The pkgsync infrastructure doesn't really care how often packages are=20 >> updated. If memory serves, we first added a "quarterly only" note wh= en=20 >> the thunderxX generation of aarch64 builders broke with distressing=20 >> regularity. The ampereX builders are much more reliable. >> >> I think the current situation for armv6 is "updated irregularly". =20 >> PowerPC is in the same boat as aarch64 in the ThunderX era: when the=20 >> hardware works, packages are updated. >> >>> Dan=E2=80=99s activities with the page do not use such notes as far = as I=20 >>> know. >> >> Would it help if we added an easy to parse text file listing the ABIs=20 >> we're currently distributing? That won't tell you anything about the=20 >> build schedule, but it'll at least tell you what's live, without havi= ng=20 >> to parse HTML and hope we don't break it. Could that extra file be useful to clusteradm, and is the 'single source= of truth', then yes, that would be useful to third parties as well.=20 Changes to FreshPorts ABI table just tells it what ABI to attempt to imp= ort. All that is lost/found is the package information. As such, it does not otherwise affect the service. Right now, I have a script which works. It will be deployed on dev.fres= hports.org later today. It will refresh the ABI on a daily basis. > I think this threads provides sufficient information for 'automaticall= y know > the list of valid ABI' to proceed: > > https://github.com/FreshPorts/freshports/issues/508 This is all implemented by short shell scripts, the longest of which is = 32 lines. See the URL above for details. --=20 Dan Langille dan@langille.org