Can we add a --force (-f) to emerge to force it to sync the tree. Sometimes the connection gets dropped before the tree is sync'ed and emerge then doesn't want to recover unless all the timestamp file are deleted. Reproducible: Always Steps to Reproduce: 1. 2. 3.
you don't have to delete all timestamp files, just /usr/portage/metadata/timestamp.chk is used for timestamp checking when emerge sync'ing but i think that a --force option is helpfull for new users
Nakano: Wanna figure this one out?
--force isn't necessary if the timestamp's state is maintained properly.
ive seen the problem originally described once or twice before ... however, one reason to have a -f with sync would be that perhaps a user deleted a bunch of subfiles by accident and wants to fix that by syncing again
Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;)
Reopening for consideration (not much for this though).
Rather than add an option for this, I think that emerge's timestamp message should just print the full path of the timestamp file and inform them to remove it in order to force sync.
In svn r5565 it now says this (appropriately for the current value of $PORTDIR): >>> In order to force sync, remove '/usr/portage/metadata/timestamp.chk'.
This has been released in 2.1.2_rc4-r9.
