From: Daisuke Fujimura <booleanlabel@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Fwd: Error running setup-x86_64.exe: syntax error in setup.zst
Date: Fri, 7 Apr 2023 18:20:50 +0900 [thread overview]
Message-ID: <CAA3frXTC8Fd2UxduqWbD_Hjd5jEb-9e336tgUHe8-V7MmLNa1w@mail.gmail.com> (raw)
In-Reply-To: <CAAHpriMPLNFRojXh2qO9=3z1xBLc+xd6J8cygW3mOj4A+wTs+g@mail.gmail.com>
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
---------- Forwarded message ---------
From: Keith Thompson via Cygwin <cygwin@cygwin.com>
Date: Fri, Apr 7, 2023 at 10:45 AM
Subject: Error running setup-x86_64.exe: syntax error in setup.zst
To: <cygwin@cygwin.com>
Cc: Keith Thompson <keithsthompson@gmail.com>
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.
--
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
next parent reply other threads:[~2023-04-07 9:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAHpriMPLNFRojXh2qO9=3z1xBLc+xd6J8cygW3mOj4A+wTs+g@mail.gmail.com>
2023-04-07 9:20 ` Daisuke Fujimura [this message]
2023-04-07 19:21 ` Brian Inglis
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=CAA3frXTC8Fd2UxduqWbD_Hjd5jEb-9e336tgUHe8-V7MmLNa1w@mail.gmail.com \
--to=booleanlabel@gmail.com \
--cc=cygwin-apps@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).