1 |
Joshua Kinard wrote: |
2 |
> This might already be covered in one of the other e-mail threads, but I've been |
3 |
> super-busy as of late and just recently ran 'emerge --sync' on my main dev box |
4 |
> for the first time after the git migration. I just synced my main dev box |
5 |
> again, ~10 hours after the last sync, but it looks like the 'Manifest' files |
6 |
> for *every* package in the tree are getting downloaded with each sync. |
7 |
> |
8 |
> I compared two Manifest files from a given package that shouldn't have changed |
9 |
> in the last 10 hours (sys-kernel/mips-sources), and there is nothing different |
10 |
> timestamp wise or content wise between then. So I'm not sure what's causing |
11 |
> 'emerge --sync' to re-fetch the whole file. |
12 |
> |
13 |
> Has anyone else noticed this and/or have a workaround? It's causing some |
14 |
> excessive disk thrashing, and what used to be a few seconds to sync is now |
15 |
> taking 5-10mins or more (depending on which machine I'm syncing). |
16 |
> |
17 |
|
18 |
|
19 |
I have synced a few times since the change and each time, it takes a lot |
20 |
longer to sync. You are not the only one that has noticed this. |
21 |
|
22 |
No clue as to why or how to fix tho. |
23 |
|
24 |
Dale |
25 |
|
26 |
:-) :-) |