Is this still true? Otherwise, I now know my problem. since I was not using the --dbpath option in my list-broken-files command at the time, it was just generating a random new sqlite db filename in the dbconfig.json file, and then failing because that file doesn’t exist.
Am I right? Because if so, the necessity of that --dbpath option in the command line docs needs to be pointed out.
I did do an export/import IIRC, but it’s been quite a while since I did it. I do think I had to uncheck the “import metadata” box to get the import to work.
Just for fun, I renamed my dbconfig.json to something else, and re-ran the list-broken-files command, with no dbpath option. It created a random db filename in the new dbconfig.json, but didn’t actually create the .sqlite file.