Commit e96fde8 doesn't quite cut it:
```
backend/dbi.c: In function ‘dbDetectBackend’:
backend/dbi.c:39:5: warning: not enough variable arguments to fit a sentinel
[-Wformat=]
char *db_backend = rpmExpand("%{?_db_backend}");
^~~~
```
Also I think software should honor configuration:
After looking at current rpm.org sources, RPM still initializes with ts->dbmode
= DB_RDONLY, and then reopens the rpmdb with O_RW in rpmtsSetup(). That opens
a (minor and mostly irrelevant wrto RPM on OS X) race window.
There is still the ability to disable fsync (or replace with fdatasync)
I have now updated the patchset again, addressing the crashes with old gcc, and
Jeff's comment above. And this time they should be rebased correctly :)
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
There's an endless row of bugs where BDB environment getting corrupted, some
of which have been BDB bugs (several found just in the last couple of years)
that have been patched in Fedora/RHEL libdb but upstream BDB 5.x does not have,
dunno about 6.x but there you run into the licensing side.
Here are the patches in libdb-5.3.28-20: the patches are trackable to bug
reports and appear to have been fixed by "upstream"
`# License clarification patch
#
http://devel.trisquel.info/gitweb/?p=package-helpers.git;a=blob;f=helpers/DA
