calibre-debug --export-all-calibre-data hangs at metadata.db

[shayaknyc]

Originally Posted by kovidgoyal

That's a different error. You need to open the libraryin the calibre program so that calibre knows about it. Once you do so you wont have that error any more.

Ok, so I loaded Calibre GUI in the VM and pointed it to the Calibre-Subset library (see attached screenshot)

However, after it loads the library correctly, I run the same export command and this is what I got:

$ calibre-debug --export-all-calibre-data /home/shayaknyc/Calibre-Backup-20260202 /home/shayaknyc/Calibre-Subset
Traceback (most recent call last):
  File "runpy.py", line 198, in _run_module_as_main
  File "runpy.py", line 88, in _run_code
  File "site.py", line 47, in <module>
  File "site.py", line 43, in main
  File "calibre/debug.py", line 308, in main
  File "calibre/utils/exim.py", line 552, in run_exporter
KeyError: '/home/shaya/Calibre-Subset'
$

[kovidgoyal]

I dont see how that's possible unless your GUI and CLI commands are accessing different config directories. In any case I have already removed the constraint that export has to work with known libraries for the next release.

[shayaknyc]

Originally Posted by kovidgoyal

I dont see how that's possible unless your GUI and CLI commands are accessing different config directories. In any case I have already removed the constraint that export has to work with known libraries for the next release.

I mean, this doesn't make any sense. Fresh Ubuntu VM, fresh calibre install, same library I shared with you, which you did not seem to have a problem with. So, I'm not at all sure what's causing this behavior....