Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[bob prohaska]

On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
> 
> The FreeBSD project will be moving it's source repo from subversion to git
> starting this this weekend. The docs repo was moved 2 weeks ago. The ports
> repo will move at the end of March, 2021 due to timing issues.
> 

Is there some way to obtain git on a Pi2B running 
13.0-CURRENT FreeBSD 13.0-CURRENT #2 r365692
without installing the ports tree? I expected 
to find git in base, but it isn't there. 

Can it be found  under another package name?

Thanks for reading, and any guidance!

bob prohaska

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[Ronald Klop]

Van: bob prohaska 
Datum: 22 december 2020 19:38
Aan: freebsd-...@freebsd.org
CC: FreeBSD Current 
Onderwerp: Re: HEADS UP: FreeBSD src repo transitioning to git this weekend



On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
> 
> The FreeBSD project will be moving it's source repo from subversion to git

> starting this this weekend. The docs repo was moved 2 weeks ago. The ports
> repo will move at the end of March, 2021 due to timing issues.
> 

Is there some way to obtain git on a Pi2B running 
13.0-CURRENT FreeBSD 13.0-CURRENT #2 r365692
without installing the ports tree? I expected 
to find git in base, but it isn't there. 


Can it be found  under another package name?

Thanks for reading, and any guidance!

bob prohaska

___
freebsd-...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "freebsd-arm-unsubscr...@freebsd.org"





what does "pkg install git" do for you? 
NB: I use "pkg install git-lite". Prevents about 1000 dependencies.



Regards,
Ronald
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[bob prohaska]

On Tue, Dec 22, 2020 at 09:34:25PM +0100, Ronald Klop wrote:
> 
> what does "pkg install git" do for you? NB: I use "pkg install git-lite".
> Prevents about 1000 dependencies.
> 

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. 

This is for a Pi2B v 1.1, arm v7 only.

Using the "mini git primer" at https://hackmd.io/hJgnfzd5TMK-VHgUzshA2g
I tried to clone stable/12 expecting that the -beta would be gone.

It looks as if I'm still jumping the gun. Although 
cgit.freegbsd.org replies to ping, using

bob@www:/usr % git clone cgit.freebsd.org -b stable/12 freebsd-src

reports:

fatal: repository 'cgit.freebsd.org' does not exist

This is just a rehearsal, so I can wait, but if I've 
made other mistakes please point them out.

Thanks for your help!

bob prohaska

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[Kristof Provost]

On 22 Dec 2020, at 22:06, bob prohaska wrote:
> On Tue, Dec 22, 2020 at 09:34:25PM +0100, Ronald Klop wrote:
>>
>> what does "pkg install git" do for you? NB: I use "pkg install git-lite".
>> Prevents about 1000 dependencies.
>>
>
> 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.
>
> This is for a Pi2B v 1.1, arm v7 only.
>
> Using the "mini git primer" at https://hackmd.io/hJgnfzd5TMK-VHgUzshA2g
> I tried to clone stable/12 expecting that the -beta would be gone.
>
> It looks as if I'm still jumping the gun. Although
> cgit.freegbsd.org replies to ping, using
>
> bob@www:/usr % git clone cgit.freebsd.org -b stable/12 freebsd-src
>
> reports:
>
> fatal: repository 'cgit.freebsd.org' does not exist
>
That’s because you have the wrong URL for the src repo.
Try `git clone https://git.FreeBSD.org/src.git  -b stable/12 freebsd-src`

Best regards,
Kristof
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[bob prohaska]

On Tue, Dec 22, 2020 at 12:19:03PM -0800, Mark Millard wrote:
> 
> git in base would have licensing issues.
> 
I gather you're referring to GPLv2. A sticky wicket.

The trouble with ports is the tree is getting awfully big.
The host in question has a 32 GB disk and is over half full
with just a base source installation. Adding a "dormant"
ports tree will take nearly 2 GB, most of which is not used.

Might there be some way to clone a "sparse tree" including 
only one port, which then leafs out just enough to build that
port and dependencies? 

When the ports system was introduced it seemed a marvel of
compactness and efficiency. Time marches on.

> Pi2B: v1.1 (armv7 only)? v1.2 running armv7 FreeBSD?
> v1.2 running arm64 FreeBSD?
>
Sorry for the ambiguity... It's v1.1, armv7 only. That's
why I want to test git on this particular machine. Git
seems to work fine on the Pi3.

Thanks for replying!

bob prohaska

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[Kristof Provost]

On 22 Dec 2020, at 22:50, Mark Millard wrote:

On 2020-Dec-22, at 13:31, Mark Millard  wrote:

Clone
https://git.FreeBSD.org/src.git
anon...@git.freebsd.org:src.git
g...@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/anon...@git.freebsd.org:src.git
and:
https://cgit.freebsd.org/src/g...@gitrepo.freebsd.org:src.git

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

No, that’s just a configuration bug in cgit. I’m sure it’ll get 
fixed in due course.


The text version of the links is the correct version.

Best regards,
Kristof
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[John Kennedy]

Attributions are really confusing at this point...

On 2020-Dec-22, at 13:06, bob prohaska  wrote:
> bob@www:/usr % git clone cgit.freebsd.org -b stable/12 freebsd-src

On 2020-Dec-22, at 13:31, Mark Millard  wrote:
> I cloned FreeBSD's src.git via:
> git clone -o freebsd --config 
> remote.freebsd.fetch='+refs/notes/*:refs/notes/*' 
> ssh://anon...@git.freebsd.org/src.git freebsd-src

  Bob, like mark, I replicated -CURRENT from git by:

cd /usr/src
git clone -o freebsd --config 
remote.freebsd.fetch='+refs/notes/*:refs/notes/*' \
anon...@git.freebsd.org:src.git .
git config pull.ff only
git pull -v

  Special callout...  that "-o freebsd" and the "--config remote.freebsd.fetch"
are related (changing the origin label), and if you don't have them in sync you
won't pull down the refs/notes, so you git logs won't have all the details and
some of the detailed info (rev, commit Id, total refs) won't show up normally.

  I don't think https was working when I initially tried, but this worked.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[Paul Mather]

On Dec 22, 2020, at 1:39 PM, bob prohaska  wrote:

> On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
>> 
>> The FreeBSD project will be moving it's source repo from subversion to git
>> starting this this weekend. The docs repo was moved 2 weeks ago. The ports
>> repo will move at the end of March, 2021 due to timing issues.
>> 
> 
> Is there some way to obtain git on a Pi2B running 
> 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r365692
> without installing the ports tree? I expected 
> to find git in base, but it isn't there. 
> 
> Can it be found  under another package name?
> 
> Thanks for reading, and any guidance!


Git (and git-lite) are available only in ports/packages at the moment.  For 
those wanting to track src via git, you need to install it from there.  I 
believe any plans for a git-compatible tool in base would be derived from Got 
(devel/got) due to licensing.

But, unless I'm mistaken, there is no need to install git to be able to 
continue to get copies of src.  It's only developers who need to commit changes 
to src that need to switch over to git in the near future.  Just as FreeBSD's 
src has been made available as a Git repository from the canonical Subversion 
repo (e.g., on GitHub), I'm sure the reverse will be true for some time and 
you'll be able to continue to get src updates via Subversion.  That would 
surely be the case for existing releases (otherwise it would be a huge POLA 
violation).

I track NetBSD src via Git, even though that project currently officially uses 
CVS.

Cheers,

Paul.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[Mark Millard]

On 2020-Dec-22, at 10:39, bob prohaska  wrote:

> On Wed, Dec 16, 2020 at 05:46:35PM -0700, Warner Losh wrote:
>> 
>> The FreeBSD project will be moving it's source repo from subversion to git
>> starting this this weekend. The docs repo was moved 2 weeks ago. The ports
>> repo will move at the end of March, 2021 due to timing issues.
>> 
> 
> Is there some way to obtain git on a Pi2B running 
> 13.0-CURRENT FreeBSD 13.0-CURRENT #2 r365692
> without installing the ports tree? I expected 
> to find git in base, but it isn't there. 
> 
> Can it be found  under another package name?
> 

git in base would have licensing issues.

Pi2B: v1.1 (armv7 only)? v1.2 running armv7 FreeBSD?
v1.2 running arm64 FreeBSD?


It does appear that arm64 ports builds have started again, or are at
least being experimented with . . .

Filling the Built search field with "/git" at:

http://ampere2.nyi.freebsd.org/build.html?mastername=head-arm64-default&build=p557699_s368500

shows that devel/git built. The context looks to be:

FreeBSD head -r368500 was used to as the context the builds were for.
Ports head   -r557699 was the vintage of the ports tree build.
This is for head-arm64-default, not a quarterly build.

It also shows devel/git@lite as having been built --and
devel/git@gui and devel/git@tiny and devel/git-lfs and
so on.

The page also reports:

Queued  Built   Failed  Skipped Ignored Remaining
32987   28781   304 3106796 0
Load Averages   SwapinfoElapsed Pkg/HourImpulse
( 4%) 1.31 1.40 1.664.41%   142:17:22   205 --

It is the only modern arm64 build that I found with anywhere near 28781
ports built.

Looks like this is for well after head -r365692 .

Unfortunately, https://pkg-status.freebsd.org/builds?type=package does
not yet seem to include ampere2.nyi.freebsd.org based builds.

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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[Mark Millard]

On 2020-Dec-22, at 13:06, bob prohaska  wrote:

> On Tue, Dec 22, 2020 at 09:34:25PM +0100, Ronald Klop wrote:
>> 
>> what does "pkg install git" do for you? NB: I use "pkg install git-lite".
>> Prevents about 1000 dependencies.
>> 
> 
> 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. 
> 
> This is for a Pi2B v 1.1, arm v7 only.

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.

> Using the "mini git primer" at https://hackmd.io/hJgnfzd5TMK-VHgUzshA2g
> I tried to clone stable/12 expecting that the -beta would be gone.
> 
> It looks as if I'm still jumping the gun. Although 
> cgit.freegbsd.org replies to ping, using
> 
> bob@www:/usr % git clone cgit.freebsd.org -b stable/12 freebsd-src
> 
> reports:
> 
> fatal: repository 'cgit.freebsd.org' does not exist
> 
> This is just a rehearsal, so I can wait, but if I've 
> made other mistakes please point them out.

cgit.freebsd.org is not for getting clones from, just like svnweb.freebsd.org
was not for getting svn from.

Using main as an example, not stable/12 . . .

The bottom of the page https://cgit.freebsd.org/src/ shows 3 URL's for
use in cloning src:

Clone
https://git.FreeBSD.org/src.git
anon...@git.freebsd.org:src.git
g...@gitrepo.freebsd.org:src.git

The last two are not explicit about notation like ssh: prefixes.

I cloned FreeBSD's src.git via:

git clone -o freebsd --config remote.freebsd.fetch='+refs/notes/*:refs/notes/*' 
ssh://anon...@git.freebsd.org/src.git freebsd-src

Other than using the ssh: style, I got the command notation from
part of:

https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md

The remote.freebsd.fetch related material allows for finding the svn version
numbers for the older content.

Checking out stable/12 from the clone should be possible after the above, but
that is not what I've been doing.

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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[Mark Millard]

On 2020-Dec-22, at 13:31, Mark Millard  wrote:



> On 2020-Dec-22, at 13:06, bob prohaska  wrote:
> 
>> On Tue, Dec 22, 2020 at 09:34:25PM +0100, Ronald Klop wrote:
>>> 
>>> what does "pkg install git" do for you? NB: I use "pkg install git-lite".
>>> Prevents about 1000 dependencies.
>>> 
>> 
>> 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. 
>> 
>> This is for a Pi2B v 1.1, arm v7 only.
> 
> 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.
> 
>> Using the "mini git primer" at https://hackmd.io/hJgnfzd5TMK-VHgUzshA2g
>> I tried to clone stable/12 expecting that the -beta would be gone.
>> 
>> It looks as if I'm still jumping the gun. Although 
>> cgit.freegbsd.org replies to ping, using
>> 
>> bob@www:/usr % git clone cgit.freebsd.org -b stable/12 freebsd-src
>> 
>> reports:
>> 
>> fatal: repository 'cgit.freebsd.org' does not exist
>> 
>> This is just a rehearsal, so I can wait, but if I've 
>> made other mistakes please point them out.
> 
> cgit.freebsd.org is not for getting clones from, just like svnweb.freebsd.org
> was not for getting svn from.
> 
> Using main as an example, not stable/12 . . .
> 
> The bottom of the page https://cgit.freebsd.org/src/ shows 3 URL's for
> use in cloning src:
> 
> Clone
> https://git.FreeBSD.org/src.git
> anon...@git.freebsd.org:src.git
> g...@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/anon...@git.freebsd.org:src.git
and:
https://cgit.freebsd.org/src/g...@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.
> 
> I cloned FreeBSD's src.git via:
> 
> git clone -o freebsd --config 
> remote.freebsd.fetch='+refs/notes/*:refs/notes/*' 
> ssh://anon...@git.freebsd.org/src.git freebsd-src
> 
> Other than using the ssh: style, I got the command notation from
> part of:
> 
> https://github.com/bsdimp/freebsd-git-docs/blob/main/src-cvt.md
> 
> The remote.freebsd.fetch related material allows for finding the svn version
> numbers for the older content.
> 
> Checking out stable/12 from the clone should be possible after the above, but
> that is not what I've been doing.
> 


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

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: HEADS UP: FreeBSD src repo transitioning to git this weekend

[John-Mark Gurney]

Steffen Nurpmeso wrote this message on Fri, Dec 18, 2020 at 19:28 +0100:
> Brooks Davis wrote in
>  <20201218175241.ga72...@spindle.one-eyed-alien.net>:
>  |On Thu, Dec 17, 2020 at 05:53:20PM -0800, Thomas Mueller wrote:
>  |>>> I hope we don't have to start signing all commits.  saltstack/salt has
>  |>>> that policy, and it's extremely annoying.
>  |> 
>  |>> Have to? Not currently. As with all process changes, there will be
>  |>> community discussion around the different points.
>  |> 
>  |>> Warner
>  |> 
>  |> I hope not!
>  |> 
>  |> Signatures, at least in email messages, are just an annoyance as \
>  |> I see them.
>  |> 
>  |> I don't even know how do sign an email message or make use of a signatur\
>  |> e in a message I receive.
>  |> 
>  |> I have never made a commit to a repository, so would not be familiar \
>  |> with signatures there; imagine it would be a barrier.
>  |
>  |Signed commits have no practicl effect on users of a repo.
> 
> Well you can verify integrity of a repository regardless of how it
> was distributed, this is why it is done, right.
> 
>   #?0$ git log --oneline --show-signature -1 v14.9.20.ar
>   16a21755 (...)
>   gpg: Signature made Sun 13 Dec 2020 12:43:44 AM CET
>   gpg:using RSA key DF082F6AEEC8C2FF
>   gpg: Good signature from "Steffen Nurpmeso "
>   Bump S-nail v14.9.20.ar ("Sombre Tit (Trauermeise)"), 2020-12-12
> 
>   #?0$ git tag -v v14.9.20.ar; echo $?
>   object 16a21755fd1fade2b15fdb78a592f12169c3453f
>   type commit
>   tag v14.9.20.ar
>   tagger Steffen Nurpmeso  1607816624 +0100
>   
>   Bump S-nail v14.9.20.ar ("Sombre Tit (Trauermeise)"), 2020-12-12
>   gpg: Signature made Sun 13 Dec 2020 12:43:44 AM CET
>   gpg:using RSA key DF082F6AEEC8C2FF
>   gpg: Good signature from "Steffen Nurpmeso "
>   0

TL;DR I don't see any reason for devs to sign commits.

I could see use for RE (or another entity) to occasionally (weekly?)
sign the repo (say COPYRIGHT or UPDATING), and it would be nice for
them to sign all the tags used for releases, but having every dev
would both make the dev's life difficult...

It's also hard to collect ALL the keys of the devs at any point in
time to decide if that key is authorized to sign a commit in the
repo...  Like if a dev starts in 2021, any commits made by that
dev prior to 2021 should not be "valid"..  Then there's also the
issue that people's keys change over time, and now you need to know
what time period each key was valid for, otherwise a compromised key
could be used to insert malicious changes into your/the tree...

Then there's also the point that the repo is (looks like it) using
SHA-1 hashes, which are effectively broken, so depending upon them
to validate the tree is questionable anyways.

-- 
  John-Mark Gurney  Voice: +1 415 225 5579

 "All that I will do, has been done, All that I have, has not."
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

src: continued use of Subversion for getting updates

[Graham Perrin]

On 23/12/2020 00:10, Paul Mather wrote:

… continue to get src updates via Subversion. …


As far as I can tell:

* for stable/12 alone

* for a limited period.



In context: 



___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: src: continued use of Subversion for getting updates

[Warner Losh]

On Tue, Dec 22, 2020, 11:47 PM Graham Perrin  wrote:

> On 23/12/2020 00:10, Paul Mather wrote:
> > … continue to get src updates via Subversion. …
>
> As far as I can tell:
>
> * for stable/12 alone
>

stable/11 as well as the releng branches for as long as the project has
them under support. I wrote the code to replay commits into subversion for
the convenience of our users on those branches. The 12.x releases will be
built out of Subversion to preserve $FreeBSD$ expansion and other obscure
subversion details that may matter or be disruptive to people using those
branches.

Current has moved entirely to git. New commits have started up again.
Stable/11 and stable/12 are there as well, but there are a couple of last
minute snags that are being sorted out so it will be an additional day,
maybe two before those start. FreeBSD 13 will be entirely from git and will
be branching late winter or early spring if all goes well. Other issues
with git are being sorted our as they arise.

For those using github, migration instructions will be in place once the
changes there are complete. What I've written up is enough for the seasoned
traveler, but lacks a few details that were hosted worked out in the past
days I've not had time to fold in. We hope to have that all sorted out by
Christmas.

This has been a big job with way more moving parts than I'd ever thought
possible. We've attended to most of them, and are fixing the stragglers as
the team becomes aware of them.

Warner

* for a limited period.
>
> <
> https://github.com/bsdimp/freebsd-git-docs/blob/4833066feda51cc3a907cf7bff1c4344b3edd5c6/big-picture.md#L103
> >
>
> In context:
> 
>
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
>
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"