Date: Sat, 17 Feb 2024 22:19:15 +0100 From: Moin Rahman <bofh@freebsd.org> To: FreeBSD Mailing List <freebsd-ports@freebsd.org> Cc: Tomoaki AOKI <junchoon@dec.sakura.ne.jp>, Mario Marietto <marietto2008@gmail.com>, freebsd-hackers <freebsd-hackers@freebsd.org>, Mark Millard <marklmi@yahoo.com> Subject: Re: files/edd962f76ea4b5869f3c6f8ee5438fb9750b802d02bb8035fe1b7bd0a8ba7401.gz not found -- snapshot corrupt. Message-ID: <F1D4AA38-788F-4613-8F9F-E0B0A827318B@freebsd.org> In-Reply-To: <F7BD898B-BCCF-475D-9D69-5A79CC34D639@yahoo.com> References: <CA%2B1FSiiGqsUip5YSfCQTR2pDt6NBfAxuMYAHy_EMo7onsKx0Sg@mail.gmail.com> <CANCZdfr3pOgs8CUFwheG1JUphXr4huGwTXHudQLapkw-jhmT7Q@mail.gmail.com> <7AA6A6B8-9BAE-4B03-9EF4-4A4D242582B4@yahoo.com> <20240215184926.42aafbbdd5644be492f600fc@dec.sakura.ne.jp> <F7BD898B-BCCF-475D-9D69-5A79CC34D639@yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--Apple-Mail=_40F3F8C3-7EDB-45F7-8588-9E05D4B4C634 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 > On Feb 15, 2024, at 6:22 PM, Mark Millard <marklmi@yahoo.com> wrote: >=20 > On Feb 15, 2024, at 01:49, Tomoaki AOKI <junchoon@dec.sakura.ne.jp> = wrote: >=20 >> Dropping freebsd-current ML as this doesn't related current (main) = but >> deprecated release (12.4). >> Dropping freebsd-arm ML as I'm not subscribed and surely be bounced, >> and the problem is ports specific. >> Adding freebsd-ports ML as this is ports related. >>=20 >> Commented inline below. >>=20 >> On Wed, 14 Feb 2024 19:15:43 -0800 >> Mark Millard <marklmi@yahoo.com> wrote: >>=20 >>> On Feb 14, 2024, at 18:23, Warner Losh <imp@bsdimp.com> wrote: >>>=20 >>>> You may need to grab the repo. You may have to back up to = December's ports tree... >>>=20 >>> My understanding was that portsnap was staying installed >>> on 13.*-RELEASE until the last version is EOL and that >>> portsnap servers would be kept operational with valid >>> content until then. >>>=20 >>> I would have guessed that this would mean that 12.4-RELEASE >>> or the like would also be able to use the portsnap it >>> contains over that same time frame. >>>=20 >>> Am I wrong? >>>=20 >>> As stands, git use on 12.4-RELEASE would require bootstrapping >>> git somehow, possibly via portsnap, building git, and then >>> installing git (and the other stuff required). >>>=20 >>> (Not that I use portsnap.) >>=20 >> Me too don't use portsnap, but if you want to switch to git, maybe >> installing git from pkg (as 12.x is already EoL'ed, extract git.pkg >> from disc1.iso for armv7, install it) >=20 > There is/was no armv7 disc1.iso (or dvd1.iso) to do > this with. >=20 > = http://ftp-archive.freebsd.org/pub/FreeBSD-Archive/old-releases/ISO-IMAGES= /12.4/ >=20 > has only the following for 12.4-RELEASE for armv7: >=20 > FreeBSD-12.4-RELEASE-arm-armv7-BANANAPI.img.xz > FreeBSD-12.4-RELEASE-arm-armv7-CUBIEBOARD.img.xz > FreeBSD-12.4-RELEASE-arm-armv7-CUBIEBOARD2.img.xz > FreeBSD-12.4-RELEASE-arm-armv7-CUBOX-HUMMINGBOARD.img.xz > FreeBSD-12.4-RELEASE-arm-armv7-GENERICSD.img.xz > FreeBSD-12.4-RELEASE-arm-armv7-RPI2.img.xz > FreeBSD-12.4-RELEASE-arm-armv7-WANDBOARD.img.xz >=20 > No dvd1/disc1/memstick material was ever produced for > armv7 12.4-RELEASE (or for any other armv7 release as > far as I know). None of the above *.img.xz files > includes any installed port-packages, nor a populated > /usr/ports/ tree. >=20 >=20 > But the /usr/ports/ tree could be extracted from a > *.iso or *.img that is not for the armv7 but happens > to contain a /usr/ports/ : /usr/ports/ is not platform > specific in its content. (Avoid powerpc* because of > big endian file system issues?) >=20 >> and clone repo into >> clean /usr/ports would be better not to poisoning by different = metadata. >> And check out the ports tree of which just befere 12.4 was obsoleted. >> After that, ports tree starts dropping support for 12.x. >>=20 >> Additional note: >> I myseld don't even tried, but for portsnap users who needs (forced) >> to switch to git, net/gitup could be your friend. >> IIUC, it would be something like csup for cvs or svnup for = subversion. >>=20 >>=20 >>>> Warner >>>>=20 >>>> On Wed, Feb 14, 2024, 5:51=E2=80=AFPM Mario Marietto = <marietto2008@gmail.com> wrote: >>>> Hello. >>>>=20 >>>> After a lot of work I've been able to install FreeBSD 12.04 for = armv7 on my ARM Chromebook. Now I would like to install some ports. This = is what happens when I try to get a fresh ports tree : >>>>=20 >>>> marietto@freebsd:/usr # sudo portsnap fetch extract >>>>=20 >>>> .... >>>> /usr/ports/databases/py-sqlalchemy10/ >>>> /usr/ports/databases/py-sqlalchemy11/ >>>> /usr/ports/databases/py-sqlalchemy12/ >>>> /usr/ports/databases/py-sqlalchemy13/ >>>> /usr/ports/databases/py-sqlalchemy14/ >>>> /usr/ports/databases/py-sqlalchemy20/ >>>> /usr/ports/databases/py-sqlcipher3/ >>>> = files/edd962f76ea4b5869f3c6f8ee5438fb9750b802d02bb8035fe1b7bd0a8ba7401.gz = not found -- snapshot corrupt. >>>>=20 >>>> I repeated the "portsnap fetch extract" command,but I always get = the same error. >>>>=20 >>=20 >=20 > =3D=3D=3D > Mark Millard > marklmi at yahoo.com >=20 >=20 Hi Everyone, It has comeup multiple times in discussion about howto bootstrap a ports tree without portsnap in base when the decision was made to cut the chord for portsnap. Or even discussion came up about having gitup in the base or using a git pkg to bootstrap. =46rom my perspective it's as simple as the following for this specific case: # fetch https://cgit.freebsd.org/ports/snapshot/ports-12-eol.tar.gz # tar -zxf ports-12-eol.tar.gz --strip-components 1 -C /usr/ports Other users who need a more recent snapshot can definitely find their way. Snapshot archive of every git commit is available for download without the need of git checkout. Although this does not create or include the git meta information to easily update again using git but once the portstree has been bootstrapped and git installed; sky is the limit. Kind regards, Moin --Apple-Mail=_40F3F8C3-7EDB-45F7-8588-9E05D4B4C634 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP -----BEGIN PGP SIGNATURE----- iQKTBAEBCgB9FiEETfdREoUGjQZKBS+fvbm1phfAvJEFAmXRItNfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDRE Rjc1MTEyODUwNjhEMDY0QTA1MkY5RkJEQjlCNUE2MTdDMEJDOTEACgkQvbm1phfA vJGI+Q//VAGTUb3fLkAJQN5HgiK2NiJ/BoTFT677qgRqZgwjxxZ4R/yMki7MnhCf yWLZH3oa39GmRPF8gaS9SdHjzX7w2L30jfnMiIrYUlKUEYcbDmDsIoDq04kY+1IP dOhRrKMKnkK7RJXazmHsZIEmpHJLg3iNPoweyU31J15/ldvr3Jqv5+XfGmvIN3Ba uqbAYMjccOn4W1cmBHyQjJ972UAudE+ZkdPRPJdk9rW6iIwUHLnGRTJ5EawAehAR U+6/mO8l0vsBb7kkxHdBFFPIwAEinUgwji1SvUaKafvp64Zy0AaLRbaItXvJq65h 5hFY49i7T3859Wrmi4rbWbm4GkDQg4kRxlrU/2IPDE2T8860t0sRWI2OnCj4/cHO 92JR5P7CtOrJAiyv5Amr6C70/m64Mc87vsASDW1qpbFGFBij4zC9VUf5tWols2yB UPOXeqgcx4CmafUgu7W5vQliV02wREFuqAiPhxVT0RXNYergNv/C1Hqx1GkxAlem gkUuWEOhoivyXWzpLobRhKB1/XAc+Xb3wa8EdkZBfVY4RWO4HCW3fFxMCidCKPgZ YTMFq61Fmol4n5xNU2gadFevaX06o+Y8FhyjmVPkBl62YGV//ECzJwGzpFaCAwi6 qLZTGP0FxP0gSulHlnL6lUICDrQOZE2s8ItaPM4DkExfm53fvBQ= =HDww -----END PGP SIGNATURE----- --Apple-Mail=_40F3F8C3-7EDB-45F7-8588-9E05D4B4C634--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F1D4AA38-788F-4613-8F9F-E0B0A827318B>