I've been running gentoo for years now, and every time I go to --sync,
it's really a painful process.

The process can take *very* before you find out if it succeeded or not.

I try different repos.conf servers - one works for a while, then
doesn't, then later, the new one doesn't work anymore and the old one
works again.

I've asked here about it multiple times and get the answers

- "I don't have a problem"

- "just change the server"

- "keep trying"

It can take several hours before it finally works

It seems like a time-out problem.  Or maybe a memory problem ... In any
case, it doesn't seem like it ought to be difficult to at least know
what the problem is.

Or?

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

n952162 wrote:

I've been running gentoo for years now, and every time I go to --sync,
it's really a painful process.

The process can take *very* before you find out if it succeeded or not.

I try different repos.conf servers - one works for a while, then
doesn't, then later, the new one doesn't work anymore and the old one
works again.

I've asked here about it multiple times and get the answers

- "I don't have a problem"

- "just change the server"

- "keep trying"

It can take several hours before it finally works

It seems like a time-out problem.  Or maybe a memory problem ... In any case, it doesn't seem like it ought to be difficult to at least know
what the problem is.

Or?

This wiki page and mirrorselect may help.

https://wiki.gentoo.org/wiki/Mirrorselect

I think this is the command I use to get the best server to sync with. 
You may want to make a backup of make.conf first, just in case.

mirrorselect -D -s4

One of those should help some unless you have a internet connection
problem.  If you have problems with multiple servers, it could be a
connection problem and you may figure that out.  It tests by downloading
a file.  If it fails on most or all servers, connection problem.  If it
works on most, just a bad server(s) most likely. 

Hope that helps.

Dale

:-)  :-) 

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 7/31/22 15:51, n952162 wrote:

I've been running gentoo for years now, and every time I go to --sync,
it's really a painful process.

The process can take *very* before you find out if it succeeded or not.

I try different repos.conf servers - one works for a while, then
doesn't, then later, the new one doesn't work anymore and the old one
works again.

I've asked here about it multiple times and get the answers

- "I don't have a problem"

- "just change the server"

- "keep trying"

It can take several hours before it finally works

It seems like a time-out problem.  Or maybe a memory problem ... In any case, it doesn't seem like it ought to be difficult to at least know
what the problem is.

Or?

Well, since "it works for me" I can only suggest some things to think of
and to try.  While a memory problem is possible, if it is timing out,
I'd look at a possible network problem.

First, as you talk about repos.conf, is your issue with the main portage
repo or some overlay?  Second, for the problem (or just pick one if it
happens with several) server, can you ping that server without
problems?  Third (maybe should have been first) what is your sync method
and what is GENTOO_MIRRORS in your make.conf?  Related to that last one,
have you run mirrorselect recently?

No solution, I know, but maybe something to trigger a useful thought.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sun, 31 Jul 2022 21:51:05 +0200, n952162 wrote:

I've been running gentoo for years now, and every time I go to --sync,
it's really a painful process.

The process can take *very* before you find out if it succeeded or not.

I try different repos.conf servers - one works for a while, then
doesn't, then later, the new one doesn't work anymore and the old one
works again.

I switched to using git for syncing, from github, and haven't looked
back. It is *much* faster, several times faster syncing from github than
using rsync to sync from a local mirror, and github is always there.

% cat /etc/portage/repos.conf/gentoo.conf
[DEFAULT]
main-repo = gentoo

[gentoo]
priority = 20
location = /var/portage
sync-type = git
sync-uri = https://github.com/gentoo-mirror/gentoo
auto-sync = yes


--
Neil Bothwick

Cereal Killer Strikes Again! Cap'n Crunch found dead...

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmLm6WAACgkQ92eFu0QS MJhVnBAAubsKQ1lncuowU7ShQEdJJUVig/70DiV1Q1FQIyud6hiC2a8lZd0+NlqW auZQgZj7QJ+O3YdgBTP2DdQSkbno0jMM42u8oqpqJvlaYcwCH2nCJLUx15IKLZUU myXT644T9ZLUDyvD4CWiPlgew4U1dsaRf6Gfb6X1Twh7E7EVFPPCSfennNRsDk47 oWsn2nTUTVHXj2Pkehd5r18H6W/S7T/j3F+23yHrSf4mJLPwiEUFqOxYDbK1arbN Ro14OcyGVVDRBfhRucbBi0hkoEy0mU2x+eYWdFm16sMEqtOCwJ6hzupKVkHhTwCQ goFBddfRKd2F2DYMzTpPxF5mWgfrE/UVkJMDqXBxmBT1SQES92bx5hWdTFTSFSJd fMJCo5I0i9Jcyhbm23CV6fcGyUpS+1o3nlz0yg4EHZvBKiXIhdJvAsUXxylArHj6 cgt1PXTko7W+fELBYfJ+A0IHX/0iE/zrbIFXFYQrVZZMZqvQAoCA5JM/4yRsT1do cXJ4aXf6LtGPaDao7orxPaw9Txflwx378TURLl112pVl8ZybQrBKJAcuwusJigvp 6xats8pX9APE+iXU3AsYAHC5R1mMkZGLEuzxyf4zKoTaIrI99/70s3jT9NY171UX H0vRgn+P8W+G5KYtVoxH8A6Jdh21VV9VT+ykznKJSWLx8z5ghf4=
=fB23
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Sonntag, 31. Juli 2022 21:51:
 

I've been running gentoo for years now, and every time I go to --sync,
it's really a painful process.

The process can take *very* [long] before you find out if it succeeded or not.

...

It can take several hours before it finally works

 
Use a tool like atop to get some info about the throughput
of your network connection. Something like "ss -ntp" might
show interesting info about the state of the connection 
between your machine and the server, too.
 
You might have problems with DNS name resolution or your
box patiently trying to establish an IPv6 connection when
your internet connection is IPv4 only.
 
But switching to git, like Neil said, does make things faster.
 
FWIW, my config file reads like this:
 
# cat /etc/portage/repos.conf/gentoo.conf
[DEFAULT]
main-repo = gentoo

[gentoo]
location = /var/db/repos/gentoo
sync-type = git
sync-uri = https://github.com/gentoo-mirror/gentoo.git
auto-sync = yes
sync-git-verify-commit-signature = yes
sync-openpgp-key-path = /usr/share/openpgp-keys/gentoo-release.asc
 
good luck,
s.

It seems like a time-out problem.  Or maybe a memory problem ... In any case, it doesn't seem like it ought to be difficult to at least know
what the problem is.

Or?

<html><head> <style type="text/css" title="rt_noDelete">
blockquote.rt {
margin: 0 0 15px;
border-left: 4px solid #81c784;
padding: 0 0 0 12px;
display: block;
}
p { margin: 0 0 0 0 }
.email-signature {font-family:"Arial Narrow"; font-size: 10pt; font-style: italic; font-weight: normal; text-decoration: none; }
</style><STYLE type="text/css" title="rt">BODY {margin: 10; font-family:"Consolas"; font-size: 11pt; color: #000000}
P {margin: 0; font-family:"Consolas"; font-size: 11pt; color: #000000} PRE.RFCheader {font-family:"Consolas"; font-size: 10pt; color: #B73A67} .email-signature { color: #969696; font-style: italic;font-weight: normal;text-decoration: none }
A {color: #0066CC; link: #0066CC; font-style: normal;font-weight: normal;text-decoration: underline }
BLOCKQUOTE.Odd {font-family:"Consolas"; font-size: 10pt; color: #9AA626; font-style: italic;font-weight: bold;text-decoration: none }
BLOCKQUOTE.Even {font-family:"Consolas"; font-size: 10pt; color: #50AF4C; font-style: italic;font-weight: bold;text-decoration: none }
.QOdd {font-family:"Consolas"; font-size: 10pt; color: #9AA626; font-style: normal;font-weight: normal;text-decoration: none }
.QEven {font-family:"Consolas"; font-size: 10pt; color: #50AF4C; font-style: normal;font-weight: normal;text-decoration: none }
PRE {font-family:"Consolas"; font-size: 11pt; font-style: normal;font-weight: normal;text-decoration: none }
BODY {background-color: #FFFFFF}
</STYLE></head><body><xhtml><head> <style title="rt_noDelete" type="text/css">
blockquote.rt {
margin: 0 0 15px;
border-left: 4px solid #81c784;
padding: 0 0 0 12px;
display: block;
}
p { margin: 0 0 0 0 }
.email-signature {font-family:"Arial Narrow"; font-size: 10pt; font-style: italic; font-weight: normal; text-decoration: none; }
</style><style title="rt" type="text/css">BODY {margin: 10; font-family:"Consolas"; font-size: 11pt; color: #000000}
P {margin: 0; font-family:"Consolas"; font-size: 11pt; color: #000000} PRE.RFCheader {font-family:"Consolas"; font-size: 10pt; color: #B73A67} .email-signature { color: #969696; font-style: italic;font-weight: normal;text-decoration: none }
A {color: #0066CC; link: #0066CC; font-style: normal;font-weight: normal;text-decoration: underline }
BLOCKQUOTE.Odd {font-family:"Consolas"; font-size: 10pt; color: #9AA626; font-style: italic;font-weight: bold;text-decoration: none }
BLOCKQUOTE.Even {font-family:"Consolas"; font-size: 10pt; color: #50AF4C; font-style: italic;font-weight: bold;text-decoration: none }
.QOdd {font-family:"Consolas"; font-size: 10pt; color: #9AA626; font-style: normal;font-weight: normal;text-decoration: none }
.QEven {font-family:"Consolas"; font-size: 10pt; color: #50AF4C; font-style: normal;font-weight: normal;text-decoration: none }
PRE {font-family:"Consolas"; font-size: 11pt; font-style: normal;font-weight: normal;text-decoration: none }
BODY {background-color: #FFFFFF}
</style></head><body>
<p></p><p>Sonntag, 31. Juli 2022 21:51:<br/></p><p>&nbsp;</p><p><xhtml><head> <style title="rt_noDelete" type="text/css">
blockquote.rt {
margin: 0 0 15px;
border-left: 4px solid #81c784;
padding: 0 0 0 12px;
display: block;
}
p { margin: 0 0 0 0 }
.email-signature {font-family:"Arial Narrow"; font-size: 10pt; font-style: italic; font-weight: normal; text-decoration: none; }
</style><style title="rt" type="text/css">BODY {margin: 10; font-family:"Consolas"; font-size: 11pt; color: #000000}
P {margin: 0; font-family:"Consolas"; font-size: 11pt; color: #000000} PRE.RFCheader {font-family:"Consolas"; font-size: 10pt; color: #B73A67} .email-signature { color: #969696; font-style: italic;font-weight: normal;text-decoration: none }
A {color: #0066CC; link: #0066CC; font-style: normal;font-weight: normal;text-decoration: underline }
BLOCKQUOTE.Odd {font-family:"Consolas"; font-size: 10pt; color: #9AA626; font-style: italic;font-weight: bold;text-decoration: none }
BLOCKQUOTE.Even {font-family:"Consolas"; font-size: 10pt; color: #50AF4C; font-style: italic;font-weight: bold;text-decoration: none }
.QOdd {font-family:"Consolas"; font-size: 10pt; color: #9AA626; font-style: normal;font-weight: normal;text-decoration: none }
.QEven {font-family:"Consolas"; font-size: 10pt; color: #50AF4C; font-style: normal;font-weight: normal;text-decoration: none }
PRE {font-family:"Consolas"; font-size: 11pt; font-style: normal;font-weight: normal;text-decoration: none }
BODY {background-color: #FFFFFF} </style></head><xbody></xbody></xhtml></p><blockquote class="Odd QOdd rt" prefix="&gt;&nbsp;">I've been running gentoo for years now, and every time I go to --sync,<br/>
it's really a painful process.</blockquote><p class="norm"><br/></p><blockquote class="Odd QOdd rt" prefix="&gt;&nbsp;">The process can take *very* [long] before you find out if it succeeded or not.</blockquote><p class="norm">...<br/></p><p class="norm">
<br/></p><blockquote class="Odd QOdd rt" prefix="&gt;&nbsp;">It can take several hours before it finally works</blockquote></body></xhtml><p>&nbsp;</p><p>Use a tool like atop to get some info about the throughput</p><p>of your network connection.
Something like "ss -ntp" might</p><p>show interesting info about the state of the connection&nbsp;</p><p>between your machine and the server, too.</p><p>&nbsp;</p><p>You might have problems with DNS name resolution or your</p><p>box patiently trying to
establish an IPv6 connection when</p><p>your internet connection is IPv4 only.</p><p>&nbsp;</p><p>But switching to git, like Neil said, does make things faster.</p><p>&nbsp;</p><p>FWIW, my config file reads like this:</p><p>&nbsp;</p><p># cat /etc/
portage/repos.conf/gentoo.conf
</p><p>[DEFAULT]</p>
<p>main-repo = gentoo</p>
<p><br/></p>
<p>[gentoo]</p>
<p>location = /var/db/repos/gentoo</p>
<p>sync-type = git</p>
<p>sync-uri =&nbsp;<a href="https://github.com/gentoo-mirror/gentoo.git">https://github.com/gentoo-mirror/gentoo.git</a></p>
<p>auto-sync = yes</p>
<p>sync-git-verify-commit-signature = yes</p>
<p>sync-openpgp-key-path = /usr/share/openpgp-keys/gentoo-release.asc</p><p>&nbsp;</p><p>good luck,</p><p>s.</p><xhtml><body><blockquote class="Odd QOdd rt" prefix="&gt;&nbsp;"></blockquote><p class="norm"><br/></p><blockquote class="Odd QOdd rt" prefix="
&gt;&nbsp;">It seems like a time-out problem.&nbsp; Or maybe a memory problem ... In any<br/>
case, it doesn't seem like it ought to be difficult to at least know<br/>
what the problem is.</blockquote><p class="norm"><br/></p><blockquote class="Odd QOdd rt" prefix="&gt;&nbsp;">Or?</blockquote><p class="norm"><br/></p><p class="norm"><br/></p></body></xhtml><br/><br/>
</body>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Had a similar issue to the OP, and it turned out to be a flaky internet connection. I switched ISP's and, while sync's still take longer than I'd
like, I don't have the failures, time outs I did before.

On Sun, Jul 31, 2022 at 1:54 PM Stefan Schmiedl <s@xss.de> wrote:

Sonntag, 31. Juli 2022 21:51:

I've been running gentoo for years now, and every time I go to --sync,
it's really a painful process.

The process can take *very* [long] before you find out if it succeeded or not.

...

It can take several hours before it finally works

Use a tool like atop to get some info about the throughput

of your network connection. Something like "ss -ntp" might

show interesting info about the state of the connection

between your machine and the server, too.

You might have problems with DNS name resolution or your

box patiently trying to establish an IPv6 connection when

your internet connection is IPv4 only.

But switching to git, like Neil said, does make things faster.

FWIW, my config file reads like this:

# cat /etc/portage/repos.conf/gentoo.conf

[DEFAULT]

main-repo = gentoo

[gentoo]

location = /var/db/repos/gentoo

sync-type = git

sync-uri = https://github.com/gentoo-mirror/gentoo.git

auto-sync = yes

sync-git-verify-commit-signature = yes

sync-openpgp-key-path = /usr/share/openpgp-keys/gentoo-release.asc

good luck,

s.

It seems like a time-out problem. Or maybe a memory problem ... In any
case, it doesn't seem like it ought to be difficult to at least know
what the problem is.

Or?

--
Lee 😎
<ny6p01@gmail.com>

<div dir="ltr">Had a similar issue to the OP, and it turned out to be a flaky internet connection. I switched ISP&#39;s and, while sync&#39;s still take longer than I&#39;d like, I don&#39;t have the failures, time outs I did before.</div><br><div class="
gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jul 31, 2022 at 1:54 PM Stefan Schmiedl &lt;<a href="mailto:s@xss.de">s@xss.de</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,
204,204);padding-left:1ex"> <div><u></u>
<div>
<p></p><p>Sonntag, 31. Juli 2022 21:51:<br></p><p> </p><p><u></u> <u></u><u></u><u></u></p><blockquote class="gmail-m_8952315266292790079Odd gmail-m_8952315266292790079QOdd gmail-m

On Sun, 31 Jul 2022 15:55:51 -0700, Lee wrote:

Had a similar issue to the OP, and it turned out to be a flaky internet connection. I switched ISP's and, while sync's still take longer than
I'd like, I don't have the failures, time outs I did before.

I have no complaints about the time taken to sync

% time emerge --sync

Syncing repository 'gentoo' into '/var/portage'...

/var/portage
/usr/bin/git fetch origin
[snip]
=== Sync completed for gentoo

Action: sync for repo: gentoo, returned code = 0


emerge --sync 1.58s user 0.51s system 75% cpu 2.750 total


--
Neil Bothwick

Do Roman paramedics refer to IV's as "4's"?

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmLnDpQACgkQ92eFu0QS MJgf6w/9EJrZIPMsLL35jBZZqigwPPStMgkh9y1ieTDZ7XatauHASp5y80abKg8y dsDdo5g2nwoOygqDFC67yIR7Tqt/pTnYumYbX7PtQ6m8T3W4LVIuoGdVSO6U/Oyw 5yc4SPX844ODfMrn87lU1L7QQ7wsd+a+WbAxRdx2vmAXhH6njRLYz11erQB2C8xF Q4sxqGjgjlgTYot0z9uKjqXXJsSws+3EvhSXy8kP1ihSPfcYHWrk7qUdh8lwOCnj jkyN1HM3xzXbF12vwmc7gojdTlglQDqKO/wOz4U+vcPmXNXwlpxMAiMiG2mhn1ct HFxKFgkquU34eMBXAb/dA8j/u3WSEanDwIAj7ddv8Bxh/fVfGhdZkakdodobgMxx VKQfp2V/4uE2cfvsWml9go7GWCewkNe3t9IzI0obYbxydw2vblezXHeqhYxVzdLt GqVLkpnO8LsyPSphg0N4h4PhOsCyhc79kfk9k2ulJUxC7av05d6A+qdAP1RORcIr lOfDRJQ+wXqAZ42+bVDuWR0+xE5ol04dh+OAegkzJzi1fv1zb0TipwmzF6qNIlZW YPHXwo9Icr0TcGKjK8YuT5Pjag8Ut1wIJOmE55MJL8FzYYGW6vdp1/A+EvxWuyGb 5tv1S0ykkQO8CoX98wrUNtImFoHKuhZgqiZSdXO+eJLqtWPkinY=
=8k0/
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Sunday, 31 July 2022 21:43:12 BST Neil Bothwick wrote:

I switched to using git for syncing, from github, and haven't looked
back. It is *much* faster, several times faster syncing from github than using rsync to sync from a local mirror, and github is always there.

One thing to note, if you do change to git syncing, is that you'll have to delete your entire portage tree: 'rm -r /var/db/repos/portage'. That may seem like a bad idea if you're having sync problems, but it isn't really. After that, the sync will take just seconds, as Neil said.

You'll never look back.

--
Regards,
Peter.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Given the speed improvement in using git for --sync, I wonder why that
isn't the default in the portage section of the manual....

On Sun, Jul 31, 2022 at 4:49 PM Peter Humphrey <peter@prh.myzen.co.uk>
wrote:

On Sunday, 31 July 2022 21:43:12 BST Neil Bothwick wrote:

I switched to using git for syncing, from github, and haven't looked
back. It is *much* faster, several times faster syncing from github than using rsync to sync from a local mirror, and github is always there.

One thing to note, if you do change to git syncing, is that you'll have to delete your entire portage tree: 'rm -r /var/db/repos/portage'. That may
seem
like a bad idea if you're having sync problems, but it isn't really. After that, the sync will take just seconds, as Neil said.

You'll never look back.

--
Regards,
Peter.

--
Lee 😎
<ny6p01@gmail.com>

<div dir="ltr">Given the speed improvement in using git for --sync, I wonder why that isn&#39;t the default in the portage section of the manual....</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Jul 31, 2022 at 4:49 PM Peter
Humphrey &lt;<a href="mailto:peter@prh.myzen.co.uk">peter@prh.myzen.co.uk</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sunday, 31 July 2022 21:43:12
BST Neil Bothwick wrote:<br>

&gt; I switched to using git for syncing, from github, and haven&#39;t looked<br>
&gt; back. It is *much* faster, several times faster syncing from github than<br>
&gt; using rsync to sync from a local mirror, and github is always there.<br>

One thing to note, if you do change to git syncing, is that you&#39;ll have to <br>
delete your entire portage tree: &#39;rm -r /var/db/repos/portage&#39;. That may seem <br>
like a bad i

On 7/31/22 21:51, n952162 wrote:

I've been running gentoo for years now, and every time I go to --sync,
it's really a painful process.

The process can take *very* before you find out if it succeeded or not.

I try different repos.conf servers - one works for a while, then
doesn't, then later, the new one doesn't work anymore and the old one
works again.

I've asked here about it multiple times and get the answers

- "I don't have a problem"

- "just change the server"

- "keep trying"

It can take several hours before it finally works

It seems like a time-out problem.  Or maybe a memory problem ... In any case, it doesn't seem like it ought to be difficult to at least know
what the problem is.

Or?

Thanks all, for the various suggestions, I'll try each.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Monday, 1 August 2022 06:09:07 BST n952162 wrote:

On 7/31/22 21:51, n952162 wrote:

I've been running gentoo for years now, and every time I go to --sync,
it's really a painful process.

The process can take *very* before you find out if it succeeded or not.

I try different repos.conf servers - one works for a while, then
doesn't, then later, the new one doesn't work anymore and the old one
works again.

I've asked here about it multiple times and get the answers

- "I don't have a problem"

- "just change the server"

- "keep trying"

It can take several hours before it finally works

It seems like a time-out problem. Or maybe a memory problem ... In any case, it doesn't seem like it ought to be difficult to at least know
what the problem is.

Or?

Thanks all, for the various suggestions, I'll try each.

Two points to consider when choosing git to sync your portage tree:

1. It used to be the case the first time you run git it would try to download GB of commits history and take ages to do so on a slow connection. The solution used to be to add "EGIT_CLONE_TYPE=shallow" in your make.conf, but
I'm not sure if this is still needed (I don't use git).

2. These days rsync uses hashes and gpg to check the integrity of portage and will flag up a warning in case of file tampering, or corrupt data. As far as I know such a solution doesn't exist with git.
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmLneX0ACgkQseqq9sKV ZxmlZBAAobF43YiItWbllhXwNX3eMrEtxdbp8aAqAb0EpaBO79QpXD9KiNFRa8Yv wDH47isIyE76LPBWWiDeXv33f+QmOKs3x7feHeG5LZ8n4pvtQ8XzbPJKCh5Iltr5 GK3CyKIgpGLyQLGcS5Rp9bIXSLPCdh+59gWCpIqv0RkiKBGc5zreVFmLnPkF4wUa WA8F/MljxnOdV1uezLhAvLuvMiXItW0didOlhViIcfLUzEZ3hagSJHKASVqLNBLo SVm+zJOC1p25lCGKU36DGWjgMOsApk4I4BNVlavXmJAILdvEDJcwgK1XrNac/CIg DfVWvcbKx2uIva6PQ4Wjq7olrmYoJFx92+LRvoMgBG0KySR/J7/vQN2m5o+yaGpo /SWjc+C7xOqOTXq+/6+YP82kEIDJj5H1e/VO1GBSQLgFOVJeu6sxaFYBNs53A7dZ KSRB1i/1jGWekb8NHylX0D0rYmX8MUBPhoruL4Id9xImpuieMmSgxj6wcxEQVmRh LhK8fh7fCR6XSme1rIDJd+/aTzd0xeuPrDqQBV4m519297qC3fs5vsC/hodSKPbB abCEquPmxTCxu9cXZj+5hjfERFF/5119AnEdYvXHWrzNi78wbB/+uKa9txvLjjg4 mAnxzw+IwkZ2bbamvEHD+8fVKt0z484qZ9FHcXvbtu0HiKbmQ6c=
=PBwd
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 01 Aug 2022 07:58:05 +0100, Michael wrote:

1. It used to be the case the first time you run git it would try to
download GB of commits history and take ages to do so on a slow
connection. The solution used to be to add "EGIT_CLONE_TYPE=shallow"
in your make.conf, but I'm not sure if this is still needed (I don't
use git).

It doesn't seem to be the case, running sync with an empty portage tree
gives

Syncing repository 'gentoo' into '/var/portage'...

/usr/bin/git clone --depth 1 https://github.com/gentoo-mirror/gentoo .

% du /var/portage
608M /var/portage

It did take 32s, but most of that was the Performing Global Updates stage.


--
Neil Bothwick

"A hundred years of forgetting and it all comes rushing back..."

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE8k9T/rX16EJxEKG692eFu0QSMJgFAmLnfyMACgkQ92eFu0QS MJjyHBAAsMNeUFe4bpRyamu9GnJxSnOppXOHku8Xcb3MURHnMek96jSDEBbRIZsK LNKb7o2IvNbT9FBOGH+lrZ5FhhuN8CSsCrmCo+5G7vAXbnR2Tzbwn5VXr12EJ23a TCgMYTCj6ZtguuJO1J8b0MTU6m/ffQZKghzSbEHFV1BTUQoUrq8PRm+n85N5hC+4 a2oXtHBGHWL3GRUXSruweuqZzSJUu0Mhp2ajLpXnAr14Z012cElvyQbWnG8I5zc0 H1fcCljPN8iKJ+3E+GKDARvB7LqpuoGu56TlSxwFHHcbXbJKBzeOUn7ikeHQEJiJ kb8dDvVAEKDxOBHJAdyeezK6ew1BJXZGu4GgFDzXWXu0aAyQqKmijDQpuAIvz6zA t7BP8SKArNVnWNbPq98ULkSohPBuEJGiEuZ4zg0LrRLC0hPKPmLUhW9FRubh0JpH YSrN7wAal99lGfZbQb66MVjhklLpr6PkF2wDkdrhk+XuJaWF6kWju9zDSmxfELDN Wqp1UMM6M4JWVQuxoXuDpyqFtiQ+pvjyTFxUtPbwIxZ126sRJ6f5aWdN6VKRx5mX Ox4zsawOpamBhN8qIsyXakOQcmyeJVLZ6I2INr46p9oukK0kzN7g+SDbY4pCgbI3 cWtYJdHYbgLSVnAI4ttCdh3VxMJ1VrmVaCr2PKGNhACqFgikRhk=
=1IER
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2022-08-01 07:58+0100 Michael <confabulate@kintzios.com> wrote:

[…]

2. These days rsync uses hashes and gpg to check the integrity of
portage and will flag up a warning in case of file tampering, or
corrupt data. As far as I know such a solution doesn't exist with
git.

Verification can be turned on with
sync-git-verify-commit-signature = yes
in repos.conf.[1] This does not seem to be enabled by default.[2]

[1] <https://wiki.gentoo.org/wiki/Project:Portage/Repository_verification#git> [2] <https://wiki.gentoo.org/wiki/Portage_Security#git-mirror_repositories>

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Monday, 1 August 2022 10:43:55 BST tastytea wrote:

On 2022-08-01 07:58+0100 Michael <confabulate@kintzios.com> wrote:

[…]

2. These days rsync uses hashes and gpg to check the integrity of
portage and will flag up a warning in case of file tampering, or
corrupt data. As far as I know such a solution doesn't exist with
git.

Verification can be turned on with
sync-git-verify-commit-signature = yes
in repos.conf.[1] This does not seem to be enabled by default.[2]

[1] <https://wiki.gentoo.org/wiki/Project:Portage/Repository_verification#git> [2] <https://wiki.gentoo.org/wiki/Portage_Security#git-mirror_repositories>

I see ... this is an improvement from what I recall it to be. Thanks for pointing it out. Perhaps I should start using git again. :-)
-----BEGIN PGP SIGNATURE-----

iQIzBAABCAAdFiEEXqhvaVh2ERicA8Ceseqq9sKVZxkFAmLnpggACgkQseqq9sKV Zxl3xBAAyX8kxTnzIWAnUTGMqEfUporOVVmeCMTpq/k/xKKPHH1Qp3BqWmhg/K5h tCk2HrnOGpmqXUJWuUwZd6/16l6SWq1lgXDwfEr6rnbiDRIMLuX83bcxHe7HZI/l 4+mrp603/vc/04tc73f0qXPr2tE01oU3DNwSJSF4caTnxI/QVAE/FkycvZYIEc9s X7czkiJPKaQAMwvp8LBCkwRi1N2+Sh4Hz/NIMkRTJQFtYDipMZT+Vn/HEL68Rqp7 TpN+11Qyi37ashDa1GLkHmQkYSuvKQk+r6xS3ofyZIu0bxTmhnzcAqweJL5MHPu4 h9ZPUpmDK7vHMKZyJfbfmb8dnbir2Jo2u2wSOL51j0CVVCA13YMoKz0hbSi5mdc/ KpMtDdwNKit2ug3lcJ1DCr/vgcQxzJgZ17WiyS0gLikuk2+Z6A+vaFUKiZ+rbvPt Z0WR5lLa3LBdQi1yci49AeyllhYezsuE2Z8S5LfU5s3m5zymJ2hNkBl1DLnbIuD5 fQdFDMeW4i/C/hiZY+7lQ8xIMVDUQaLwMyfvAMtVYThqSFROLA/oteGZzGvWiJII UWyfMQE0/TqYUZESqsvSs+P58kJGn91aUp795c0Vy/8LitaTr1x2Lk0rfJ/3CZBp XBI8XjQn/hSl53se7uNCmYAUSpYWDs9Hwqu7DZ22ODMS/TTmCRc=
=pw5O
-----END PGP SIGNATURE-----

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2022-07-31, n952162 <n952162@web.de> wrote:

I've been running gentoo for years now, and every time I go to --sync,
it's really a painful process.

The process can take *very* before you find out if it succeeded or not.

In my experience, long --sync times have always been due to a slow
rsync server. Switching to a different server fixed it for me (though
sometimes it took a few tries to find a server that responded in a
timly manner).

That said, git is an order of magnitude faster than even the fastest
rsync server.

It can take several hours before it finally works

That seems like something other than just a slow server. When dealing
with slow servers, it never took more than 15-30 minutes.

--
Grant

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Neil,

On Sunday, 2022-07-31 21:43:12 +0100, you wrote:

...
I switched to using git for syncing, from github, and haven't looked
back. It is *much* faster, several times faster syncing from github than using rsync to sync from a local mirror, and github is always there.

The replies from you and some other people suggesting the use of Git for syncing and providing howtos were the straw that broke the camel's back
and overcame my lazyness. So I too switched to Git and now am as happy
as can be :-D

Many thanks for this tip :-)

Sincerely,
Rainer

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)