Don't restore db file atime/mtime after rebuild
authorPanu Matilainen <pmatilai@redhat.com>
Wed, 10 Nov 2010 11:44:02 +0000 (13:44 +0200)
committerPanu Matilainen <pmatilai@redhat.com>
Wed, 10 Nov 2010 11:44:02 +0000 (13:44 +0200)
commit1ba00100204711ed0454746dd294002f97931226
tree74b288a9ec6059ccaf37d55754eb108d77f8e761
parentad0687bd5726092d822886fdbf8aa55a63b4c4b2
Don't restore db file atime/mtime after rebuild
- The files are regenerated from scratch, involving header record
  numbers moving around, possibly removing broken headers and all.
  Don't pretend nothing changed when some changes almost certainly,
  occurred, various API users rely on rpmdb mtime for determining
  whether the db has changed since they last accessed it.
lib/rpmdb.c