public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Blaesse, Michael" <blaesse@proteros.de>
To: "'cygwin@cygwin.com'" <cygwin@cygwin.com>
Subject: Re: Errors on installing additional packages
Date: Fri, 18 Aug 2017 13:34:00 -0000	[thread overview]
Message-ID: <6b69c604cbb34b60947020e8fe0cbfba@proteros.de> (raw)

Hello,

Thanks for the answers to my questions and in general the work with Cygwin.
Sorry for the late answer and if this message is not correctly sorted in the right thread. I subscribed to the after sending my first message and recognizing that I don´t get the answers per mail. Thus I cannot answer directly to them.

I installed the new version on a local disc and there it works. Thus, it seems that the ACLs cause the problems. Are there any changes in the newer versions of the setup.exe regarding the ACLs? I am not aware that anything on the network share has changed and I have used it for several Cygwin versions in the past. 
Using a network share has the big advantage, that it can be used from any user with the appropriate permissions on any computer in the company reducing the administration effort a lot, e.g. for GIMP, software for crystallographie, some useful shell or perl scripts, etc.
As the installed version on the network share works (only setup.exe does not install new packages) , I will try to sync that installation with the local one.

Best regards,
Michael Blaesse


--
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:[~2017-08-18 13:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-18 13:34 Blaesse, Michael [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-08-10  8:14 Blaesse, Michael
2017-08-10 12:14 ` cyg Simple
2017-08-10 17:46 ` Achim Gratz

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=6b69c604cbb34b60947020e8fe0cbfba@proteros.de \
    --to=blaesse@proteros.de \
    --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).