On 22/09/2022 18:14, Achim Gratz wrote:
The release_2.91 comes with another regression that still puzzles me.
In a nutshell, the three commits that deal with setting up the groups
during / after installation
2022-08-27 Jon Turney Drop setting root_scope as a side-effect of
read_mounts()
2022-08-16 Jon Turney Defer setting group until after All Users/Just
For...
2022-08-16 Jon Turney Drop group change while running postinstall
scripts
break existing installs in certain circumstances that are not yet
completely clear. The server installation @work (which uses exactly the
same scripting around the installation that I use for my build system
@home) changed from using the "Domain Users" group to "Administrators".
Additionally the previous access for "Everyone" has been removed and
instead SYSTEM is now part of the (Windows) ACL. In effect certain
files have become inaccessible to the normal users (unless they are aso
Administrators), in particular (this is the part that I still don't
understand) newly created symlinks can't be read by a normal user even
when the target is fully accessible. Even doing an ls on such a symlink
gets a "permission denied".
This problem is with files created by setup, or by post-install scripts?
(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...)
