| 1 |
Robert Bradbury wrote: |
| 2 |
> I commonly run: |
| 3 |
> emerge --pretend --update --verbose --deep --newuse world |
| 4 |
> at least once every day to provide a list of recently updated packages |
| 5 |
> that I need to re-emerge. |
| 6 |
> |
| 7 |
> I've noticed recently (in the last 1-2 weeks) that it seems to be taking |
| 8 |
> a very long time. The one I've got running now has on the order of 8+ |
| 9 |
> CPU minutes which seems very long. I think this used to take <2 minutes. |
| 10 |
|
| 11 |
Maybe it's backtracking for some reason. If that's the case, should |
| 12 |
see some related messages about backtracking. Please file a bug at |
| 13 |
http://bugs.gentoo.org and include --pretend --debug output for the |
| 14 |
long-running dependency calculation. |
| 15 |
|
| 16 |
> I've also noticed some chatter on the gentoo-dev list about including |
| 17 |
> package dates in the portage database. |
| 18 |
> |
| 19 |
> Has anyone else encountered this problem or have any ideas about the |
| 20 |
> possible cause? Could it be python version related? |
| 21 |
|
| 22 |
I haven't seen any other reports like this. I doubt that the python |
| 23 |
version is related. |
| 24 |
|
| 25 |
> Versions are: portage-2.1.7.1 and Python 2.6.3 (r263:75183, Oct 3 2009, |
| 26 |
> 02:52:55). |
| 27 |
> |
| 28 |
> Thanks, |
| 29 |
> Robert |
| 30 |
> |
| 31 |
> |
| 32 |
|
| 33 |
|
| 34 |
-- |
| 35 |
Thanks, |
| 36 |
Zac |
Archives