Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Dec 2020 13:50:53 -0800
From:      Mark Millard <marklmi@yahoo.com>
To:        bob prohaska <fbsd@www.zefox.net>
Cc:        Ronald Klop <ronald-lists@klop.ws>, FreeBSD Current <freebsd-current@freebsd.org>, freebsd-arm@freebsd.org
Subject:   Re: HEADS UP: FreeBSD src repo transitioning to git this weekend
Message-ID:  <28028C56-7E5A-4961-8F09-36351CDDFF20@yahoo.com>
In-Reply-To: <19860CB5-716C-47A9-BB96-0EA16051DD9D@yahoo.com>
References:  <20201222183900.GA22353@www.zefox.net> <1249102000.16891.1608669265488@localhost> <20201222210628.GA34436@www.zefox.net> <19860CB5-716C-47A9-BB96-0EA16051DD9D@yahoo.com>

next in thread | previous in thread | raw e-mail | index | archive | help


On 2020-Dec-22, at 13:31, Mark Millard <marklmi at yahoo.com> wrote:



> On 2020-Dec-22, at 13:06, bob prohaska <fbsd at www.zefox.net> wrote:
>=20
>> On Tue, Dec 22, 2020 at 09:34:25PM +0100, Ronald Klop wrote:
>>>=20
>>> what does "pkg install git" do for you? NB: I use "pkg install =
git-lite".
>>> Prevents about 1000 dependencies.
>>>=20
>>=20
>> That seems to have worked. It reported something about package =
management
>> not being installed, but after a prompt installed pkg-static and set
>> up a version of git which seems to run. Svnlite had been working =
without
>> this step.....=20
>>=20
>> This is for a Pi2B v 1.1, arm v7 only.
>=20
> Ahh. As far as I know armv7 ports have been building right along. It =
was
> arm64 that had the old build system fail as I understand.
>=20
>> Using the "mini git primer" at =
https://hackmd.io/hJgnfzd5TMK-VHgUzshA2g
>> I tried to clone stable/12 expecting that the -beta would be gone.
>>=20
>> It looks as if I'm still jumping the gun. Although=20
>> cgit.freegbsd.org replies to ping, using
>>=20
>> bob@www:/usr % git clone cgit.freebsd.org -b stable/12 freebsd-src
>>=20
>> reports:
>>=20
>> fatal: repository 'cgit.freebsd.org' does not exist
>>=20
>> This is just a rehearsal, so I can wait, but if I've=20
>> made other mistakes please point them out.
>=20
> cgit.freebsd.org is not for getting clones from, just like =
svnweb.freebsd.org
> was not for getting svn from.
>=20
> Using main as an example, not stable/12 . . .
>=20
> The bottom of the page https://cgit.freebsd.org/src/ shows 3 URL's for
> use in cloning src:
>=20
> Clone
> https://git.FreeBSD.org/src.git
> anongit@git.FreeBSD.org:src.git
> git@gitrepo.FreeBSD.org:src.git

Hmm. It turns out that the last 2 are links on that page and the
links expand out to:

https://cgit.freebsd.org/src/anongit@git.FreeBSD.org:src.git
and:
https://cgit.freebsd.org/src/git@gitrepo.FreeBSD.org:src.git

So it seems that there are ways to clone that involve referencing
cgit.freebsd.org .

> The last two are not explicit about notation like ssh: prefixes.
>=20
> I cloned FreeBSD's src.git via:
>=20
> git clone -o freebsd --config =
remote.freebsd.fetch=3D'+refs/notes/*:refs/notes/*' =
ssh://anongit@git.freebsd.org/src.git freebsd-src
>=20
> Other than using the ssh: style, I got the command notation from
> part of:
>=20
> https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
>=20
> The remote.freebsd.fetch related material allows for finding the svn =
version
> numbers for the older content.
>=20
> Checking out stable/12 from the clone should be possible after the =
above, but
> that is not what I've been doing.
>=20


=3D=3D=3D
Mark Millard
marklmi at yahoo.com
( dsl-only.net went
away in early 2018-Mar)




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?28028C56-7E5A-4961-8F09-36351CDDFF20>