Re: [Rpm-maint] [rpm-software-management/rpm] Warn and fall back to dummy database on unknown database backend config (471b7be)
Hmm. I suppose it's entirely possible that exact scenario couldn't happen with the current codebase anyhow, the detection code is quite different from what was in 4.15 (which is what caused my first-ever rpmdb loss). Still, I think it's better to be safe than sorry with our primary piece of data. Been intending to submit a patch to disable the implicit db initialization, that'll make things a little saner and safer too. -- 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/commit/471b7be4bd5cc7f245f9aa00c7784a7056e439b7#commitcomment-44296125___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] Warn and fall back to dummy database on unknown database backend config (471b7be)
The idea is that it prevents the kind of scenario described in the commit message from happening in the future. If an unknown database is configured, rpm cannot know if its just a typo or some new backend from a newer rpm version (consider eg various chroot scenarios), and together with the implicit database init (which is really the evil thing here) it's downright dangerous. It's not the most common scenario for sure, but this chain of events managed to nuke the rpmdb on my own laptop... -- 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/commit/471b7be4bd5cc7f245f9aa00c7784a7056e439b7#commitcomment-44295216___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
Re: [Rpm-maint] [rpm-software-management/rpm] Warn and fall back to dummy database on unknown database backend config (471b7be)
Ok, I may be a bit dense here, but: what exactly does the commit guard? The only thing it seems to do is disabling autoprobing of the database if there is a unknown database backend config, but why is this a bad thing? I.e. why would it fallback to bdb? -- 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/commit/471b7be4bd5cc7f245f9aa00c7784a7056e439b7#commitcomment-44294491___ Rpm-maint mailing list Rpm-maint@lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint
