Marcel Waldvogel

I just ran into the same problem. 1. Immutable should not prevent the deduplication, as it does neither modify the (user-visible) contents of the file nor allow later modification that...

Looking at the code changed in #97, it seems that earlier, `EACCESS` was returned on immutable (at least that's how it is handled). Now, special handling for `EPERM` is added....

#97 works fine for me

#97 does not fix the *cause*, but makes the error message more helpful (mentions immutable) and improves the behavior (does not abort when it probably is only due to immutable)....

BTW: I have since stopped using deduplication on btrfs. Deduplication was very successful on my backup disks (created using `rsync --link-dest`), probably too successful. It resulted in slowing down many...

@lilydjwg: My cause of immutable attributes was terminating a `bedup dedup` run with ^C

A (not really elegant) workaround would be to ```sh btrfs property set "$dir" ro false bedup dedup "$dir" btrfs property set "$dir" ro true ``` It worked for me with...

Just a naive question: Deduplication (unlike hardlinks) is supposed to be invisible for the user. What is your use case for knowing which files share blocks? (This happens with snapshots...

Why is CFFI not added as a dependecy such that it is automatically installed?

As a possible first step, could you make it available to the [Extensions installer](https://inkscape.org/develop/extensions/#sharing-your-extension)?