public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Yadin Y. Goldschmidt" <yadin@pitt.edu>
To: cygwin@cygwin.com
Subject: Re: Setup Parse Errors
Date: Fri, 19 Sep 2003 20:00:00 -0000	[thread overview]
Message-ID: <bkfmeb$95r$1@sea.gmane.org> (raw)
In-Reply-To: <71A0F7B0F1F4F94F85F3D64C4BD0CCFE029B6FFC@bmkc1svmail01.am.mfg>

I am getting the same problem exactly after downloading setup 2.340.2.5 due
to the tetex problem. I can no longer update cygwin.

"Parker, Ron" <rdparker@butlermfg.com> wrote in message
news:71A0F7B0F1F4F94F85F3D64C4BD0CCFE029B6FFC@bmkc1svmail01.am.mfg...
> I am attempting to run setup version 2.340.2.5, which I just downloaded
from
> cygwin.com, and I am receiving a number of different "Parse Errors"
> processing setup.bz2.  They all read:
>
> (null) line X: syntax error, unexpected NL, expecting STRING
> (null) line X: unrecognized line X+1 (do you have the latest setup?)
>
> for x in 429 440 744.
>
> It's also interesting that each time I back up and try again with a
> different site the list gets appended to instead of restarted.  I might
try
> debugging this, but I have to get Cygwin reinstalled first, catch-22.
>
> This is all because tetex-base-2.0.1.13(version???) was freezing setup, so
I
> decided to uninstall and reinstall.
>




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2003-09-19 19:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 18:06 Parker, Ron
2003-09-19 20:00 ` Yadin Y. Goldschmidt [this message]
2010-05-29 22:32 Mahir Morshed
2010-05-30  6:00 ` Thierry
2010-05-30  8:19 ` Christopher Faylor

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='bkfmeb$95r$1@sea.gmane.org' \
    --to=yadin@pitt.edu \
    --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).