Re: Deprecation of portsnap (was: Proposed ports git transition schedule)

[Michael Gmelin]

> On 14. Apr 2021, at 00:54, Dave Horsfall  wrote:
> 
> On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:
> 
>> Except that git will arbitrarily and randomly decide that it needs to run 
>> "gc" - which is similarly extravagant in memory usage.  Last time I found 
>> one running, it thrashed that poor VM for 3 days.
> Would this be a good time to mention the https://ohshitgit.com/ site? 
> Warning: it contains strong language...

I prefer this site: https://git-man-page-generator.lokaltog.net/

-m

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

Re: Deprecation of portsnap (was: Proposed ports git transition schedule)

[Dave Horsfall]

On Mon, 12 Apr 2021, Peter Jeremy via freebsd-ports wrote:

Except that git will arbitrarily and randomly decide that it needs to 
run "gc" - which is similarly extravagant in memory usage.  Last time I 
found one running, it thrashed that poor VM for 3 days.


Would this be a good time to mention the https://ohshitgit.com/ site? 
Warning: it contains strong language...


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

Re: Deprecation of portsnap (was: Proposed ports git transition schedule)

[Michael Gmelin]

> On 12. Apr 2021, at 13:12, Peter Jeremy via freebsd-ports 
>  wrote:
> 
> On 2021-Apr-11 14:27:27 +0200, Helge Oldach  wrote:
>> Peter Jeremy via freebsd-ports wrote on Sun, 11 Apr 2021 00:52:11 +0200 
>> (CEST):
>>> Following the SVN to GIT migration, portsnap is now the only practical
>>> way to use ports on a low-memory system.  I've done some experiments
>>> and standard git has a 2GB working set to checkout a ports tree.
>> 
>> However checking out is a one-time action with ports as there is only
>> one branch (switching frequently between main and quarterly is probably
>> not very sensible on a limited machine). git pull is significantly more
>> lightweight, I've just seen some 200M RSS. That should work well even on
>> a 512M machine. Probably much better than gitup in constrained memory?
> 
> Except that git will arbitrarily and randomly decide that it needs to
> run "gc" -

See https://git-scm.com/docs/git-gc for an explanation of how git decides when 
to run gc and how you can control it (e.g., by setting gc.auto to 0).

-m

> which is similarly extravagant in memory usage.  Last time
> I found one running, it thrashed that poor VM for 3 days.
> 
> Ignoring that, a "git up -ff" on a ports tree peaks with 2×1GB processes,
> though it looks like the working set size might only be ~350MB.
> 
> -- 
> Peter Jeremy
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Deprecation of portsnap (was: Proposed ports git transition schedule)

[Peter Jeremy via freebsd-ports]

On 2021-Apr-11 14:27:27 +0200, Helge Oldach  wrote:
>Peter Jeremy via freebsd-ports wrote on Sun, 11 Apr 2021 00:52:11 +0200 (CEST):
>> Following the SVN to GIT migration, portsnap is now the only practical
>> way to use ports on a low-memory system.  I've done some experiments
>> and standard git has a 2GB working set to checkout a ports tree.
>
>However checking out is a one-time action with ports as there is only
>one branch (switching frequently between main and quarterly is probably
>not very sensible on a limited machine). git pull is significantly more
>lightweight, I've just seen some 200M RSS. That should work well even on
>a 512M machine. Probably much better than gitup in constrained memory?

Except that git will arbitrarily and randomly decide that it needs to
run "gc" - which is similarly extravagant in memory usage.  Last time
I found one running, it thrashed that poor VM for 3 days.

Ignoring that, a "git up -ff" on a ports tree peaks with 2×1GB processes,
though it looks like the working set size might only be ~350MB.

-- 
Peter Jeremy


signature.asc
Description: PGP signature

Re: Deprecation of portsnap (was: Proposed ports git transition schedule)

[LuKreme]

On Apr 11, 2021, at 06:27, free...@oldach.net wrote:
> 
> However checking out is a one-time action with ports as there is only
> one branch

It sure looks like gitup is checking the entire port tree every single time. If 
I run it twice in a row it is no faster the second time.


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

Re: Deprecation of portsnap (was: Proposed ports git transition schedule)

[Peter Jeremy via freebsd-ports]

On 2021-Apr-01 12:19:08 +0200, Felix Palmen  wrote:
>* Christoph Moench-Tegeder  [20210326 19:45]:
>> ## Felix Palmen (fe...@palmen-it.de):
>> 
>> > I'd assume (someone may correct me) that portsnap will still be
>> > supported,
>> 
>> https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119098.html
>
>Is this finally decided, and is there a timeline? Right now, it seems
>portsnap is still built by default on releng/13.0.

Following the SVN to GIT migration, portsnap is now the only practical
way to use ports on a low-memory system.  I've done some experiments
and standard git has a 2GB working set to checkout a ports tree.
gitup reached a 5GB working set size before I gave up.  Typical small
VPSs are around the 1GB RAM size and moving to something that can
support 2GB or 5GB processes is a big price jump.

-- 
Peter Jeremy


signature.asc
Description: PGP signature

Re: Proposed ports git transition schedule

[Kevin Oberman]

On Fri, Apr 2, 2021 at 7:36 AM Michael Gmelin  wrote:

>
>
> On 2. Apr 2021, at 16:27, Kevin Oberman  wrote:
>
> On Fri, Apr 2, 2021 at 4:53 AM Robert Huff  wrote:
>
>
>The transition has happened.
>
>Where do I find the authoritative guide for non-committers?
>
>
>
>Respectfully,
>
>
>
>Robert Huff
>
>
> --
>
> Hello ... my name is SARS-CoV-2.
>
> You are not wearing a mask?
>
> Prepare to die!
>
>
> And where do I find the repository? I look at https://cgit.freebsd.org and
> see only doc and src. Is there a delay in the move of the repo? Or, am I
> looking in the wrong place?
>
>
> According to https://wiki.freebsd.org/git the final run of subversion-git
> conversion hasn’t started yet (was planned for yesterday). So I guess we
> just have to be patient.
>
> -m
>
Thanks! I suspect I've seen pointers to that wiki page as it looks very
familiar, but forgot about it since the src conversion.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Proposed ports git transition schedule

[Michael Gmelin]

> On 2. Apr 2021, at 16:27, Kevin Oberman  wrote:
> 
> On Fri, Apr 2, 2021 at 4:53 AM Robert Huff  wrote:
> 
>> 
>>The transition has happened.
>>Where do I find the authoritative guide for non-committers?
>> 
>> 
>>Respectfully,
>> 
>> 
>>Robert Huff
>> 
>> --
>> Hello ... my name is SARS-CoV-2.
>> You are not wearing a mask?
>> Prepare to die!
>> 
> And where do I find the repository? I look at https://cgit.freebsd.org and
> see only doc and src. Is there a delay in the move of the repo? Or, am I
> looking in the wrong place?

According to https://wiki.freebsd.org/git the final run of subversion-git 
conversion hasn’t started yet (was planned for yesterday). So I guess we just 
have to be patient.

-m



> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
> ___
> freebsd-ports@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Proposed ports git transition schedule

[Baptiste Daroussin]

On Fri, Apr 02, 2021 at 07:26:42AM -0700, Kevin Oberman wrote:
> On Fri, Apr 2, 2021 at 4:53 AM Robert Huff  wrote:
> 
> >
> > The transition has happened.
> > Where do I find the authoritative guide for non-committers?
> >
> >
> > Respectfully,
> >
> >
> > Robert Huff
> >
> > --
> > Hello ... my name is SARS-CoV-2.
> > You are not wearing a mask?
> > Prepare to die!
> >
> And where do I find the repository? I look at https://cgit.freebsd.org and
> see only doc and src. Is there a delay in the move of the repo? Or, am I
> looking in the wrong place?

Conversion of such big repos takes time + all the verification to ensure the
migration went correctly, so yes, it will take time, but will appear there.

Bapt


signature.asc
Description: PGP signature

Re: Proposed ports git transition schedule

[Kevin Oberman]

On Fri, Apr 2, 2021 at 4:53 AM Robert Huff  wrote:

>
> The transition has happened.
> Where do I find the authoritative guide for non-committers?
>
>
> Respectfully,
>
>
> Robert Huff
>
> --
> Hello ... my name is SARS-CoV-2.
> You are not wearing a mask?
> Prepare to die!
>
And where do I find the repository? I look at https://cgit.freebsd.org and
see only doc and src. Is there a delay in the move of the repo? Or, am I
looking in the wrong place?
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Proposed ports git transition schedule

[Robert Huff]

The transition has happened.
Where do I find the authoritative guide for non-committers?


Respectfully,


Robert Huff

-- 
Hello ... my name is SARS-CoV-2.
You are not wearing a mask?
Prepare to die!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Deprecation of portsnap (was: Proposed ports git transition schedule)

[@lbutlr]

On 01 Apr 2021, at 04:19, Felix Palmen  wrote:
> * Christoph Moench-Tegeder  [20210326 19:45]:
>> ## Felix Palmen (fe...@palmen-it.de):
>>> I'd assume (someone may correct me) that portsnap will still be
>>> supported,

>> https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119098.html

> Is this finally decided, and is there a timeline?

That post I read as the official decision that port snap was going to die. But  
WITHOUT_PORTSANP added to the default base would be the single, I'd think. Most 
of the ground work has already been done.

> portsnap is still built by default on releng/13.0.

We'll see if it makes it to RELEASE or not.

gitup is working well right now, but it looks more fiddly and I wish the 'fake 
JSON' configuration file was actual valid JSON, OTOH, it seems o run a lot 
faster than portsnap.


-- 
I WILL NOT TRADE PANTS WITH OTHERS Bart chalkboard Ep. 7F05

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

Deprecation of portsnap (was: Proposed ports git transition schedule)

[Felix Palmen]

Hallo Christoph,

* Christoph Moench-Tegeder  [20210326 19:45]:
> ## Felix Palmen (fe...@palmen-it.de):
> 
> > I'd assume (someone may correct me) that portsnap will still be
> > supported,
> 
> https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119098.html

Is this finally decided, and is there a timeline? Right now, it seems
portsnap is still built by default on releng/13.0.

-- 
 Dipl.-Inform. Felix Palmen ,.//..
 {web}  http://palmen-it.de  {jabber} [see email]   ,//palmen-it.de
 {pgp public key} http://palmen-it.de/pub.txt   //   """
 {pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A


signature.asc
Description: PGP signature

Re: Proposed ports git transition schedule

[@lbutlr]

On 27 Mar 2021, at 08:20, Felix Palmen  wrote:
> I'm talking about net/gitup, which is a little C program with
> *no* dependencies and definitely no python involved. If you don't have
> it in your ports tree, upgrade your ports tree.

Just for clarity sakes, running gitup ports wight now would replace running 
portsnap?

But we should update it to point to a different server at some point in the 
future?

Would I be safe in removing the stable and current blocks from the gitup.conf 
file since I will never use those?

Might I suggest that -v should mean -v 1 and -vv should mean -v 2? As it is, -v 
means -v 0 and that seems odd?

There's no cron flag, so does this mean we do not need to be concerned with 
when the process runs? Is it safe to run it more than once a day? I mean, I 
doubt GitHub cares at this point, but looking forward…

-- 
A bad day using a Mac is better than a good day using Windows

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

Re: Proposed ports git transition schedule

[Felix Palmen]

* Bob Eager  [20210327 16:01]:
> Thanks - that looks like a nice simple way of replacing the portsnap
> functionality (while avoiding its pitfalls).

Right now, the default configuration uses the mirror repo from github
because the official repo isn't there yet. You might want to change the
configuration once migration is complete.

> I feel it ought to be in base soon, though.

I think *something* will come to base eventually. gitup might be an
interesting candidate…

-- 
 Dipl.-Inform. Felix Palmen ,.//..
 {web}  http://palmen-it.de  {jabber} [see email]   ,//palmen-it.de
 {pgp public key} http://palmen-it.de/pub.txt   //   """
 {pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A


signature.asc
Description: PGP signature

Re: Proposed ports git transition schedule

[Bob Eager]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sat, 27 Mar 2021 15:20:33 +0100
Felix Palmen  wrote:

> * Bob Eager  [20210327 14:14]:
> > I looked for gitup, and it's moved to py37-git-up (unless something
> > replaced it, but nothing in devel/).  
> 
> That's an entirely different software which has nothing to do with
> gitup. I'm talking about net/gitup, which is a little C program with
> *no* dependencies and definitely no python involved. If you don't have
> it in your ports tree, upgrade your ports tree.
> 

Thanks. I thought that might be the case, but I only just got back to
the keyboard. I was looking on a system that wasn't up to date, and
when I checked on one that was, it was there OK.

Thanks - that looks like a nice simple way of replacing the portsnap
functionality (while avoiding its pitfalls).

I feel it ought to be in base soon, though.

And thanks for your patience!
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEVgdI2KeVldPAhUYaKBdf2az8e6gFAmBfVr8ACgkQKBdf2az8
e6gfrwgAiS0UqsP48wbKY3DLtcz6pZwTQ1VOD3ly1G/njbmJVon+9AjNMW9LKntT
h8PfphWjpTslvbYewsjb3ZtyufK61VLas5WnV/03s9ZSLwFJXgyVbQYMRtQ4Jnti
LnSS0KHDa+l8h+NxCOq4qlTaBq/cbO1zj3AwyIPZRXtMkzyJaX7Gg3wPWVWkSMkl
PcqeOH3M/utY+7WZsvnswtqXvlRGYgxVrv+UpZKF0DryYDeUE1PeDTZ2IqcVyPvs
VsNUEun2ul+lvZal28CD7ILvQ2PQ9/DW8GXmoZOz1YpSQX7lw7qQGLC1tFUX7dR/
ebQzeuCd9tvAAR7iUlau+2pxrzVamg==
=QSYD
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Proposed ports git transition schedule

[jaap . akkerhuis]

> On Mar 27, 2021, at 0:19, Felix Palmen  > wrote:
> 
>> No, that's not what I'm asking. I'm asking (on behalf of many people,
>> I'm sure) just what I have to enter instead of:
>> 
>>  $ portsnap fetch extract
> 
> $ gitup ports

I just did the following

mv ports old.ports  # just in case
mkdir ports
gitup ports

and it seemed to work fine.

jaap



signature.asc
Description: Message signed with OpenPGP

Re: Proposed ports git transition schedule

[George Mitchell]

On 3/27/21 10:20 AM, Felix Palmen wrote:

[...]  I'm talking about net/gitup, which is a little C program with
*no* dependencies and definitely no python involved. If you don't have
it in your ports tree, upgrade your ports tree.


-- while you still can, with the existing tools ...-- George




OpenPGP_signature
Description: OpenPGP digital signature

Re: Proposed ports git transition schedule

[Felix Palmen]

* Bob Eager  [20210327 14:14]:
> I looked for gitup, and it's moved to py37-git-up (unless something
> replaced it, but nothing in devel/).

That's an entirely different software which has nothing to do with
gitup. I'm talking about net/gitup, which is a little C program with
*no* dependencies and definitely no python involved. If you don't have
it in your ports tree, upgrade your ports tree.

-- 
 Dipl.-Inform. Felix Palmen ,.//..
 {web}  http://palmen-it.de  {jabber} [see email]   ,//palmen-it.de
 {pgp public key} http://palmen-it.de/pub.txt   //   """
 {pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A


signature.asc
Description: PGP signature

Re: Proposed ports git transition schedule

[Bob Eager]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Sat, 27 Mar 2021 00:19:55 +0100
Felix Palmen  wrote:

> > With portsnap, I don't need a URL. It's built in. And that would be
> > nice.  
> 
> Ever had a look in /etc/portsnap.conf? Although it only wants a server
> name (well, much of a difference), there's nothing built in.

OK, it's there by default anyway.

> gitup comes with a working configuration as well.

See below.

> > No, that's not what I'm asking. I'm asking (on behalf of many
> > people, I'm sure) just what I have to enter instead of:
> > 
> >   $ portsnap fetch extract  
> 
> $ gitup ports

I'm not trying to be awkward, but just trying to get it going!

I looked for gitup, and it's moved to py37-git-up (unless something
replaced it, but nothing in devel/).

I installed it (and git), and there is zero documentation. I also can't
see any working configuration file.

I tried as you suggest:

- 
root@test:/ # git-up ports
Usage: git-up [OPTIONS]
Try "git-up --help" for help.

Error: Got unexpected extra argument (ports)
root@test:/ # exit
exit
- 

Am I looking at the wrong thing?



-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEVgdI2KeVldPAhUYaKBdf2az8e6gFAmBfPeIACgkQKBdf2az8
e6j9Ewf9HMPaz+8sSsSMGalHAzMFWhd5ePDqJXIhQ61DteIzSIuj35KEZtI3aGo3
RcRU7YaBi4sca8GHTG/uxpj2e+q/zzg3f8eZpoWfKPD7WAFTP5cJ/RyBXwAIdEjw
IfZi3ZFpZ0RwKBPyrUCocZqD6IVaaO9sIdzPY8WLPsUMFzYcSoRSqJaPdmvWpmR7
j/4gJd6n2NMHndM1J8eVPK2AdcuaOJ0yxOLcb+ZaxegCgys43RxvMs4zYarTadJl
g+2tMP2W2x+5dmSfGR8TCscvp3jwO6iGHjc1S4BI1rhNDOKB2pA1HxdB8aS3JQp5
aMcltOAhZ2vhf7VdAVUlvm6pIC//IA==
=omJW
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Proposed ports git transition schedule

[Felix Palmen]

* Bob Eager  [20210326 20:22]:
> Felix Palmen  wrote:
> > I don't get what you mean. Repo details? A URL.
> 
> With portsnap, I don't need a URL. It's built in. And that would be
> nice.

Ever had a look in /etc/portsnap.conf? Although it only wants a server
name (well, much of a difference), there's nothing built in. gitup comes
with a working configuration as well.

> > And that's all it does, it doesn't do any "security checks", that's
> > handled by pkg audit.
> 
> What does it need a public key for?

Checking integrity of the downloaded snapshots? With fetching from
repositories, integrity checks are built in.

> No, that's not what I'm asking. I'm asking (on behalf of many people,
> I'm sure) just what I have to enter instead of:
> 
>   $ portsnap fetch extract

$ gitup ports

-- 
 Dipl.-Inform. Felix Palmen ,.//..
 {web}  http://palmen-it.de  {jabber} [see email]   ,//palmen-it.de
 {pgp public key} http://palmen-it.de/pub.txt   //   """
 {pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A


signature.asc
Description: PGP signature

Re: Proposed ports git transition schedule

[Bob Eager]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, 26 Mar 2021 19:30:03 +0100
Felix Palmen  wrote:

> * Bob Eager  [20210326 14:27]:
> > On Fri, 26 Mar 2021 14:04:17 +0100
> > Felix Palmen  wrote:  
> > > I never used portsnap, but I'd assume net/gitup should serve the
> > > same usecase.
> > >   
> > 
> > Probably. So would git.  
> 
> Only that net/gitup is very lightweight and doesn't use git, so if you
> want to just get the latest contents of a git repository, that's
> probably what you want to use.
> 
> > But portsnap needs no more at all than the above. All of the rest
> > (repo details, security checks, etc.) are all done internally.  
> 
> I don't get what you mean. Repo details? A URL.

With portsnap, I don't need a URL. It's built in. And that would be
nice.

> There's example
> configurations containing the correct ones, just like portsnap has a
> server configured where to fetch snapshots from.

I'm sure there are.

> And that's all it does, it doesn't do any "security checks", that's
> handled by pkg audit.

What does it need a public key for?

> I'd assume (someone may correct me) that portsnap will still be
> supported, as the snapshots don't depend on svn or git. But as you
> asked for a replacement for git, gitup comes to mind as a simple tool.

No, that's not what I'm asking. I'm asking (on behalf of many people,
I'm sure) just what I have to enter instead of:

  $ portsnap fetch extract

It's probably more than one command, and/or longer. I just thought it
would be useful if everyone was told exactly what to use.
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEVgdI2KeVldPAhUYaKBdf2az8e6gFAmBeQpAACgkQKBdf2az8
e6gDbggAwVs+WOBaqO2jN4yBMyF486bQOW8jV2QS9EBBjauSoIi5wkeZj/1ep0R6
xwFIGbLe4x0SkdKzWG+D/8rIgW89luVAQK7dWw2Ag61RbQANSCmjcZNSfdnWb0fY
b63tkAB5JqnohBJg9VHy7QQEOpVTof5iig06ShvDojUJo2MxzC1slYeXDDuIm91E
PQ2KsuLVuh4uGokAPec5mXUAKef+PS+4k3GWP47u7+7bsNhECjlO0B2Kv5EbkW8t
e2UL/JEAc+W813uKuesP1XJaQg3BlOiyIGVung8BrT+P84yhS9lIFrBKSPu5XBxk
y1wdcGA76Z+q8VPDborIdMHx18m8sA==
=3pXs
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Proposed ports git transition schedule

[Christoph Moench-Tegeder]

## Felix Palmen (fe...@palmen-it.de):

> I'd assume (someone may correct me) that portsnap will still be
> supported,

https://lists.freebsd.org/pipermail/freebsd-ports/2020-August/119098.html

Regards,
Christoph

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

Re: Proposed ports git transition schedule

[Felix Palmen]

* Bob Eager  [20210326 14:27]:
> On Fri, 26 Mar 2021 14:04:17 +0100
> Felix Palmen  wrote:
> > I never used portsnap, but I'd assume net/gitup should serve the same
> > usecase.
> > 
> 
> Probably. So would git.

Only that net/gitup is very lightweight and doesn't use git, so if you
want to just get the latest contents of a git repository, that's
probably what you want to use.

> But portsnap needs no more at all than the above. All of the rest (repo
> details, security checks, etc.) are all done internally.

I don't get what you mean. Repo details? A URL. There's example
configurations containing the correct ones, just like portsnap has a
server configured where to fetch snapshots from.

And that's all it does, it doesn't do any "security checks", that's
handled by pkg audit.

I'd assume (someone may correct me) that portsnap will still be
supported, as the snapshots don't depend on svn or git. But as you asked
for a replacement for git, gitup comes to mind as a simple tool.

-- 
 Dipl.-Inform. Felix Palmen ,.//..
 {web}  http://palmen-it.de  {jabber} [see email]   ,//palmen-it.de
 {pgp public key} http://palmen-it.de/pub.txt   //   """
 {pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A


signature.asc
Description: PGP signature

Re: Proposed ports git transition schedule

[Bob Eager]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Fri, 26 Mar 2021 14:04:17 +0100
Felix Palmen  wrote:

> * Bob Eager  [20210326 09:22]:
> > Thanks for this. The documentation (although introductory) is quite
> > detailed. What would be useful is just to note down the exact
> > replacement for:
> > 
> >   portsnap fetch
> >   portsnap extract  
> 
> I never used portsnap, but I'd assume net/gitup should serve the same
> usecase.
> 

Probably. So would git.

But portsnap needs no more at all than the above. All of the rest (repo
details, security checks, etc.) are all done internally.
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEVgdI2KeVldPAhUYaKBdf2az8e6gFAmBd7z8ACgkQKBdf2az8
e6huSQf+P1l9gMFuqk93s0jkx8939g3jCl6fIHEePkF/H3pxbd9Ivmr7XCateIjs
deMJPaRC1kPqhJymh5vsjRBoTAxckMBkCASYaaqrLEC1stl+UyduyDhdmxDcqTRq
49Ehdagfq9bBK+2Qz3+RxNN8iuqaK88ZxjUQF0YIRblJG9CKUdyn0DC1/nMsiqLS
fGG2mwS0atXSfzybORdCNTrQ+SGJKSvPJ/lcnWbnPpQ8yl/uLeWAGezFRHa1hvg+
xZSJ/oszVQD+rfdYjYNdp3JrJfuKEgvljG7rIvc/ExdUH9BtAwUEm+oA7oy33G06
nQZO4RMtZYCUoxoEf+zSgrP77GSA/Q==
=jHnH
-END PGP SIGNATURE-
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Proposed ports git transition schedule

[Felix Palmen]

* Bob Eager  [20210326 09:22]:
> Thanks for this. The documentation (although introductory) is quite
> detailed. What would be useful is just to note down the exact
> replacement for:
> 
>   portsnap fetch
>   portsnap extract

I never used portsnap, but I'd assume net/gitup should serve the same
usecase.

-- 
 Dipl.-Inform. Felix Palmen ,.//..
 {web}  http://palmen-it.de  {jabber} [see email]   ,//palmen-it.de
 {pgp public key} http://palmen-it.de/pub.txt   //   """
 {pgp fingerprint} A891 3D55 5F2E 3A74 3965 B997 3EF2 8B0A BC02 DA2A


signature.asc
Description: PGP signature

Re: Proposed ports git transition schedule

[Bob Eager]

On Thu, 25 Mar 2021 21:56:03 -0400
Ed Maste  wrote:

> When the conversion is complete, Subversion will become read-only with
> no further updates to the ports tree. If you are fetching ports using
> svn, you will need to switch to the new git repository at the
> following URLS:
> 
> Web repository browser:
> https://cgit.freebsd.org/ports/
> 
> Distributed mirrors for anonymous readonly checkout/clone
> https://git.freebsd.org/ports.git
> ssh://anon...@git.freebsd.org/ports.git

Thanks for this. The documentation (although introductory) is quite
detailed. What would be useful is just to note down the exact
replacement for:

  portsnap fetch
  portsnap extract

when the migration is complete. A shell script would be even better!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Proposed ports git transition schedule

[Ed Maste]

The doc and src tree git migrations are complete, and the git working
group is preparing the ports tree transition in advance of the 2021Q2
quarterly branch.

The proposed schedule is available at https://wiki.freebsd.org/git and
the status will be updated throughout the process, and important
milestones will be sent here as well.

The committer's guide has been updated with Git documentation, at
https://docs.freebsd.org/en/articles/committers-guide/#git-primer.
Some additional draft / in-progress notes are available in Warner's
repo at https://github.com/bsdimp/freebsd-git-docs/, and additional
documentation will be updated over the next few days.

When the conversion is complete, Subversion will become read-only with
no further updates to the ports tree. If you are fetching ports using
svn, you will need to switch to the new git repository at the
following URLS:

Web repository browser:
https://cgit.freebsd.org/ports/

Distributed mirrors for anonymous readonly checkout/clone
https://git.freebsd.org/ports.git
ssh://anon...@git.freebsd.org/ports.git

Read/write Repository for committers
ssh://g...@gitrepo.freebsd.org/ports.git

We will be monitoring #gitcvt on EFnet (irc.efnet.org) and #git on the
unofficial FreeBSD Discord server (https://discord.gg/WKEKSPtJGp)
during and after the cutover.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"