GNU bug report logs - #44631
28.0.50; Byte compilation fails if destination file is a mount point

Previous Next

Full log

Message #25 received at 44631-done <at> debbugs.gnu.org (full text, mbox):

From: Philipp Stephani <p.stephani2 <at> gmail.com>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 44631-done <at> debbugs.gnu.org
Subject: Re: bug#44631: 28.0.50; Byte compilation fails if destination file is
 a mount point
Date: Sun, 13 Dec 2020 17:41:55 +0100

Am So., 13. Dez. 2020 um 13:32 Uhr schrieb Lars Ingebrigtsen <larsi <at> gnus.org>:
>
> Philipp Stephani <p.stephani2 <at> gmail.com> writes:
>
> > I guess it also depends on what the semantics are that
> > byte-compile-file guarantees. If it attempts to guarantee atomicity,
> > then only a intra-filesystem rename (or similar alternatives such as
> > O_TMPFILE + linkat) are acceptable, and technically, not even the
> > current fallback on EXDEV (which makes rename-file nonatomic) is OK.
> > If atomic writes are best-effort, then we could always fall back to
> > copy-file + delete-file on any file-error.
>
> It's definitely best-effort, so altering byte-compile-file to try
> copy-file + delete-file sounds like the best solution to me.

I've now pushed a slightly different fix to master (commit
fe50a8b9ba79b4ac14a3a352d8bf84eaee4f2122).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.