public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christian Franke <Christian.Franke@t-online.de>
To: cygwin@cygwin.com
Subject: fish-3.5.0-1: /etc/fish/conf.d/cygwin.fish only readable by owner
Date: Sat, 2 Jul 2022 19:17:11 +0200	[thread overview]
Message-ID: <40463b39-cd3b-00c2-a833-07ef5cbe2c51@t-online.de> (raw)

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



BTW: Easily found during testing of new setup rc 2.920 with etckeeper 
installed:

$ etckeeper vcs log -1
...
     committing changes in /etc after cygwin-setup run

     Packages with configuration changes:
     -fish 3.4.1-1
     +fish 3.5.0-1

     Package changes:
     -fish 3.4.1-1
     +fish 3.5.0-1

$ etckeeper vcs diff --stat HEAD^
  .etckeeper                           | 4 ++--
  defaults/etc/fish/conf.d/cygwin.fish | 0
  fish/conf.d/cygwin.fish              | 0
  setup/installed.db                   | 2 +-
  4 files changed, 3 insertions(+), 3 deletions(-)

$ etckeeper vcs diff HEAD^ .etckeeper
...
-maybe chmod 0754 'defaults/etc/fish/conf.d/cygwin.fish'
+maybe chmod 0600 'defaults/etc/fish/conf.d/cygwin.fish'
...
-maybe chmod 0754 'fish/conf.d/cygwin.fish'
+maybe chmod 0600 'fish/conf.d/cygwin.fish'
...


-- 
Regards,
Christian


             reply	other threads:[~2022-07-02 17:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-02 17:17 Christian Franke [this message]
2022-10-18 17:54 ` Andrew Schulman
2022-10-24  9:43   ` Christian Franke

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=40463b39-cd3b-00c2-a833-07ef5cbe2c51@t-online.de \
    --to=christian.franke@t-online.de \
    --cc=cygwin@cygwin.com \
    /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).