From: Christian Franke <Christian.Franke@t-online.de>
To: Andrew Schulman <schulman.andrew@epa.gov>, cygwin@cygwin.com
Subject: Re: fish-3.5.0-1: /etc/fish/conf.d/cygwin.fish only readable by owner
Date: Mon, 24 Oct 2022 11:43:59 +0200 [thread overview]
Message-ID: <381d29c0-222b-21fd-a5dd-d450f4a2b0b4@t-online.de> (raw)
In-Reply-To: <afatkhhpon22ctrm85djcq9jv12k09cjle@4ax.com>
Andrew Schulman via Cygwin wrote:
>> The permission of cygwin.fish looks somewhat random (depends on umask
>> during build?):
>>
>> $ tar tvf fish-3.4.1-1.tar.xz etc/defaults/etc/fish/conf.d/cygwin.fish
>> -rw-r-xr-- ... 1101 2022-04-07 20:34
>> etc/defaults/etc/fish/conf.d/cygwin.fish
>>
>> $ tar tvf fish-3.5.0-1.tar.xz etc/defaults/etc/fish/conf.d/cygwin.fish
>> -rw------- ... 1101 2022-06-29 17:29
>> etc/defaults/etc/fish/conf.d/cygwin.fish
> Hi Christian. Thanks for reporting this, and sorry for my slow reply. I was
> suprprised by this, because I thought setup would set up rational permissions
> for us. I've just come to expect that permissions on my Cygwin files get set to
> screwy values, and I thought that setup was fixing them up for us.
setup sets the permissions as specified in the tar file.
> Anyway I fixed the permissions in version 3.5.1-2, which I just uploaded. Once
> you update to that version, please let me know if everything looks okay again.
Looks good, permissions are now -rw-r--r--.
--
Regards,
Christian
prev parent reply other threads:[~2022-10-24 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 17:17 Christian Franke
2022-10-18 17:54 ` Andrew Schulman
2022-10-24 9:43 ` Christian Franke [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=381d29c0-222b-21fd-a5dd-d450f4a2b0b4@t-online.de \
--to=christian.franke@t-online.de \
--cc=cygwin@cygwin.com \
--cc=schulman.andrew@epa.gov \
/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.
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).