diff options
| author | Sebastian Lackner <sebastian@fds-team.de> | 2015-07-04 18:39:42 +0200 |
|---|---|---|
| committer | Allan McRae <allan@archlinux.org> | 2015-08-08 10:45:09 +1000 |
| commit | 578035075108a90d20f084f077badf05d1c8527c (patch) | |
| tree | a6213e7ec05487053d5b7c25879c35f30e6f7808 /proto | |
| parent | ae97082e98b6c3984799ba9f3f6ccc6ef5da6034 (diff) | |
libalpm: Force update when database is marked as corrupted.
When a database and its signature is updated non-atomically on a server,
there is a window where a user may update the database but grab the old
signature. The database is marked as invalid by libalpm, which can be
fixed by forcing a refresh (assuming the server has caught up and the
user realizes what has happened) or with a future update of the repo.
Work around this by forcing a repository refresh whenever a database is
invalid.
Signed-off-by: Sebastian Lackner <sebastian@fds-team.de>
Signed-off-by: Allan McRae <allan@archlinux.org>
Diffstat (limited to 'proto')
0 files changed, 0 insertions, 0 deletions