> Hi Wojtek, > > Is there any way of translating this into a git url that can be "git > cloned"? I figure there must be ... but I can't see for the life of > me where the git clone url is!
It wasn't obvious to me either. But hey, there is the Internet! I found that this [1] guide (sort of) works. Minus that the "bundle" downloaded is not in the actual format we associate the term "git bundle" with (it's instead just a tar'ed .git directory). And that for me, it gets downloaded as an uncompressed tar archive rather than gzip-compressed (as suggested by the author). [1] https://til.simonwillison.net/github/software-archive-recovery Also, even if you disable JS, you can easily find the `swh:1:snp:…' id in the source of that SWH page. Btw, you might consider making the repository publicly cloneable. Like putting it on Codeberg or repo.or.cz. Btw2, I suspect the replicant servers had simply fallen prey to AI crawlers. Disabling the web interface on git.replicant.us could help. And in the long run, it could be reinstated behind some crawler-stopper. Even dumb solutions, like mine [2], seem to be still effective. [2] https://git.koszko.org/stop-crawlers?then=simple-browser-extension%2Flog%2F Best! Wojtek -- W. Kosior website: https://koszko.org/koszko.html fediverse: https://friendica.me/profile/koszko/profile PGP fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A On Thu, 9 Jul 2026 15:41:36 +0100 J05HYYY <[email protected]> wrote: > Hi Wojtek, > > Is there any way of translating this into a git url that can be "git > cloned"? I figure there must be ... but I can't see for the life of > me where the git clone url is! > > https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://git.replicant.us/replicant/vendor_replicant-data&visit_type=git > > Josh > > On Wed, 8 Jul 2026 22:56:23 +0200 > "W. Kosior via Replicant" <[email protected]> wrote: > > > > Hi, > > > since a few weeks, I encountered a lot of difficulties to repo sync > > > the repo of Replicant 6. > > > > > > Josh seems to get the same issues. > > > > > > Is there some way to solve this issue? > > > > Hi there, > > > > although I have never had the opportunity to touch > > a Replicant-supported device, I am following this list as part of > > peanut gallery and I think there might be a solution. > > > > Try marrying repo with SWH copy of the sources [1]. > > > > [1] > > https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://git.replicant.us/replicant/vendor_replicant-data&visit_type=git > > > > Good luck! > > Wojtek > > > > -- > > W. Kosior > > > > website: https://koszko.org/koszko.html > > fediverse: https://friendica.me/profile/koszko/profile > > PGP fingerprint: E972 7060 E3C5 637C 8A4F 4B42 4BC5 221C 5A79 FD1A > > > > > > On Wed, 08 Jul 2026 19:54:55 +0000 > > Fil Lupin via Replicant <[email protected]> wrote: > > > > > Hi, > > > since a few weeks, I encountered a lot of difficulties to repo sync > > > the repo of Replicant 6. > > > > > > Josh seems to get the same issues. > > > > > > Is there some way to solve this issue? > > > > > > last lines I got are > > > --- > > > Fetching projects: 99% (498/501) > > > replicant/vendor_replicant-scripts.giterror: Cannot fetch > > > replicant/vendor_replicant-data.git from > > > https://git.replicant.us/replicant/vendor_replicant-data.git > > > Fetching projects: 99% (499/501) > > > replicant/vendor_replicant-data.giterror: Cannot fetch > > > replicant/toolchain_binutils.git from > > > https://git.replicant.us/replicant/toolchain_binutils.gitFetching > > > projects: 99% (500/501) replicant/toolchain_binutils.git --- Regards > > > > > > - Fil Lupin. > > >
pgp8BwlLGVCt1.pgp
Description: OpenPGP digital signature
_______________________________________________ Replicant mailing list [email protected] https://lists.osuosl.org/mailman/listinfo/replicant
