Hmm. Actually doing the WAL docs suggested `PRAGMA journal_mode=DELETE` on the
database results in a database that can still be opened by rpm, regular users
and all. Rpm will try to re-establish WAL if opened in read-write mode, so
nothing too terrible should happen if you do the journal delete as a part of
the image building. Except voiding the warranty :wink:
It'd be nicer of course if rpm had a supported procedure to "park" databases
for this kind of thing. --rebuilddb with some special flag maybe.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/issues/2219#issuecomment-1268066501
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/issues/2219/1268066...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
http://lists.rpm.org/mailman/listinfo/rpm-maint
