saving attachment on sshfs-mounted volume results in fopen error

2015-06-17 Thread Peter P.
Hi mutt and friends

when I try to save an attachment from within mutt to a directory that is
mounted on an sshfs volume, mutt tells me that
fopen: File exists (errno = 17)
and writes an empty file with the correct name to that location.
It then offers to save the file to the same path/filename which
obviously results in the message
File exists, (o)verwrite, (a)ppend, or (c)ancel?

Is this behavior known, is it only me (Debian testing mutt package,
Version 1.5.23) and what could I do to help enabling saving attachments
to such volumes?

thx
P


Re: saving attachment on sshfs-mounted volume results in fopen error

2015-06-17 Thread Peter P.
* Peter P.  [2015-06-17 13:04]:
> Hi mutt and friends
> 
> when I try to save an attachment from within mutt to a directory that is
> mounted on an sshfs volume, mutt tells me that
>   fopen: File exists (errno = 17)
> and writes an empty file with the correct name to that location.
> It then offers to save the file to the same path/filename which
> obviously results in the message
>   File exists, (o)verwrite, (a)ppend, or (c)ancel?
> 
> Is this behavior known, is it only me (Debian testing mutt package,
> Version 1.5.23) and what could I do to help enabling saving attachments
> to such volumes?

Excuse me list, I could have had made my homework though first.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670926
This report claims that it is an sshfs bug that was fixed in the current
version of sshfs on Debian testing, so I have gotten in contact with the
sshfs maintainers/developers.

Sorry for the noise.
P