Bug#1108072: darktable: db backup file has 0200 permision

[David Bremner]

Control: tag -1 fixed-upstream, tag -1 confirmed

Greg Schmidt <greg at gwschmidt.com> writes:

> My umask is ok, and i have several database files and they are not at 
> the default location. To reproduce the problem try this.
>
> mkdir dtdir
>
>      darktable --library dtdir/lib.db --cachedir dtdir/cache --configdir 
> dtdir
>
> I took a look at the change history and see the following changes. One 
> of which changed the permissions on the empty backup file from S_IRUSR 
> to S_IWUSR.
>
> The unreadable file can not be backed up.

Thanks for the reproducer. It seems  this happens only for empty backup
files.

Upstream has fixed this in the master branch [1]. I guess it will be in
the next stable release of Darktable. We can probably backport the
commit to Debian, but I'm not sure if the bug is severe enough for a
freeze exception.

[1]: https://github.com/darktable-org/darktable/commit/d8c060354ac3d37f5f668c34d636ad08c0eb570f