From: ngraves--- via Guix-patches via <guix-patches@gnu.org>
To: 74872@debbugs.gnu.org
Subject: [bug#74872] bugfix: update symlinks
Date: Sat, 14 Dec 2024 17:49:51 +0100 [thread overview]
Message-ID: <8f00e019e47cc41d4c85a524908d63aa@ngraves.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 353 bytes --]
For some reason, rename-file fails when the target and destination are
not in the same filesystem. However, we can't assume for the
update-symlink script that all users will always have e.g.
~/.local/share/applications (managed by guix-home) and ~ on the same
filesystem. My use-case is trying to implement home impermanence. The
patch is attached.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-home-Replace-rename-in-update-symlinks-scripts.patch --]
[-- Type: text/x-diff; name=0001-gnu-home-Replace-rename-in-update-symlinks-scripts.patch, Size: 1159 bytes --]
From fe07066b88556c3755db3fc29665ce93d23cc071 Mon Sep 17 00:00:00 2001
From: Nicolas Graves <ngraves@ngraves.fr>
Date: Sat, 14 Dec 2024 12:38:14 +0100
Subject: [PATCH] gnu: home: Replace rename in update-symlinks scripts.
* gnu/home/services/symlink-manager.scm (update-symlinks): Use
copy-file and delete-file instead of rename-file to avoid an error
when the target and backup are not in the same filesystem.
---
gnu/home/services/symlink-manager.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gnu/home/services/symlink-manager.scm b/gnu/home/services/symlink-manager.scm
index 560e03a839..d7b22d7fba 100644
--- a/gnu/home/services/symlink-manager.scm
+++ b/gnu/home/services/symlink-manager.scm
@@ -106,7 +106,8 @@ (define backup
(mkdir-p backup-directory)
(format #t (G_ "Backing up ~a...") (target-file file))
(mkdir-p (dirname backup))
- (rename-file (target-file file) backup)
+ (copy-file (target-file file) backup)
+ (delete-file (target-file file))
(display (G_ " done\n")))
(define (cleanup-symlinks home-generation)
--
2.46.0
reply other threads:[~2024-12-14 16:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8f00e019e47cc41d4c85a524908d63aa@ngraves.fr \
--to=guix-patches@gnu.org \
--cc=74872@debbugs.gnu.org \
--cc=ngraves@ngraves.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).