cygwin permissions on folders creating problems for windows applications (like explorer, gvim)

2020-09-08 Thread L A Walsh
I was trying to edit files in /etc/ssh: /etc/ssh> gvim sshd_config Error: Current working directory has restricted permissions which render it inaccessible as Win32 working directory. Ca

Re: ag 2 <(echo 2) gets assertion "p >= path" failed: .. /cygwin-3.1.7 ... /cygwin/path.cc", line 3065, function: int symlink_info::check

2020-09-08 Thread David Dyck via Cygwin
ot;/dev/fd/%d/foo", fd[0]); > >>if (open (fname, O_RDONLY) < 0) > >> { > >>perror ("open"); > >>exit (1); > >> } > >> } > >> > >> $ gcc -o proc_bug proc_bug.c > >> > &g

[ANNOUNCEMENT] New: unison2.48+4.04.2, unison2.48+4.08.1 [test]

2020-09-08 Thread Andrew Schulman via Cygwin-announce
Two new Unison packages are now available in test: unison2.48+4.04.2 unison2.48+4.08.1 Both of these are Unison 2.48.4, but compiled with OCaml 4.04.2 and 4.08.1, respectively. For the reasons explained below, we now need separate Unison packages for compatible versions of both Unison and OCaml.

Re: ag 2 <(echo 2) gets assertion "p >= path" failed: .. /cygwin-3.1.7 ... /cygwin/path.cc", line 3065, function: int symlink_info::check

2020-09-08 Thread Ken Brown via Cygwin
On 9/8/2020 3:26 PM, Ken Brown via Cygwin wrote: On 9/7/2020 4:35 PM, Ken Brown via Cygwin wrote: On 9/6/2020 4:28 PM, Ken Brown via Cygwin wrote: On 9/6/2020 3:47 PM, Ken Brown via Cygwin wrote: On 9/6/2020 2:43 PM, David Dyck via Cygwin wrote: This command triggers an assertion failure    "

Re: ag 2 <(echo 2) gets assertion "p >= path" failed: .. /cygwin-3.1.7 ... /cygwin/path.cc", line 3065, function: int symlink_info::check

2020-09-08 Thread Ken Brown via Cygwin
On 9/7/2020 4:35 PM, Ken Brown via Cygwin wrote: On 9/6/2020 4:28 PM, Ken Brown via Cygwin wrote: On 9/6/2020 3:47 PM, Ken Brown via Cygwin wrote: On 9/6/2020 2:43 PM, David Dyck via Cygwin wrote: This command triggers an assertion failure    "ag" is from the_silver_searcher $ ag 2 <(echo 2)

Re: cygwin1.dll: uname_x not found

2020-09-08 Thread Corinna Vinschen
On Sep 8 21:21, Corinna Vinschen wrote: > On Sep 8 11:28, L A Walsh wrote: > > > > > > On 9/8/2020 12:18 AM, Corinna Vinschen wrote: > > > On Sep 7 14:34, L A Walsh wrote: > > >>> I uploaded new snapshots for testing to https://cygwin.com/snapshots/ > > >>> > > >>> Please give them a try. > >

Re: cygwin1.dll: uname_x not found

2020-09-08 Thread Corinna Vinschen
On Sep 8 11:28, L A Walsh wrote: > > > On 9/8/2020 12:18 AM, Corinna Vinschen wrote: > > On Sep 7 14:34, L A Walsh wrote: > >>> I uploaded new snapshots for testing to https://cygwin.com/snapshots/ > >>> > >>> Please give them a try. > >> --- > >> Got: > >> > >> "The procedure entry point uname

Re: cygwin1.dll: uname_x not found

2020-09-08 Thread Corinna Vinschen
On Sep 8 20:47, Thomas Wolff wrote: > > > Am 08.09.2020 um 20:28 schrieb L A Walsh: > > > > On 9/8/2020 12:18 AM, Corinna Vinschen wrote: > > > On Sep 7 14:34, L A Walsh wrote: > > > > > I uploaded new snapshots for testing to https://cygwin.com/snapshots/ > > > > > > > > > > Please give them

Re: cygwin1.dll: uname_x not found

2020-09-08 Thread Thomas Wolff
Am 08.09.2020 um 20:28 schrieb L A Walsh: On 9/8/2020 12:18 AM, Corinna Vinschen wrote: On Sep 7 14:34, L A Walsh wrote: I uploaded new snapshots for testing to https://cygwin.com/snapshots/ Please give them a try. For me, the snapshot dll fixes the issue I observed. Thomas --- Got: "

Re: Bash 4.4.12-3 erroneous behavior using [[ -f name ]] and other utilities

2020-09-08 Thread L A Walsh
What are you complaining about? What erroneous behavior? We can't read your mind, but it isn't clear what you think is going wrong -- so how are we supposed to figure out what the erroneous behavior is? Please give an example of what you think is wrong and what you expected instead. Please be cl

Re: cygwin1.dll: uname_x not found

2020-09-08 Thread L A Walsh
On 9/8/2020 12:18 AM, Corinna Vinschen wrote: > On Sep 7 14:34, L A Walsh wrote: >>> I uploaded new snapshots for testing to https://cygwin.com/snapshots/ >>> >>> Please give them a try. >> --- >> Got: >> >> "The procedure entry point uname_x could not be located in the dynamic >> link library

Re: Bash 4.4.12-3 erroneous behavior using [[ -f name ]] and other utilities

2020-09-08 Thread Brian Inglis
On 2020-09-08 10:22, Brian Inglis wrote: > On 2020-09-08 00:24, johnb...@email.com wrote: > You are demonstrating erroneous behaviour. What erroneous behaviour, what other utilities? You need to include your console or terminal log, or a copy and paste of (*relevant* selections of) the input and

Re: Bash 4.4.12-3 erroneous behavior using [[ -f name ]] and other utilities

2020-09-08 Thread Brian Inglis
On 2020-09-08 00:24, johnb...@email.com wrote: > You are demonstrating erroneous behaviour. -- 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. [Data in IEC units and pr

Re: postinstall: fontconfig abnormal exit

2020-09-08 Thread Brian Inglis
On 2020-09-08 09:18, Fergus Daly via Cygwin wrote: >> Greetings, Fergus Daly! > >>> Sorry if this has been asked 4 million times already. >>> During postinstall, both at ground-zero installation and at every update >>> thereafter, and for both Cygwin-32 and -64, >>> (both using the appropriate set

RE: postinstall: fontconfig abnormal exit

2020-09-08 Thread Fergus Daly via Cygwin
> Greetings, Fergus Daly! >> Sorry if this has been asked 4 million times already. >> During postinstall, both at ground-zero installation and at every update >> thereafter, and for both Cygwin-32 and -64, >> (both using the appropriate setup-x86[_64].exe) I get: >> running: {pathToCygwin}\bin\bas

Re: postinstall: fontconfig abnormal exit

2020-09-08 Thread Andrey Repin
Greetings, Fergus Daly! > Sorry if this has been asked 4 million times already. > During postinstall, both at ground-zero installation and at every update > thereafter, and for both Cygwin-32 and -64, > (both using the appropriate setup-x86[_64].exe) I get: > running: {pathToCygwin}\bin\bash.exe -

Re: Linux

2020-09-08 Thread cygwinautoreply--- via Cygwin
>1 [main] ssh 11260 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer >The information contained in this message is proprietary and/or confidential. >If you are not the intended recipient, please: (i) delete the message and all >copies; (ii) do not disclose, distribute or use the message

Linux

2020-09-08 Thread Zektser, Michael P via Cygwin
1 [main] ssh 11260 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in a

[ANNOUNCEMENT] Updated: znc-1.8.2-1

2020-09-08 Thread Alexey Sokolov
Version 1.8.2-1 of "znc" has been uploaded. ZNC is an IRC network bouncer (BNC). It can detach the client from the actual IRC server, and also from selected channels. Multiple clients from different locations can connect to a single ZNC account simultaneously and therefore appear under the same ni

Re: postinstall: fontconfig abnormal exit

2020-09-08 Thread Hamish McIntyre-Bhatty via Cygwin
On 08/09/2020 07:43, Fergus Daly via Cygwin wrote: > Sorry if this has been asked 4 million times already. > During postinstall, both at ground-zero installation and at every update > thereafter, and for both Cygwin-32 and -64, > (both using the appropriate setup-x86[_64].exe) I get: > running: {p

Re: update with apt-cyg ?

2020-09-08 Thread Ulli Horlacher
On Sun 2020-09-06 (19:11), Brian Inglis wrote: > If using unattended (--quiet) mode, you have to specify everything else: > > $ ./setup-x86_64 -gq -R "$rootdir" -l "$pkgdir" -s $site > > otherwise try semi-attended (--package-manager) chooser-only mode: > > $ ./setup-x86_64 -gM -R "

Re: cygwin1.dll: uname_x not found

2020-09-08 Thread Corinna Vinschen
On Sep 7 14:34, L A Walsh wrote: > > > > > I uploaded new snapshots for testing to https://cygwin.com/snapshots/ > > > > Please give them a try. > --- > Got: > > "The procedure entry point uname_x could not be located in the dynamic > link library cygwin1.dll" > > :-( uname_x is exported jus