Some Debian users aren't thrilled about a behavior change associated with the 
20170611 Berkeley DB 2 DB_CONFIG fix.  Apparently [1] something like:

| root@playbox01:~# postmap test/in

used to work, but now there is an error:

| postmap: fatal: open database test/in.db: No such file or directory

[1] in the bug report, I suggested this was a reasonable side effect of the 
change, but not everyone agreed, so I said I'd ask if that could be made to 
work again.

Any feedback on this?

Scott K

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879200

Reply via email to