Calibre not playing well with git-annex

Bug #739045 reported by Christopher Browne on 2011-03-20
This bug affects 3 people
Affects Status Importance Assigned to Milestone

Bug Description

Running on Linux, version 0.7.44...

I was hoping to use git-annex ( to manage copying bits of my library to different hosts.

"git-annex allows managing files with git, without checking the file contents into git. While that may seem paradoxical, it is useful when dealing with files larger than git can currently easily handle, whether due to limitations in memory, checksumming time, or disk space.

Even without file content tracking, being able to manage files with git, move files around and delete files with versioned directory trees, and use branches and distributed clones, are all very handy reasons to use git. And annexed files can co-exist in the same git repository with regularly versioned files, which is convenient for maintaining documents, Makefiles, etc that are associated with annexed files but that benefit from full revision control."

I "ran" git-annex against one of my Calibre library instances. This shifts all the "real" files into the git repository "object area," leaving symlinks. Calibre is fine with this, until I try copying some books onto my Kobo, at which point Calibre decides the book files can't be written to, and refuses to do the copy.

That is, in fact, correct; git-annex stows its documents in what it terms "WORM" files (e.g. - Write Once, Read Many), which get made read-only.

It seems unfortunate that copying a book from one place to another requires modifying it, and it seems to me that there would be value in having Calibre *mostly* have the invariant that it never writes to book files.

This might represent a rather deeper change than anyone wants to go into.

This is not worth the effort for me personally. If some one else wants to implement it, I will be happy to supply any needed guidance. If so, re-open the ticket and we can discuss it.

 status wontfix

Changed in calibre:
status: New → Won't Fix
a-or-b (still-another-person) wrote :

This is also an issue for me, but also leads to a bigger question:
  Why does Calibre need to have write access to existing book files in the library?

 Surely this means that backup software will flag changes when it doesn't seem that there would need to be any?

i.e. my file of Ulysses from Project Gutenberg shouldn't change whether it is on my ereader or not and so shouldn't need to be backed up if nothing else has changed...

Or am I missing something deep in the design of Calibre?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers