The recent portage snapshot issues (Bug #79455) showed a weakness in emerge-webrsync, in that it will fetch and sync against a previously-installed snapshot, as it doesn't track the last "successful" snapshot. I have made some changes to the script to do this (and also slightly improved help, and fixing of another couple of issues that annoy me), and submit this patch for inclusion in the original source. Reproducible: Always Steps to Reproduce: Expected Results: Portage should not try to download a snapshot it has already used.
Created attachment 50009 [details, diff] Patch to emerge-webrsymc, which adds last successful date support etc This patch will add "last successful date" support, by recording the date of the last successful snapshot download into /var/lib/portage/webrsync-date. The patch also adds help (-h) support, and fixes one or two minor things that irk me about the current script.
Created attachment 50025 [details, diff] Corrected patch Whoops, the last version of the patch missed the line which updates the stored date - now corrected.
Created attachment 50086 [details, diff] Third attempt to generate a patch to emerge-webrsync Brain obviously asleep the previous day - this patch should work.
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.
In the time since this bug was initially raised, I've also made some other minor changes to my own copy of "emerge-webrsync"; the main one is the use of a tmpfs filesystem to unpack the downloaded tarball into (since I have plenty of RAM and this prevents disk IO contention). Would you like me to update the attached patch with a newly generated one with these features as well?