[Rpm-maint] [rpm-software-management/rpm] Ensure database creation on initial installation (#1639)

[Panu Matilainen]

Disabling implicit database creation on read-only handles in commit
afbc2b07839c9ffe9f274f3a4bc2395c76d65472 broke number of handy
use-cases such as install to an empty chroot directory, both with
rpm itself and dnf/yum at least, probably others too.

This minimally resurrects the desired part of the behavior: if people are
asking us to install something, creating a missing database is probably
okay to create without requiring an explicit --initdb action first.
It'll still spit some ugly errors from trying to load the keyring but
at least it'll work. The harmless errors we can try to deal with
separately later on.
You can view, comment on, or merge this pull request online at:

  https://github.com/rpm-software-management/rpm/pull/1639

-- Commit Summary --

  * Ensure database creation on initial installation

-- File Changes --

    M lib/depends.c (6)

-- Patch Links --

https://github.com/rpm-software-management/rpm/pull/1639.patch
https://github.com/rpm-software-management/rpm/pull/1639.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/1639
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rpm.org/pipermail/rpm-maint/attachments/20210416/2326031a/attachment.html>