It may be worth mentioning that calibredb is
supposed to emit an error message explaining the problem, but due to an oversight on Windows and macOS, this was not actually printed.
This should be fixed in the next release, see:
https://github.com/kovidgoyal/build-...bb3229e0fff372