FYI apps - fixed 20 minutes after your post - noted on original Cygwin thread
On 2023-04-07 03:20, Daisuke Fujimura via Cygwin-apps wrote:
I think it's the effect of the latest gnubg package, can anyone fix it?
https://cygwin.com/git-cygwin-packages/?p=git/cygwin-packages/gnubg.git;a=blobdiff;f=gnubg.cygport;h=559ae03f174cbcd3ad7ab3fcca11ad210f45ed0f;hp=471f68c78804b0da14e7a22fa9befce86cc2521e;hb=0961ac54da1a03e8c747281f8359449636dd0db7;hpb=522ffd2cf1f6fb831f14b239058d5f589a176917
On Fri, Apr 7, 2023 at 10:45 AM, Keith Thompson 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/sourceware/cygwin/x86_64/setup.zst line
30182: unrecognized line 30183 (do you have the latest setup?)
https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30203: syntax error, unexpected $undefined, expecting COMMA or NL
https://mirrors.kernel.org/sourceware/cygwin/x86_64/setup.zst line
30203: unrecognized line 30204 (do you have the latest setup?)
(I can't copy the text from the message box so I retyped it.)
I re-downloaded setup-x86_64.exec, and it's identical to the one on my laptop.
I'm using the mirrors.kernel.org mirror.
The setup.zst from mirrors.dotsrc.org is identical.
I decompressed setup.zst and I do see something suspicious on the
indicated lines.
Here's line 30182:
build-depends: \, bison, cygport, dblatex, docbook2X, flex,
gettext-devel, libGLU-devel, libcairo-devel, libcanberra-gtk-devel,
libcurl-devel, libfreetype-devel, libglib2.0-devel, libgmp-devel,
libgtk2.0-devel, libgtkglext1.0-devel, libpango1.0-devel,
libpng-devel, libreadline-devel, libsqlite3-devel, libxslt,
python3-devel, texinfo
Line 30203 is similar. I don't see a lone backslash anywhere else in the file.
The setup.zst from mirrors.sonic.net does *not* have problematic
build-depends lines.
(Switching to a different mirror might be a workaround, but I haven't
tried it yet.)
The "bad" setup.zst has "setup-timestamp: 1680813730" (Thu 2023-04-06
20:42:10 UTC).
The "good" setup.zst has "setup-timestamp: 1680795371" (Thu 2023-04-06
15:36:11 UTC).
The bad one is about 5 hours newer than the good one.
I'm concerned that the bad setup.zst might propagate to other mirrors.
