From: Jon Turney <jon.turney@dronecode.org.uk>
To: "cygwin-apps@cygwin.com" <cygwin-apps@cygwin.com>
Subject: Re: [Bug] setup regression #2
Date: Thu, 2 Feb 2023 16:00:17 +0000 [thread overview]
Message-ID: <c99b5587-1cdd-b6e2-ac6b-67f009a04a83@dronecode.org.uk> (raw)
In-Reply-To: <ecb9e196-4941-f8c2-0993-4f66054e8a83@dronecode.org.uk>
On 20/11/2022 17:16, Jon Turney wrote:
> On 13/11/2022 12:47, Achim Gratz wrote:
>> The problem is actually a more knotty than you seem to think:
>> prominently ca-certificates and man-db get their knickers in a twist
>> when the group during post-install is different from the group of the
>> installed files and I suspect some other packages will run into similar
>> problems depending on how fussy they are with the group permissions.
>
> I take it seriously, otherwise I would have just released a setup with
> those changes.
>
> I've reverted them for the moment, since I want to do a setup release
> now for other reasons.
I've reapplied these changes in the latest RC, since I'm assuming the
problem(s) here are resolved as of [1], but it's very difficult to tell.
[1]
https://cygwin.com/git/?p=newlib-cygwin.git;a=commit;h=a5bcfe616c7e8f78f464bf045595d8213244876a
prev parent reply other threads:[~2023-02-02 16:00 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
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 [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=c99b5587-1cdd-b6e2-ac6b-67f009a04a83@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--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).