When does calibre use mechanize? Because then it will use the wrong version of html5lib.

@FRidh, I'm not sure where else, but the command in question is calibredb; there is a way to pass it a URL, so as long as you have calibre running with the server enabled (or run the standalone server), then this one will show all book titles in the library matching the search (in this case, any works by Arthur Conan Doyle is used as the exemplar).

calibredb \
    --with-library="http://localhost:8080/#Calibre_Library" \
    list \
    -f title \
    -sort_by=title \
    -s 'authors:"=Arthur Conan Doyle"'

This does assume that your library uses the default name of Calibre Library; there are instructions for how to use calibredb to get a list of libraries on the server which IIRC should also trigger the bug.

I discovered yesterday that my computer's case fans are dead, so it overheats if I do any long compilation, so e.g. building chromium causes it to lock up or power off. As such, I hadn't gotten this into actual use to see if this is an issue in practice; I was just able to verify that the base commands would handle <cmd> --help as they have in the past. I'll run the above test once I have the system fully working, and will see if I can figure out another way around this, but we may have to override mechanize just for calibre (to not propagate html5lib).

Running a full test of my use case (as described above) with the changes in this branch does work.

My guess is that when calibre uses html5lib directly, it depends on html5lib_0_9999999, while other code uses mechanize instead, which acts as a wrapper around the newer html5lib (thus not exposing the new html5lib to most of calibre).

Perhaps someone more familiar with python packaging in nix can explain why this works, but including the older html5lib after mechanize in the buildInputs list or using the vendored version does not?

My guess is that when calibre uses html5lib directly, it depends on html5lib_0_9999999, while other code uses mechanize instead, which acts as a wrapper around the newer html5lib (thus not exposing the new html5lib to most of calibre).

I doubt it picks the correct version depending on what code is used. Instead, I think the parts of mechanize that are used work fine with another version of html5lib.

I'll merge this but its very fragile. Unfortunately I don't see any other solution either.