| 1 |
Paul Sobey schrieb: |
| 2 |
> For the last couple of weeks I've noticed that emerge -puv world takes |
| 3 |
> an absolute age on my machine (currently at 5 mins and counting), while |
| 4 |
> the cpu gows to 100%. The little emerge rotator bar that spins while it |
| 5 |
> calculates dependencies moves extremely slowly. Is there any known bug |
| 6 |
> that causes this? How can I go about troubleshooting? |
| 7 |
> |
| 8 |
> Cheers, |
| 9 |
> Paul |
| 10 |
|
| 11 |
|
| 12 |
My guess is you have removed the portage-cache before using emerge. |
| 13 |
Normally this happens when a previous emerge --sync fails because of an |
| 14 |
error or there are identical timestamps on the server and the local machine. |
| 15 |
|
| 16 |
When this happens you have no portage-cache because portage deletes the |
| 17 |
cache first when syncing. If the timestamps are identical the cache is |
| 18 |
not regenerated. If there is an error while syncing the cache is missing |
| 19 |
too, because the regeneration of the cache is done in the end of the sync. |
| 20 |
|
| 21 |
So the cache is regenerated when doing the first emerge and this takes |
| 22 |
quite a while. Even on a Core2Duo 6600@2.40GHz i takes more then three |
| 23 |
minutes :-). |
| 24 |
|
| 25 |
In case of the timestamp issue i think it is a bug [1]. I think portage |
| 26 |
should first check the timestamps and if they are different it should |
| 27 |
delete the cache! |
| 28 |
|
| 29 |
[1] http://bugs.gentoo.org/show_bug.cgi?id=202535 |
| 30 |
|
| 31 |
Regards, |
| 32 |
|
| 33 |
Daniel |
| 34 |
-- |
| 35 |
gentoo-user@l.g.o mailing list |
Archives