From: david <david@daku.org>
To: Brian.Inglis@SystematicSw.ab.ca, cygwin@cygwin.com
Subject: Re: Failure download cygwin
Date: Sun, 13 May 2018 14:37:00 -0000 [thread overview]
Message-ID: <201805130957.w4D9vXir031126@telford.daku.org> (raw)
In-Reply-To: <7f49a650-4b02-275b-d200-a0c8704a532a@SystematicSw.ab.ca>
At 09:20 AM 5/12/2018, Brian Inglis wrote:
>On 2018-05-12 09:06, david wrote:
> > I tried to install the full collection from cygwin 64-bit. Yes, I
> know "you
> > really don't want to do that", but nevertheless, I do.
> > Using three different download mirrors, I find a large number of packages
> > have failed. A partial list is given below. In the past, the download has
> > succeeded, and yes, it took hours.
> > Please advise.
> > My most recent download attempt was from
> > ftp://linux.rz.ruhr-uni-bochum.de/cygwin
> > Download failures: (partial list)
>...
>
>You may be more successful if you preload your local package cache using e.g.
>wget -m, with some retry (and rate) limiting options, from your
>closest, lowest
>latency, fastest transfer rate, http mirror.
>
>--
Brian:
I followed your suggestion, but still had problems. After some more
experiments, I figured out that the file names were too long, and
thus the downloads failed. Unfortunately, this was not diagnosed by
"setup", which, in my opinion, should not allow a download to start
if the file names won't fit in the current Windows. I assume
(perhaps incorrectly), that there is a limit to package name length.
For example, I used as the directory
d:\arch\archiven\cygwin.2.10.0
and the selection of the download site made it
d:\arch\archiven\cygwin.2.10.0\ftp%3a%2f%2flinux.rz.ruhr-uni-bochum.de%2fcygwin%2f
which is getting pretty long.
Thanks for the download pointer; it helped me isolate the problem.
David
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-05-13 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-12 16:20 david
2018-05-12 17:15 ` Brian Inglis
2018-05-13 14:37 ` david [this message]
2018-05-13 15:46 ` Lee
2018-05-13 16:01 ` 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=201805130957.w4D9vXir031126@telford.daku.org \
--to=david@daku.org \
--cc=Brian.Inglis@SystematicSw.ab.ca \
--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).