Alan Hourihane
Tue, 13 Oct 2009 04:21:23 -0700
On Tue, 2009-10-13 at 11:43 +0100, Alan Hourihane wrote: > On Tue, 2009-10-13 at 12:37 +0200, Fabian Groffen wrote: > > On 13-10-2009 11:09:11 +0100, Alan Hourihane wrote: > > > > Yes it happens everytime, regardless of sync. > > > > > > > > For example, if I do say.... > > > > > > > > emerge net-ftp/lftp > > > > > > > > It does a bunch of updates before it starts "Calculating dependencies". > > > > > > > > And for > > > > > > > > emerge --sync > > > > > > > > It does a bunch of updates before the sync happens, then a bunch of them > > > > again after it's finished. > > > > > > > > Alan. > > > > > > > > > > > > > > Here's what happens with an emerge --sync.... > > > > could this be related to statvfs? Sounds like Portage can't see that > > the files still have the same timestamp, and hence reparses them > > Don't think so, as the statvfs call is only made to check there's enough > storage space. No date/time checking.
So I moved /var/cache/edb/mtimedb out of the way and ran emerge --info to update mtimedb. I got the full complement of Performing updates for every quarter and every year this time which is expected. Then I run emerge --info again and the same select ones re-appear as reported before, being these.... Performing Global Updates: /usr/portage/profiles/updates/1Q-2004 Performing Global Updates: /usr/portage/profiles/updates/2Q-2004 Performing Global Updates: /usr/portage/profiles/updates/3Q-2004 Performing Global Updates: /usr/portage/profiles/updates/4Q-2004 Performing Global Updates: /usr/portage/profiles/updates/1Q-2005 Performing Global Updates: /usr/portage/profiles/updates/1Q-2006 Performing Global Updates: /usr/portage/profiles/updates/1Q-2007 Performing Global Updates: /usr/portage/profiles/updates/2Q-2007 Performing Global Updates: /usr/portage/profiles/updates/1Q-2008 Performing Global Updates: /usr/portage/profiles/updates/4Q-2009 Alan.