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.
signature.asc
Description: This is a digitally signed message part.
