public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Cygwin installer does not select the packages specified by the -P option
Date: Thu, 08 Aug 2019 00:36:00 -0000	[thread overview]
Message-ID: <1b387ca1-576f-67a6-3537-5fc138520b27@SystematicSw.ab.ca> (raw)
In-Reply-To: <877e7oakbn.fsf@Rainer.invalid>

On 2019-08-07 12:42, Achim Gratz wrote:
> KAVALAGIOS Panagiotis (EEAS-EXT) writes:
>> I have tried the -A option, the -B option as single user to no
>> avail. There is no antivirus running. Well, there is in general in our
>> PCs, but no installed on my test machine. I have also tried another
>> mirror to re-download the packages in a local repository, but it
>> didn't work either. Can you provide your local repo data to check?
> 
> That repo is not public, no.  But if you've mirrored the repo with
> setup.exe (like your directory name seems to suggest), then I don't see
> why the repo structure should be wrong.
> 
>> Just to ensure that my local repo is not the problem.
> 
> Again, check the Windows DACL on the local repo directory down to the
> actual files.  If you have "interesting" inheritable DACL, that can lead
> to lots of fun behaviour.
> 
>>> Again, it should just work the way you were trying, but something's
>>> interfering. 
>>
>> Probably, but I would need more information to prove it. I am
>> suspecting a Windows Group Policy, but I would have to be sure and
>> prove it in order to request the exception from our Windows Team.
> 
> I've been at the receiving end of group policies gone wild, but your
> symptoms don't seem to click with that.  You might try to rename
> setup.exe to something entirely else, lest somebody targeted certain
> program names.
> 
>> I forgot to mention that we are using Windows 7 and I don't know if
>> the setup behaves different on that operating system.
> 
> I still have the odd Win7 box here and there around, I don't think that
> this makes any difference.

The OP's package list include sudo, which does not exist, diffutils and tar,
which are part of base. Should the first not fail setup, and all be omitted for
a retest?

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-08-08  0:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-29 10:14 KAVALAGIOS Panagiotis (EEAS-EXT)
2019-08-01  9:07 ` KAVALAGIOS Panagiotis (EEAS-EXT)
2019-08-01 15:41 ` Jon Turney
2019-08-01 17:30   ` Achim Gratz
2019-08-02  9:19     ` KAVALAGIOS Panagiotis (EEAS-EXT)
2019-08-02 18:49       ` Achim Gratz
2019-08-07 11:46         ` KAVALAGIOS Panagiotis (EEAS-EXT)
2019-08-07 18:42           ` Achim Gratz
2019-08-08  0:36             ` Brian Inglis [this message]
2019-08-08 18:11               ` Achim Gratz
2019-08-19 10:49                 ` KAVALAGIOS Panagiotis (EEAS-EXT)

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=1b387ca1-576f-67a6-3537-5fc138520b27@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).