From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [Bug] setup regression #2
Date: Mon, 03 Oct 2022 21:23:36 +0200 [thread overview]
Message-ID: <877d1gd83r.fsf@Rainer.invalid> (raw)
In-Reply-To: <0c8c757c-4f6b-3b49-5404-99353de48b1b@dronecode.org.uk> (Jon Turney's message of "Sat, 1 Oct 2022 16:37:15 +0100")
Jon Turney writes:
> This problem is with files created by setup, or by post-install scripts?
I think both, although the problematic symlinks were created through
alternatives.
> (I'm not sure how these commits could have caused the former, if the
> latter then reverting 45d8e84e "Drop group change while running
> postinstall scripts" would be the thing to try...)
As I said, I don't understand it either. It seems my installations were
all using the primary group for the account that does the install (which
does have administrative rights and is separate from my normal user
account on most machines). The primary group is either "None" for the
build machine that only uses local accounts and is not a member of any
domain or "Domain Users" otherwise.
The new code uses "Administrators", but that seems to have the side
effect of denying "normal" users access to the installation and instead
weaves in extra DACL for SYSTEM.
As long as there's an option to force it to keep the former behaviour
things should be OK, but I haven't really checked if and how this is
possible.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
SD adaptations for KORG EX-800 and Poly-800MkII V0.9:
http://Synth.Stromeko.net/Downloads.html#KorgSDada
next prev parent reply other threads:[~2022-10-03 19:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 17:14 Achim Gratz
2022-10-01 15:37 ` Jon Turney
2022-10-03 19:23 ` Achim Gratz [this message]
2022-10-08 15:18 ` Jon Turney
2022-10-08 16:56 ` Achim Gratz
2022-11-08 16:21 ` Jon Turney
2022-11-09 18:25 ` Achim Gratz
2022-11-13 12:47 ` Achim Gratz
2022-11-20 17:16 ` Jon Turney
2022-11-20 19:05 ` Achim Gratz
2022-11-21 12:32 ` Corinna Vinschen
2022-11-21 12:39 ` ASSI
2022-11-21 12:47 ` Corinna Vinschen
2022-11-29 21:37 ` Jon Turney
2022-11-30 21:22 ` Christian Franke
2022-12-01 19:50 ` Achim Gratz
2023-02-02 16:00 ` Jon Turney
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=877d1gd83r.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--cc=cygwin-apps@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).