Currently we always say "Invalid or corrupt database" when database
signature checking fails.  This is particularly confusing when there
is not signature.

Also, we immediately verify databases at the start of the transaction
which potentially results in (invalid) error messages being output
that may be fixed when the sync database gets updated.


I'm not 100% convinced this is the right way to fix this...


Allan McRae (2):
  Provide a mechanism to skip validation of sync repos
  Provide more information for database signature failures

 lib/libalpm/alpm.h      |  4 +++-
 lib/libalpm/be_sync.c   | 20 ++++++++++++++++----
 lib/libalpm/db.c        |  4 ++--
 lib/libalpm/db.h        |  3 ++-
 lib/libalpm/error.c     |  2 ++
 src/pacman/conf.c       |  2 +-
 src/util/cleanupdelta.c |  2 +-
 src/util/pactree.c      |  2 +-
 src/util/testdb.c       |  2 +-
 9 files changed, 29 insertions(+), 12 deletions(-)

-- 
1.8.3.3


Reply via email to