From: Rainer Emrich <rainer-lists@emrich-ebersheim.de>
To: Jon Turney <jon.turney@dronecode.org.uk>,
Doug Henderson <djndnbvg@gmail.com>,
The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] Updated: setup (2.911)
Date: Fri, 31 Dec 2021 16:02:31 +0100 [thread overview]
Message-ID: <f582e76f-ea06-4d59-d555-97a7b24dbf6a@emrich-ebersheim.de> (raw)
In-Reply-To: <f4d57960-3a09-8b7c-ce60-6e80ff788ee8@dronecode.org.uk>
Hi Jon,
Am 31.12.2021 um 15:38 schrieb Jon Turney:
> On 30/12/2021 18:38, Doug Henderson wrote:
>> On Thu, 30 Dec 2021 at 09:46, Rainer Emrich
>> <rainer-lists@emrich-ebersheim.de> wrote:
>>>
>>> Hi Jon,
>>> for me the new setup executables do not work, same for both:
>>
>> In my analysis, setup is reporting for a non-elevated shell:
>>
>> $ ./setup-x86_64
>> User has NO backup/restore rights
>> User has symlink creation right
>> note: Hand installation over to elevated child process.
>>
>> for an elevated shell:
>>
>> $ ./setup-x86_64
>> Starting cygwin install, version 2.911
>> User has backup/restore rights
>> User has symlink creation right
>> *** --symlink-type native requires SeCreateSymbolicLink privilege or
>> 'Developer Mode'
>>
> [...]
>
>> I do not have 'Developer Mode' enabled as it is overkill unless
>> necessary.
>>
>> I suspect that setup-x86_64.exe is not correctly checking for the
>> "SeCreateSymbolicLink" and/or "Create symbolic links" permission.
>
> Thanks! Yes, there's a few things wrong with how that permission is
> detected and it's presence reported.
>
> I've uploaded setup 2.912 with an attempted fix.
>
> https://cygwin.com/setup/setup-2.912.x86_64.exe
> https://cygwin.com/setup/setup-2.912.x86.exe
>
> Please try that, and see if it improves things for you?
first impression this version works as expected.
Thanks for all your hard work!
next prev parent reply other threads:[~2021-12-31 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 15:58 Jon Turney
2021-12-30 16:45 ` Rainer Emrich
2021-12-30 17:38 ` Jon Turney
2021-12-30 18:31 ` Rainer Emrich
2021-12-30 19:04 ` Rainer Emrich
2021-12-30 18:38 ` Doug Henderson
2021-12-31 14:38 ` Jon Turney
2021-12-31 15:02 ` Rainer Emrich [this message]
2022-01-01 14:15 ` © Fxzx mic
2022-01-01 15:14 ` Marco Atzeri
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=f582e76f-ea06-4d59-d555-97a7b24dbf6a@emrich-ebersheim.de \
--to=rainer-lists@emrich-ebersheim.de \
--cc=cygwin@cygwin.com \
--cc=djndnbvg@gmail.com \
--cc=jon.turney@dronecode.org.uk \
/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).