1 |
On Thu, Jan 24, 2019 at 7:55 PM Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
> |
3 |
> On Thu, 24 Jan 2019 19:18:17 -0500, Alan Grimes wrote: |
4 |
> |
5 |
> > Since 2004, I have been using "emerge --sync" to update my portage tree. |
6 |
> > I understand that it accesses a local list of mirrors and then runs |
7 |
> > rsync against one of those. On spinning media hard disks it is helpful |
8 |
> > to pre-cache the portage tree as shown in my scripts, on SSD systems, it |
9 |
> > is simply harmless. I refreshed my mirror list and selected either HTTP |
10 |
> > or RSYNC mirrors from across the USA. |
11 |
> |
12 |
> I doubt that there is an advantage in pre-caching, all you are doing is |
13 |
> taking time from the sync process and adding it to another process, but I |
14 |
> also doubt that has anything to do with your problems. |
15 |
> |
16 |
> > The problem is NOT with emerge in that the files that it complains about |
17 |
> > not being present are in fact not present. |
18 |
> |
19 |
> That's the rub, they are present here, so something is interfering with |
20 |
> your downloading of these patch files. Do you have any entries in |
21 |
> make.conf that would modify rsync behaviour? Try |
22 |
> |
23 |
> emerge --info -v | grep -i sync |
24 |
> |
25 |
> Also, what do you have in /etc/portage/repos.conf/gentoo.conf? |
26 |
> |
27 |
|
28 |
Some kind of rsync issue (assuming rsync is even being used) seems |
29 |
likely. It is a bit odd since I'd think that rsync would download the |
30 |
missing files at about the same time that it downloads the manifests - |
31 |
I assume that it goes in directory order. |
32 |
|
33 |
If you have some kind of environment variable or make.conf option set |
34 |
that overrides rsync defaults maybe that is causing rsync to not |
35 |
actually sync the tree? Deleting /usr/portage and re-syncing seems |
36 |
like an obvious way to wipe the slate clean. Other local issues could |
37 |
be anything that might cause rsync to terminate prematurely (RAM, |
38 |
ulimit, whatever - obviously unlikely). |
39 |
|
40 |
Knowing what mirror is in use may also be helpful - could be a bad |
41 |
mirror or something. What server/IP/etc is being output in the emerge |
42 |
--sync output? |
43 |
|
44 |
If you're syncing with git and manually modify stuff in the local repo |
45 |
that can cause issues since git will start getting merge conflicts. |
46 |
rsync just overwrites your repo with the Gentoo one and wipes out your |
47 |
own changes. |
48 |
|
49 |
If you use emerge-webrsync then the sync operation itself should use |
50 |
gpg signature checking and that should rule out server issues. Ditto |
51 |
if you sync with git with the appropriate settings, though git also |
52 |
has internal hash consistency checking (that doesn't prevent |
53 |
intentional tampering but should catch data transmission issues). |
54 |
|
55 |
The suspicion of an error by a Gentoo developer is a possibility, but |
56 |
these are pretty rare and usually get fixed very quickly. If you sync |
57 |
from one of the stable mirrors in git those are all screened by CI |
58 |
which eliminates these sorts of missing file issues (granted, in git |
59 |
we don't track FILESDIR in manifests anyway). If this is happening it |
60 |
would be trivial to detect on the various online git repositories - so |
61 |
checking these for the error before pointing fingers is appropriate. |
62 |
Typically these sorts of errors are caught by bots and result in |
63 |
plenty of internal shaming already, which is why it is likely a |
64 |
problem like this would be short-lived. |
65 |
|
66 |
-- |
67 |
Rich |