1 |
Had a similar issue to the OP, and it turned out to be a flaky internet |
2 |
connection. I switched ISP's and, while sync's still take longer than I'd |
3 |
like, I don't have the failures, time outs I did before. |
4 |
|
5 |
On Sun, Jul 31, 2022 at 1:54 PM Stefan Schmiedl <s@×××.de> wrote: |
6 |
|
7 |
> Sonntag, 31. Juli 2022 21:51: |
8 |
> |
9 |
> |
10 |
> |
11 |
> I've been running gentoo for years now, and every time I go to --sync, |
12 |
> it's really a painful process. |
13 |
> |
14 |
> |
15 |
> The process can take *very* [long] before you find out if it succeeded or |
16 |
> not. |
17 |
> |
18 |
> ... |
19 |
> |
20 |
> |
21 |
> It can take several hours before it finally works |
22 |
> |
23 |
> |
24 |
> |
25 |
> Use a tool like atop to get some info about the throughput |
26 |
> |
27 |
> of your network connection. Something like "ss -ntp" might |
28 |
> |
29 |
> show interesting info about the state of the connection |
30 |
> |
31 |
> between your machine and the server, too. |
32 |
> |
33 |
> |
34 |
> |
35 |
> You might have problems with DNS name resolution or your |
36 |
> |
37 |
> box patiently trying to establish an IPv6 connection when |
38 |
> |
39 |
> your internet connection is IPv4 only. |
40 |
> |
41 |
> |
42 |
> |
43 |
> But switching to git, like Neil said, does make things faster. |
44 |
> |
45 |
> |
46 |
> |
47 |
> FWIW, my config file reads like this: |
48 |
> |
49 |
> |
50 |
> |
51 |
> # cat /etc/portage/repos.conf/gentoo.conf |
52 |
> |
53 |
> [DEFAULT] |
54 |
> |
55 |
> main-repo = gentoo |
56 |
> |
57 |
> |
58 |
> [gentoo] |
59 |
> |
60 |
> location = /var/db/repos/gentoo |
61 |
> |
62 |
> sync-type = git |
63 |
> |
64 |
> sync-uri = https://github.com/gentoo-mirror/gentoo.git |
65 |
> |
66 |
> auto-sync = yes |
67 |
> |
68 |
> sync-git-verify-commit-signature = yes |
69 |
> |
70 |
> sync-openpgp-key-path = /usr/share/openpgp-keys/gentoo-release.asc |
71 |
> |
72 |
> |
73 |
> |
74 |
> good luck, |
75 |
> |
76 |
> s. |
77 |
> |
78 |
> |
79 |
> It seems like a time-out problem. Or maybe a memory problem ... In any |
80 |
> case, it doesn't seem like it ought to be difficult to at least know |
81 |
> what the problem is. |
82 |
> |
83 |
> |
84 |
> Or? |
85 |
> |
86 |
> |
87 |
> |
88 |
> |
89 |
> |
90 |
> |
91 |
|
92 |
-- |
93 |
Lee 😎 |
94 |
<ny6p01@×××××.com> |