From: Reza Alizadeh Majd <r.majd@pantherx.org>
To: 44463@debbugs.gnu.org
Subject: bug#44463: Skeleton files in sub-directories are not writable
Date: Thu, 5 Nov 2020 14:14:37 +0330 [thread overview]
Message-ID: <20201105141437.486402c9@pantherx.org> (raw)
Hi Guix,
trying to add a new skeleton file in a sub-directory in newly created
users home, skeleton files add in read-only mode.
since there shouldn't be any difference between adding a skeleton file
in user home directory, or in a sub-directory under user's home, I
assume this might be a bug related to skeleton file creation.
following configuration could be used to reproduce this issue:
--8<---------------cut here---------------start------------->8---
(use-modules (gnu))
(define (test-skeletons)
(append
`(("test" ,(computed-file
"test"
(with-imported-modules '((guix build utils))
#~(begin
(use-modules (guix build utils))
(mkdir-p #$output)))))
("foo" ,(plain-file "foo" "foo is writable"))
("test/bar" ,(plain-file "bar" "bar is read-only")))
(default-skeletons)))
(operating-system
(host-name "guix.test")
(timezone "Asia/Tehran")
(locale "en_US.utf8")
(bootloader (bootloader-configuration
(bootloader grub-bootloader)
(target "/dev/sda")))
(file-systems (cons (file-system
(device (file-system-label "my-root"))
(mount-point "/")
(type "ext4"))
%base-file-systems))
(skeletons (test-skeletons)))
--8<---------------cut here---------------end--------------->8---
generated skeleton files status:
--8<---------------cut here---------------start------------->8---
root@guix ~# ll
total 4
-rw-r--r-- 1 root root 15 Nov 5 14:05 foo
-rw-r--r-- 2 root root 15 Nov 5 14:05 test/
root@guix ~# ll
-r--r--r-- 1 root root 15 Nov 5 14:05 bar
--8<---------------cut here---------------end--------------->8---
Regards,
Reza
--
Reza Alizadeh Majd
PantherX Team
https://www.pantherx.org/
reply other threads:[~2020-11-05 11:45 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=20201105141437.486402c9@pantherx.org \
--to=r.majd@pantherx.org \
--cc=44463@debbugs.gnu.org \
/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).