This is a consequence of the poor layout noted in this comment in
purge_missing:
if (will_run_mandb)
/* Reset mtime to avoid confusing mandb into not running.
* TODO: It would be better to avoid this by only opening
* the database once between here and mandb.
*/
MYDBM_SET_TIME (dbf, db_mtime);
There are some situations where a later update_db will not actually
modify the database and update the mtime, and in this situation
purge_missing may have updated the database but reset the mtime to its
previous value. The reorganisation implied by this comment would fix
this.
** Changed in: man-db (Ubuntu)
Status: New => Triaged
** Changed in: man-db (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1411633
Title:
man-db's manipulation of index.db mtime timestamp interferes with
incremental backups
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1411633/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
