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 😎 <ny6...@gmail.com>
