From: Roland Roberts <roland@astrofoto.org>
To: cygwin@cygwin.com
Subject: Re: Windows 7, cygwin > 3.1.4 symlink issue
Date: Thu, 17 Sep 2020 16:27:26 -0400 [thread overview]
Message-ID: <119a2d84-6862-bf96-902a-8a2a07a04dd7@astrofoto.org> (raw)
In-Reply-To: <614223b1-8418-b6f4-3911-55d557cb4728@astrofoto.org>
On 8/24/2020 5:43 PM, Roland Roberts wrote:
> I have one machine, a company machine which makes it hard to post
> details, which is running Windows 7. We run cygwin as our development
> environment for Java, but Java is installed as a Windows program. The
> scripts that do the builds are bash scripts that pull down updated
> code from svn, then run unit tests. All of the cygwin bits work fine,
> but when Java is launched to run the unit tests, it runs into problems
> with reading files that were created as symlinks in cygwin. Note that
> this does *not* happen with cygwin 3.1.4, but does with higher
> versions (up through 3.1.7).
>
> Possibly related, the permissions on installed files is odd if I roll
> back from > 3.1.4 to 3.1.4. The files that were updated with the later
> version can't be deleted. The permissions on, for example, an Emacs
> upgraded under 3.1.6 or 3.1.7 show "Unknown User" when I downgrade
> just cygwin and I can't run it. I have to upgrade cygwin, uninstall
> Emacs, downgrade cygwin then reinstall.
>
> Other users in the company have had their machines upgraded/replaced
> with Windows 10 and don't seem to have this issue. Eventually, mine
> will be replaced as well, but in the meantime, later versions of
> cygwin can't be used.
Okay, I have no idea what form of dyslexia struck me when I wrote all
those version numbers, but I've edited the above since it wasn't 1.x but
3.1.x
roland
next prev parent reply other threads:[~2020-09-17 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 21:43 Windows 7, cygwin > 1.4.1 " Roland Roberts
2020-09-17 20:27 ` Roland Roberts [this message]
2020-09-17 21:20 ` Windows 7, cygwin > 3.1.4 " Ken Brown
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=119a2d84-6862-bf96-902a-8a2a07a04dd7@astrofoto.org \
--to=roland@astrofoto.org \
--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).