From: "Thompson, David" <dthompson2@worcester.edu>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 56444@debbugs.gnu.org
Subject: bug#56444: Patch to fix Gitolite home directory permissions
Date: Mon, 29 Aug 2022 08:49:54 -0400 [thread overview]
Message-ID: <CAJ=RwfYw+uoxcjUW_AyHmYnyrUOSCw-3uNs8peopF1skgFRZxg@mail.gmail.com> (raw)
In-Reply-To: <CAJ=RwfaQvY=AT+_sDwGy3tkPEkekGt-djEjPuztFb+4QuYpFZg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 922 bytes --]
Hi again Maxime,
What do you think of my proposal? Do any other maintainers care to chime
in here?
- Dave
On Tue, Aug 23, 2022 at 10:45 AM Thompson, David <dthompson2@worcester.edu>
wrote:
> Hi Maxime,
>
> On Tue, Aug 23, 2022, 8:41 AM Maxime Devos <maximedevos@telenet.be> wrote:
>
>>
>> During "guix system reconfigure", there is now window where the
>> directory temporarily has incorrect bits and hence if gitolite is
>> restarted during that time it will presumably fail. Could a
>> 'home-permission-bits' or such field be added instead to <user-account>
>> to make things atomic?
>>
>
> That would be a nice improvement to backlog now that such a use case has
> emerged. However, I think for our immediate needs this one line patch,
> while imperfect, solves a longstanding problem adequately. So how about
> merging it, closing this bug, and opening a new bug for the system level
> improvement?
>
> - Dave
>
[-- Attachment #2: Type: text/html, Size: 1778 bytes --]
next prev parent reply other threads:[~2022-08-29 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 21:35 bug#56444: Gitolite home directory permissions Evgeny Pisemsky
[not found] ` <handler.56444.B.165722972531874.ack@debbugs.gnu.org>
2022-07-08 8:10 ` bug#56444: Acknowledgement (Gitolite home directory permissions) Evgeny Pisemsky
2022-08-19 13:32 ` bug#56444: Patch to fix Gitolite home directory permissions Thompson, David
2022-08-23 12:41 ` Maxime Devos
2022-08-23 14:45 ` Thompson, David
2022-08-29 12:49 ` Thompson, David [this message]
2022-08-29 12:52 ` Maxime Devos
2022-08-29 12:57 ` bug#56444: [EXT] " Thompson, David
2022-08-29 13:09 ` Maxime Devos
2022-08-29 13:11 ` Maxime Devos
2022-08-29 13:19 ` Maxime Devos
2022-08-29 13:30 ` bug#56444: [EXT] " Thompson, David
2022-08-29 13:44 ` Maxime Devos
2022-08-29 13:59 ` bug#56444: [EXT] " Thompson, David
2022-08-29 21:05 ` zimoun
2022-08-30 15:20 ` bug#56444: " Ludovic Courtès
2022-08-30 16:39 ` bug#56444: [EXT] " Thompson, David
2022-08-30 18:31 ` david larsson
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='CAJ=RwfYw+uoxcjUW_AyHmYnyrUOSCw-3uNs8peopF1skgFRZxg@mail.gmail.com' \
--to=dthompson2@worcester.edu \
--cc=56444@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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).