From nobody Tue May 27 09:06:02 2025 X-Original-To: freebsd-current@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 4b66Ds1wb5z5x8Xw for ; Tue, 27 May 2025 09:06:05 +0000 (UTC) (envelope-from agh@riseup.net) Received: from mx0.riseup.net (mx0.riseup.net [198.252.153.6]) (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-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "mx0.riseup.net", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4b66Dr72Fvz3G8q for ; Tue, 27 May 2025 09:06:04 +0000 (UTC) (envelope-from agh@riseup.net) Authentication-Results: mx1.freebsd.org; none Received: from fews02-sea.riseup.net (fews02-sea-pn.riseup.net [10.0.1.112]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mx0.riseup.net (Postfix) with ESMTPS id 4b66Dq2hjsz9vmy; Tue, 27 May 2025 09:06:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak; t=1748336763; bh=Vd0IZRO091ViYw2mVrBdJ67irvUm4Q4IoaEl6DEYKKA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=M0wdeqzW7zyDhxOzCrL0TUkFkN/YalAO1ZWvjZqOXLT8kfWBCLGUrpbHBlTLyN9ey nw+MsDF9V9U1d3PLHa9MtFSTDRnmjhFb/AfJOqj0cD9JVNGVqBVbbw7rpW9pq5lDZO 541qsZP76VJMYZnrmabvUPWw2JeMBv0ubRxWcm3s= X-Riseup-User-ID: 681400A92AEA642A35C3620E49F579CD0A42C63812399E683CA45CB07AFCCBEE Received: from [127.0.0.1] (localhost [127.0.0.1]) by fews02-sea.riseup.net (Postfix) with ESMTPSA id 4b66Dq16pmzFtdM; Tue, 27 May 2025 09:06:03 +0000 (UTC) List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Date: Tue, 27 May 2025 09:06:02 +0000 From: Alastair Hogge To: Mark Millard Cc: FreeBSD Current Subject: Re: With poudriere how does one create a jail of a slightly older RELEASE ? [github related notes] In-Reply-To: <2177B8F6-D8B9-4FFE-BB29-D3A83B935C6F@yahoo.com> References: <2177B8F6-D8B9-4FFE-BB29-D3A83B935C6F.ref@yahoo.com> <2177B8F6-D8B9-4FFE-BB29-D3A83B935C6F@yahoo.com> Message-ID: Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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:16652, ipnet:198.252.153.0/24, country:US] X-Rspamd-Queue-Id: 4b66Dr72Fvz3G8q X-Spamd-Bar: ---- On 2025-05-27 10:09, Mark Millard wrote: > Alastair Hogge wrote on > Date: Mon, 26 May 2025 22:58:38 UTC : > >> . . . >> >> GitHub is another Walled Garden. You need an account to read code on >> it's platform, > > I'm right now using an old iPad with FireFox looking at the > recent upstream error about fopen("tmp/pkg_add_cache","w") > still being in use in recent pkg-devel update. I did not > log into my github account to do this. (Line 1177 of > pkg_add.c .) The "Sign in" button still says that. > > For reference, I navigated to what ended up > being: > > github.com/freebsd/pkg/blob/main/libpkg/pkg_add.c > > This is in the USA, in case that matters. > > May be you mean something more specific, but, as far as I > can tell, your claim above is just false here. If I point Firefox at https://github.com/search?q=repo%3Amamedev%2Fmame%20freebsd&type=issues, on the left side of the site, under "Filter by", there is the following options: Code Issues Pull requests Discussions Commits Packages Wikis To the right of "Code" will be "...", the remaining items in the list, will have a hit count to the right. Clicking on "Code" takes on to a "Sign in to search code on GitHub" landing page, this is what I meant, sorry for the confusion. A super handy feature, locked behind their Wall. >> and they are terrible at providing access to new >> subscribers. > > I've never had troubles that would lead me to such > a statement --or much of any note. (I do have an > account --and have had it for a long time, so, > likely not matching your specification of "new > subscribers" at this point. I'm not going to create > another account to check a better matching context.) > >> I am on my second account, and none of my up upstream >> Issues are appearing. . . . >> . . . > > I've never had troubles with my issue submittals on > github, including the one today about the bug > referenced above. (Not that I submit such very often.) > The submittal shows up just fine (#2450). > > > === > Mark Millard > marklmi at yahoo.com