On 2024-04-17 13:37, Jon Turney via Cygwin-apps wrote:
On 17/04/2024 15:17, Brian Inglis via Cygwin-apps wrote:
On 2024-04-17 07:08, cygwin-no-reply wrote:
ERROR: package 'geoipupdate' is at paths geoipupdate and
GeoIP-database/geoipupdate
This is the "change things to that the geoipu
lftp sftp://cygwin:@cygwin.com
cd: Access failed: No such file (/x86_64/release)
*** ERROR: Upload failed
Thanks for reporting this.
When I connect using `lftp sftp://cygwin` I now seem to be logged in to the
sftp *root* instead of /home/Brian\ Inglis!
But in future, if you are ever reporti
iled: No such file (/x86_64/release)
*** ERROR: Upload failed
Thanks for reporting this.
When I connect using `lftp sftp://cygwin` I now seem to be logged in to
the sftp *root* instead of /home/Brian\ Inglis!
But in future, if you are ever reporting "I think I have access to stuff
on sour
On 17/04/2024 15:17, Brian Inglis via Cygwin-apps wrote:
On 2024-04-17 07:08,
cygwin-no-reply-rdbxbdvo6bxqt0dzr+a...@public.gmane.org wrote:
ERROR: package 'geoipupdate' is at paths geoipupdate and
GeoIP-database/geoipupdate
This is the "change things to that the geoipupdate package be
Hi folks,
Fairly straightforward upgrade of packages.
Is anything demented about my setup:
$ cygport GeoIP.cygport upload
>>> Uploading GeoIP-1.7.0-1.x86_64
>>> Running lftp sftp://cygwin:@cygwin.com
cd: Access failed: No such file (/x86_64/release)
*** ERROR: Upload fail
On 2024-04-17 07:08, cygwin-no-re...@cygwin.com wrote:
ERROR: package 'geoipupdate' is at paths geoipupdate and
GeoIP-database/geoipupdate
ERROR: error while merging uploaded x86_64 packages for Brian Inglis
SUMMARY: 2 ERROR(s)
Hi folks/Jon,
Replacing obsolete compiled geoipupdate package
---
libgetopt++/include/getopt++/DefaultFormatter.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/libgetopt++/include/getopt++/DefaultFormatter.h
b/libgetopt++/include/getopt++/DefaultFormatter.h
index ee2397f5..43c253a5 100644
--- a/libgetopt++/include/getopt++/DefaultFormatter.h
+++
On 2024-03-24 12:59, Matthias--- via Cygwin wrote:
I downloaded ntfs-3g_ntfsprogs-2022.10.3.tgz from tuxera, extract it and run,
in my cygwin 3.5
environment:
./configure
make ntfsprogs
I got a "fatal error: linux/fd.h: No such file or directory".
All ntfsprogs are build in ~
Hello,
I downloaded ntfs-3g_ntfsprogs-2022.10.3.tgz from tuxera, extract it and run,
in my cygwin 3.5
environment:
./configure
make ntfsprogs
I got a "fatal error: linux/fd.h: No such file or directory".
All ntfsprogs are build in ~/ntfsprogs but not ntfsrecover, nt
On 2024-03-22 09:49, J M wrote:
This is a very painfull and weird failed error of Windows antivirus. I apologize
for not having realized before.
For other people who may encounter this difficult problem, the key to find this
error is (cut connections only for sites that use Letsencrypt
Hi,
This is a very painfull and weird failed error of Windows antivirus. I
apologize for not having realized before.
For other people who may encounter this difficult problem, the key to find
this error is (cut connections only for sites that use Letsencrypt
certificates), is the strace /usr
ck):
$ ldd /usr/bin/curl
ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffadca5)
KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL
(0x7ffadb6d)
KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll
(0x7ffada49)
cygz.d
On 2024-03-19 11:00, J M wrote:
$ file /etc/pki/tls/certs/*
/etc/pki/tls/certs/ca-bundle.crt: symbolic link to
/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem
/etc/pki/tls/certs/ca-bundle.trust.crt: symbolic link to
/etc/pki/ca-trust/extracted/openssl/ca-bundle.trust.crt
$ grep -c
On 2024-03-19 08:02, ASSI via Cygwin wrote:
J M via Cygwin writes:
$ curl - -O https://cygwin.com/setup-x86_64.exe
% Total% Received % Xferd Average Speed TimeTime Time
Current
Dload Upload Total SpentLeft
Speed
0 0
J M via Cygwin writes:
> $ curl - -O https://cygwin.com/setup-x86_64.exe
> % Total% Received % Xferd Average Speed TimeTime Time
> Current
> Dload Upload Total SpentLeft
> Speed
> 0 00 00 0 0 0
2>
El lun, 18 mar 2024 a las 23:19, Brian Inglis via Cygwin ()
escribió:
> On 2024-03-18 15:21, J M via Cygwin wrote:
> > With a fresh install of Cygwin then I launch (with package curl
> installed):
> >
> > curl -O https://www.cygwin.com/setup-x86_64.exe
> &
On 2024-03-18 15:21, J M via Cygwin wrote:
With a fresh install of Cygwin then I launch (with package curl installed):
curl -O https://www.cygwin.com/setup-x86_64.exe
Shows a curl 60 error ssl problem.
Using -k or --insecure works, but is not recomended.
Howto fix it?
WJFFM!
That error
Hi,
With a fresh install of Cygwin then I launch (with package curl installed):
curl -O https://www.cygwin.com/setup-x86_64.exe
Shows a curl 60 error ssl problem.
Using -k or --insecure works, but is not recomended.
Howto fix it?
Regards,
Cesar Jorge
--
Problem reports: https
On 23/02/2024 12:09, Christian Franke via Cygwin-apps wrote:
Harmless bug ...
Applied. Thanks.
; >> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
> >> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
> >> GNU make 4.4.1-2, when it starts external processes and those external
> >> processes exit with a
>> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
>> GNU make 4.4.1-2, when it starts external processes and those external
>> processes exit with a zero exit code.
>>
>> For example, a very simple Makefile:
>>
>> all:
On Feb 26 17:34, Dimitry Andric via Cygwin wrote:
> Hi,
>
> After a recent upgrade of a Cygwin installation, including cygwin1.dll
> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's co
i,
>>>> After a recent upgrade of a Cygwin installation, including cygwin1.dll
>>>> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
>>>> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
>>>> GNU make 4.4
-February/255308.html) to
3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
GNU make 4.4.1-2, when it starts external processes and those external
processes exit with a zero exit code.
For example, a very simple Makefile:
all:
cmd /c echo done
Running this a few times i
to
>> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
>> GNU make 4.4.1-2, when it starts external processes and those external
>> processes exit with a zero exit code.
>> For example, a very simple Makefile:
>> all:
>> cmd /
On 26/02/2024 17:34, Dimitry Andric via Cygwin wrote:
Hi,
After a recent upgrade of a Cygwin installation, including cygwin1.dll
(see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
GNU make 4.4
Hi,
After a recent upgrade of a Cygwin installation, including cygwin1.dll
(see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
GNU make 4.4.1-2, when it starts external processes and thos
Harmless bug ...
--
Regards,
Christian
From b1074f4cfe549c852be7fa59d85d312c9579cf0d Mon Sep 17 00:00:00 2001
From: Christian Franke
Date: Fri, 23 Feb 2024 13:04:21 +0100
Subject: [PATCH] Fix variable expansion in error message of embedded SMTP perl
script
---
lib/pkg_upload.cygpart | 2
On Thu, 22 Feb 2024, Takashi Yano wrote:
> On Thu, 22 Feb 2024 11:46:39 +0530 (IST) Satish Balay wrote:
> > With cygwin upgrade to 3.5.0-1 - I'm not seeing "error return codes" on
> > compile failures.
> Thanks for the report.
> This bug has already has
in upgrade to 3.5.0-1 - I'm not seeing "error return codes" on
> compile failures.
>
> However - this works again after downgrading to 3.4.10-1.
>
> Note: This works with 3.5.0-1 - if I use 'mintty' - instead of 'cygwin.bat'
> or 'bash --login' from 'Compiler
Usage: Invoke 'cl' from cygwin/bash. i.e:
- run 'Visual Studio CMD' to setup MS compilers in dos shell
- run 'c:\cygwin64\cygwin.bat' [or 'c:\cygwin64\bin\bash --login']
- run 'cl /c test.c'
With cygwin upgrade to 3.5.0-1 - I'm not seeing "error return codes" on compile
failures
On Sun, Feb 18, 2024 at 3:40 PM Cary Lewis via Cygwin wrote:
>
> Attempting to run:
>
> openssl enc -base64 -i file
>
> gives the following error:
>
> 42949672976:error:25066067:DSO support routines:dlfcn_load:could not load
> the shared library:crypto/d
Attempting to run:
openssl enc -base64 -i file
gives the following error:
42949672976:error:25066067:DSO support routines:dlfcn_load:could not load
the shared library:crypto/dso/dso_dlfcn.c:118:filename(libproviders.dll):
No such file or directory
42949672976:error:25070067:DSO support
On Sat, 3 Feb 2024 at 19:25, Corinna Vinschen wrote:
> > Sorry to say that, but SetThreadErrorMode/CreateProcess don't do what we
> > want them to do. I just tested this myself with a modified Cygwin DLL
> > (code below) and it turns out that the child process error mo
inna Vinschen via Cygwin wrote:
> > > > > Is it actually a safe bet that the error mode set by
> > > > > SetThreadErrorMode
> > > > > is then propagated as process error mode to the child process?
> > > > >
> > > > > I ha
ight" is the reason the flag/option was
re-added in MSYS2. I think the most "right" thing Cygwin could do (if it
were to only do one thing, rather than having an option) would be to
somehow have native processes inherit the error mode as though Cygwin were
not in the mix. The issue wit
On Feb 2 19:51, Corinna Vinschen via Cygwin wrote:
> On Feb 2 18:22, Corinna Vinschen via Cygwin wrote:
> > On Feb 2 14:56, David Allsopp via Cygwin wrote:
> > > On Fri, 2 Feb 2024 at 14:18, Corinna Vinschen via Cygwin wrote:
> > > > Is it actually a sa
the
> > > > call to CreateProcess for a non-Cygwin binary, Cygwin restores the
> > > > error mode (for that thread only) to the value read at startup, calls
> > > > CreateProcess and then sets the error mode back.
> > >
> > > This sounds like a good
e change), but in some ways perhaps Cygwin
> > > should be using GetErrorMode on startup and instead of not inheriting
> > > it, ensuring that it sets whatever it received? i.e. just before the
> > > call to CreateProcess for a non-Cygwin binary, Cygwin restores the
>
e done this way (it feels more complicated
> > than just reverting the change), but in some ways perhaps Cygwin
> > should be using GetErrorMode on startup and instead of not inheriting
> > it, ensuring that it sets whatever it received? i.e. just before the
> > call to CreatePr
f not inheriting
> it, ensuring that it sets whatever it received? i.e. just before the
> call to CreateProcess for a non-Cygwin binary, Cygwin restores the
> error mode (for that thread only) to the value read at startup, calls
> CreateProcess and then sets the error mode back.
This soun
his way (it feels more complicated
than just reverting the change), but in some ways perhaps Cygwin
should be using GetErrorMode on startup and instead of not inheriting
it, ensuring that it sets whatever it received? i.e. just before the
call to CreateProcess for a non-Cygwin binary, Cygwin restores the
erro
On Fri, 2 Feb 2024 at 12:55, Corinna Vinschen via Cygwin wrote:
> On Feb 2 09:43, David Allsopp via Cygwin wrote:
> > On Thu, 1 Feb 2024 at 10:02, Corinna Vinschen via Cygwin
> > wrote:
> > >
> > > The behaviour changed in 2020
> > >
> > >
behaviour you want?
I guess perhaps what's needed here is a command-wrapper tool like 'nice'
or 'env' which lets you run a command with the error-handling mode you want.
But that must already exist for Windows, right? :)
--
Problem reports: https://cygwin.com/problems.html
FAQ:
On Feb 2 09:43, David Allsopp via Cygwin wrote:
> On Thu, 1 Feb 2024 at 10:02, Corinna Vinschen via Cygwin
> wrote:
> >
> > The behaviour changed in 2020
> >
> > https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=21ec498d7f912
> >
> > not without a discussion
> >
> >
On Thu, 1 Feb 2024 at 10:02, Corinna Vinschen via Cygwin
wrote:
>
> The behaviour changed in 2020
>
> https://cygwin.com/git/?p=newlib-cygwin.git;a=commitdiff;h=21ec498d7f912
>
> not without a discussion
>
> https://cygwin.com/pipermail/cygwin-patches/2020q4/010870.html
Aha, thank you! (congrats
v%d\n", ZSTD_versionNumber());
}
and compiling with
x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
when I then run ./test.exe, I get the Windows critical-error-handler
dialog stating "The code execution cannot proceed because
libzstd-1.dll was not found. Reinstalling the program may fix this
problem
ere is no popup displayed. However, it also calls
> Cygwin's sh and _that_ executes that program too, so something like
> "C:\cygwin64\bin\sh -c "./test.exe | sed ..." but then the popup error
> message appears. So somewhere along the line, Cygwin appears to be
> resetting t
omething like
"C:\cygwin64\bin\sh -c "./test.exe | sed ..." but then the popup error
message appears. So somewhere along the line, Cygwin appears to be
resetting the system error mode, and that appears contrary to previous
(old) messages on the subject.
Thanks,
David
--
Problem r
printf("Zstandard v%d\n", ZSTD_versionNumber());
> > }
> >
> > and compiling with
> >
> > x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
> >
> > when I then run ./test.exe, I get the Windows critical-error-handler
> > dialog stating "The code exec
exe, I get the Windows critical-error-handler
dialog stating "The code execution cannot proceed because
libzstd-1.dll was not found. Reinstalling the program may fix this
problem."
My question is not how to fix the problem (I'm well aware of that),
but rather why that message is be
x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
>
> when I then run ./test.exe, I get the Windows critical-error-handler
> dialog stating "The code execution cannot proceed because
> libzstd-1.dll was not found. Reinstalling the program may fix this
> problem."
>
> My q
exe, I get the Windows critical-error-handler
dialog stating "The code execution cannot proceed because
libzstd-1.dll was not found. Reinstalling the program may fix this
problem."
[snip]
x86_64-w64-mingw32-gcc is a cross compiler, a.k.a. the Mingw compiler,
not Cygwin's gcc.
Starting with this very trivial C program:
#include
#include
int main(void) {
printf("Zstandard v%d\n", ZSTD_versionNumber());
}
and compiling with
x86_64-w64-mingw32-gcc -o test.exe test.c -lzstd
when I then run ./test.exe, I get the Windows critical-error-handler
dial
Thanks, Jon - I've removed the parameter for '
http://cygwinports.org/ports.gpg' and I'm not entirely sure why I had it
there in the first place.
However, on removing the parameter, I now get the error for every
referenced site in the script "Unable to get setup from <https://.../>
On 22/12/2023 14:41, James Hanley via Cygwin wrote:
when running the following script below - I always get the error indicated
in the subject line. If I click another site from the UI then after it
works fine. If I change the script to reflect that selected site from the
UI and re-run, I get
when running the following script below - I always get the error indicated
in the subject line. If I click another site from the UI then after it
works fine. If I change the script to reflect that selected site from the
UI and re-run, I get the same error mentioned. Any ideas?
""&
Version 1.47-1 of
libgpg-error-devel
libgpg-error0
are available in the Cygwin distribution:
CHANGES
Latest upstream release
DESCRIPTION
Libgpg-error is a small library that originally defined common error
values for all GnuPG components. Among these are GPG, GPGSM, GPGME
Hi,
On 27/11/2023 7:51 pm, tk--- via Cygwin wrote:
Any idea why this is happening ?
I suspect the reason is related to this long standing understanding of
Cygwin:
https://sourceware.org/legacy-ml/cygwin/2004-09/msg00087.html
On 03/09/2004 2:13 am, Corinna Vinschen wrote:
Public Key
Hi,
We have observed that the command 'NET USER' issues en error message and
doesn't display the computer name, even if it completes the command
successfully:
>>>>>
User accounts for \\
---
t; to use StrictMode
and "yes" to install sshd as a service
I just press for the question for "Value of CYGWIN for the daemon".
cygrunsrv -S cygsshd will not start the sshd. "QueryServiceStatus: Win32 error
1062:"
I tried "ssh-keygen -A" - but no keys cre
On Nov 14 00:58, Mark Geisert wrote:
> Minor updates to profiler and gmondump, which share some code:
> - fix operation of error() so it actually works as intended
> - resize 4K-size auto buffer reservations to BUFSIZ (==1K)
> - remove trailing '\n' from 2nd arg on error() call
Minor updates to profiler and gmondump, which share some code:
- fix operation of error() so it actually works as intended
- resize 4K-size auto buffer reservations to BUFSIZ (==1K)
- remove trailing '\n' from 2nd arg on error() calls everywhere
- provide consistent annotation of Windows error
Hi Corinna,
On Mon, 13 Nov 2023, Corinna Vinschen wrote:
On Nov 13 01:46, Mark Geisert wrote:
Minor updates to profiler and gmondump, which share some code:
- fix operation of error() so it actually works as intended
- resize 4K-size auto buffer reservations to BUFSIZ (==1K)
- remove trailing
Hi Mark,
On Nov 13 01:46, Mark Geisert wrote:
> Minor updates to profiler and gmondump, which share some code:
> - fix operation of error() so it actually works as intended
> - resize 4K-size auto buffer reservations to BUFSIZ (==1K)
> - remove trailing '\n' from 2nd arg on e
Minor updates to profiler and gmondump, which share some code:
- fix operation of error() so it actually works as intended
- resize 4K-size auto buffer reservations to BUFSIZ (==1K)
- remove trailing '\n' from 2nd arg on error() calls everywhere
- provide consistent annotation of Windows error
and he gets a seemingly nonsensical
> error that I don't understand.
> The script starts out pretty simply, just like this:
> --
> #! /bin/bash
> #set -x
> main() {
> if [ "$1" == "" ]; then
> usage;
> exit;
> fi
> ...
>
, but couldn't find the repo for
cygwin-devel anywhere.
This error was introduced with the most recent update to cpuset.h.
There is a public-visible mirror of the Cygwin tree at
https://github.com/cygwin/cygwin/blob/main/winsup/cygwin
and the problematic file can be found at
include/sys
was worked on recently, but couldn't track it down any closer. I also
tried to find a git repository so I could find the commit so I could check
for similar errors on other headers, but couldn't find the repo for
cygwin-devel anywhere.
This error was introduced with the most recent update t
I just updated to 3.4.9-1 and compiled some code, and it complained about
cpuset.h.
Specifically, "C++ requires a type specifier for all declarations", and
sure enough, there's no return type on line 52. So I changed my local copy
to the following, and it cleared things up:
#define
---
winsup/cygwin/fhandler/dsp.cc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/winsup/cygwin/fhandler/dsp.cc b/winsup/cygwin/fhandler/dsp.cc
index 8e51a51c5..e872aa08c 100644
--- a/winsup/cygwin/fhandler/dsp.cc
+++ b/winsup/cygwin/fhandler/dsp.cc
@@ -1192,7 +1192,9 @@
- Fatal error 1 on xcb connection
winDeinitMultiWindowWM - Noting shutdown in progress (II) Server
terminated successfully (0). Closing log file.
Any pointers for how to troubleshoot?
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation
>Not sure if you guys still exist or not? But having a problem porting over
>to Windows 10 and getting this error. Any suggestions?
>1 [main] bash 9592 find_fst_cwd: WARNING: Couldnt compute FAST_CWD pointer.
>Please report this problem to the public mailing list cygwin@cygwin.
Not sure if you guys still exist or not? But having a problem porting over
to Windows 10 and getting this error. Any suggestions?
1 [main] bash 9592 find_fst_cwd: WARNING: Couldnt compute FAST_CWD pointer.
Please report this problem to the public mailing list cygwin@cygwin.com
Thanks,
--
Rich
>bin/iperf3.exe -c 192.168.1.233 -P 1 -i 1 -p 5201 -f g -t 10Â Â Â 0 [main]
>iperf3 17636 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer.Â
>Please report this problem tothe public mailing list cygwin@cygwin.com
bin/iperf3.exe -c 192.168.1.233 -P 1 -i 1 -p 5201 -f g -t 10 0 [main]
iperf3 17636 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer. Please
report this problem tothe public mailing list cygwin@cygwin.com
--
Problem reports: https://cygwin.com/problems.html
FAQ:
ext copied in "c." to the cntlm.ini file below the
>following line:
> i. #
> PassNTLMv2 D5826E9C665C37C80B53397D5C07BBCB
>e. Save and Close the cntlm.ini file.
>When I press enter at the end of this li
i. #
PassNTLMv2 D5826E9C665C37C80B53397D5C07BBCB
e. Save and Close the cntlm.ini file.
When I press enter at the end of this line, cntlm -c cntlm.ini -I -M
http://google.ro, it returns the following error.
4 [main] cntlm 5768 find_fast_cwd: WARNING: Couldn'
On Jul 8 07:59, Takashi Yano wrote:
> Hi Corinna,
>
> On Fri, 7 Jul 2023 11:46:15 +0200
> Corinna Vinschen wrote:
> > On Jul 7 12:34, Takashi Yano wrote:
> > > diff --git a/winsup/cygwin/dtable.cc b/winsup/cygwin/dtable.cc
> > > index 18e0f3097..2aae2fd65 100644
> > > ---
Hi Corinna,
On Fri, 7 Jul 2023 11:46:15 +0200
Corinna Vinschen wrote:
> On Jul 7 12:34, Takashi Yano wrote:
> > diff --git a/winsup/cygwin/dtable.cc b/winsup/cygwin/dtable.cc
> > index 18e0f3097..2aae2fd65 100644
> > --- a/winsup/cygwin/dtable.cc
> > +++ b/winsup/cygwin/dtable.cc
> > @@ -600,7
Hi Takashi,
On Jul 7 12:34, Takashi Yano wrote:
> diff --git a/winsup/cygwin/dtable.cc b/winsup/cygwin/dtable.cc
> index 18e0f3097..2aae2fd65 100644
> --- a/winsup/cygwin/dtable.cc
> +++ b/winsup/cygwin/dtable.cc
> @@ -600,7 +600,13 @@ fh_alloc (path_conv& pc)
> case FH_TTY:
> if
As reported in
https://cygwin.com/pipermail/cygwin/2023-June/253888.html,
"Bad address" error occurs when stat() is called after the commit
3721a756b0d8 ("Cygwin: console: Make the console accessible from
other terminals.").
There are two problems in the current code. One
On 28/06/2023 11:56, Daisuke Fujimura via Cygwin-apps wrote:
I am reporting a scallywag error during git push.
remote: scallywag: invoked on repository git/cygwin-packages/libhtp,
by maintainer Daisuke Fujimura
remote: scallywag: timeout waiting for GitHub to assign a wfr_id
remote: scallywag
I am reporting a scallywag error during git push.
remote: scallywag: invoked on repository git/cygwin-packages/libhtp,
by maintainer Daisuke Fujimura
remote: scallywag: timeout waiting for GitHub to assign a wfr_id
remote: scallywag: PLEASE REPORT THIS!
remote: scallywag: build 6661 queued
>
> ...
>
> > He was getting a weird error on line 3, just saying this:
> > -
> > ...: line 3: syntax error near unexpected token `$'{\r''
> > ...: line 3: `main() {
> > ---
>
> If you run bash with the "-o igncr&q
fferent problem.
...
> He was getting a weird error on line 3, just saying this:
> -
> ...: line 3: syntax error near unexpected token `$'{\r''
> ...: line 3: `main() {
> ---
If you run bash with the "-o igncr" option, it will igno
On 6/26/2023 4:58 PM, Dan Harkless via Cygwin wrote:
On 6/26/2023 4:35 PM, David Karr via Cygwin wrote:
> > He was getting a weird error on line 3, just saying this:
> > -
> > ...: line 3: syntax error near unexpected token `$'{\r''
>
On 6/26/2023 4:35 PM, David Karr via Cygwin wrote:
> He was getting a weird error on line 3, just saying this:
> -
> ...: line 3: syntax error near unexpected token `$'{\r''
> ...: line 3: `main() {
> ---
Apologies, I don't remember yo
I'm seeing a problem with someone else's Cygwin setup, sort of similar to a
problem I asked about a couple of weeks ago, in that it's a problem with
the same user, but seemingly a completely different problem.
He is using a Bash script that I wrote, and he gets a seemingly nonsensical
error
Achim Gratz wrote:
> Brian Inglis writes:
> > Problem writing tar (with Cygwin default sys) symlinks before target
> > created under Cygwin 3.5.0 - error messages are issued and tar exits
> > with failure status!
> […]
> > The only likely culprit betwe
target
> > created under Cygwin 3.5.0 - error messages are issued and tar exits
> > with failure status!
> […]
> > The only likely culprit between 3.4.6 and that commit seems to be
> > commit 2023-04-18 fa84aa4dd2fb43eaf7fcdfb040aef854f2f19d01 Cygwin: fix
> > errno v
Brian Inglis via Cygwin writes:
> Problem writing tar (with Cygwin default sys) symlinks before target
> created under Cygwin 3.5.0 - error messages are issued and tar exits
> with failure status!
[…]
> The only likely culprit between 3.4.6 and that commit seems to be
> co
Problem writing tar (with Cygwin default sys) symlinks before target created
under Cygwin 3.5.0 - error messages are issued and tar exits with failure status!
Also failed with the same issues under my own dev build based off origin/main
commit 2023-05-01
Hello,
I'm trying to create a volume shadow copy image using
$ dd if=/proc/sys/Device/HarddiskVolumeShadowCopy9 of=/dev/null
bs=4096 status=progress
but it ends prematurely with
116923437056 bytes (117 GB, 109 GiB) copied, 65 s, 1.8 GB/s
dd: error reading '/proc/sys/Device
folks,
Just updated everything including perl and now git send-email fails with error
without prompting or requesting input for sendemail.confirm = always - address
headers have been sanitized and perl indents have been reduced:
$ git send-email --to=patches
0001-fhandler-proc.cc
>pwd 2444 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer
https://cygwin.com/faq.html#faq.using.fixing-find_fast_cwd-warnings
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
pwd 2444 find_fast_cwd: WARNING: Couldn't compute FAST_CWD pointer
--
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
get this error message:
https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30182: syntax error, unexpected $undefined, expecting COMMA or NL
https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30182: unrecognized line 30183 (do you have the latest setup?)
https
On Fri, Apr 7, 2023 at 2:40 AM Jon Turney wrote:
>
> On 07/04/2023 02:44, Keith Thompson via Cygwin wrote:
> > Running setup-x86_64.exe on a Windows 10 laptop, I get this error message:
> >
> > https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
> > 3
On 07/04/2023 02:44, Keith Thompson via Cygwin wrote:
Running setup-x86_64.exe on a Windows 10 laptop, I get this error message:
https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30182: syntax error, unexpected $undefined, expecting COMMA or NL
https://mirrors.kernel.org
1 - 100 of 7042 matches
Mail list logo
