GNU bug report logs -
#27959
26.0.50; File renaming fails on sshfs
Previous Next
Reported by: Lars Ingebrigtsen <larsi <at> gnus.org>
Date: Fri, 4 Aug 2017 21:39:02 UTC
Severity: normal
Found in version 26.0.50
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Lars Ingebrigtsen <larsi <at> gnus.org> schrieb am Fr., 4. Aug. 2017 um
23:39 Uhr:
>
> /tv is mounted via sshfs.
>
> (rename-file "/tv/a.foo" "/tv/b.foo")
>
> Debugger entered--Lisp error: (file-error "Renaming" "Invalid argument"
> "/tv/a.foo" "/tv/b.foo")
> rename-file("/tv/a.foo" "/tv/b.foo")
> eval((rename-file "/tv/a.foo" "/tv/b.foo") nil)
> eval-expression((rename-file "/tv/a.foo" "/tv/b.foo") nil nil 127)
> funcall-interactively(eval-expression (rename-file "/tv/a.foo"
> "/tv/b.foo") nil nil 127)
> call-interactively(eval-expression nil nil)
> command-execute(eval-expression)
>
> But if I say
>
> larsi <at> amy:~$ mv /tv/a.foo /tv/b.foo
>
> on the same machine, it works fine. So ... where is the "Invalid
> argument" coming from?
>
Probably more fallout of 1f9f514e7c2ba41b0954d0141f99652f6a53a107. Does it
work if you compile without that commit (e.g. git reset --hard
1f9f514e7c2ba41b0954d0141f99652f6a53a107^ from a clean working directory)?
[Message part 2 (text/html, inline)]
This bug report was last modified 7 years and 297 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.