Fix index file's mtime, which can differ from TIMESTAMP.
authorW-Mark Kubacki <wmark@hurrikane.de>
Wed, 1 Aug 2012 19:12:24 +0000 (21:12 +0200)
committerZac Medico <zmedico@gentoo.org>
Thu, 2 Aug 2012 00:54:44 +0000 (17:54 -0700)
commit13abe0398fbe724218c8c9ac2597ebe15d7db7e1
treece0071d388d3f00ce97b794fca743f9b28c310c1
parentcbebf76d8e5666aad4984f87c2be83d474fe5a7e
Fix index file's mtime, which can differ from TIMESTAMP.

This enables Portage to reliably query for remote indices with
HTTP-header If-Modified-Since.

Without this patch mtime is greater than TIMESTAMP for large
indices and slow storages - because writing a large file takes
time. If the difference spans a second (TIMESTAMP 08:00:00, mtime
08:00:01), then Portage will always fetch the remote index because
it will appear being modified (mtime is used there) after the copy
has been made (local copy's TIMESTAMP is used here).
pym/portage/dbapi/bintree.py