public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Significant problems with reinstalling whole system
Date: Sat, 10 Feb 2018 16:18:00 -0000	[thread overview]
Message-ID: <a8dcff0d-3e73-96b3-2a20-d966f18c3d02@SystematicSw.ab.ca> (raw)
In-Reply-To: <CA+Ni7jMHr+NNWJpEb8AB3bdyimwYHQdCRAYv_JnFbYui0Xm=Fw@mail.gmail.com>

On 2018-02-10 01:16, Pëtr B. wrote:
> I was experiencing problems with my installation of Cygwin lately and
> decided to reinstall everything from local package archive. I
> experienced following problem while doing so:
> https://imgur.com/a/9lm4W
> which occured for a busload of packages. What's causing it? I am suspecting
> that it's because I used multiple mirrors but this should obviously is taken
> into account.

One of your downloaded mirrors may not have the package version it needs to
install. For setup problems, please just attach as plain text (or paste from):
	<CYGWIN_ROOT>/var/log/setup.log.full
to show last setup run verbose details to aid diagnosis, and maybe also:
	<CYGWIN_ROOT>/var/log/setup.log
with the summaries of the last few runs.

Cygwin setup is really only intended to support a local or overlay mirror with a
full recent mirror. You have five mirrors on two continents accessed over two
protocols. Move all of the package subdirectories under your most available,
closest, fastest mirror directory from all your other mirror directories, delete
all others, download a fresh copy of
	https://cygwin.com/setup-x86[_64].exe
pick just that one mirror in setup, and let setup download and install the
upgrades it needs to give you a working system.
If you are reinstalling, download and install only the base system packages in
the first setup run, add simple utility packages in the next run, add major
suites like gcc, clang, tex, base X, in separate runs, rather than trying a big
bang recreation, unless you know you have a reliable, close, fast mirror on a
fast link, and are prepared to wait a long time for postinstall scripts to finish.
Changes in cygwin and other DLLs may require rebuilds of packages and
installation of upgraded versions of packages and dependencies, but setup will
not download or install anything you already have with the current version and
matching hash sum.

If you really have to use a screen shot, instead of a blurry <PrintScreen> full
screen shot, with a short message about a symptom in one tiny message window,
maybe focus on and snap just the message window with <Alt-PrintScreen> or
another utility, paste it into some graphics editor, save it as a PNG at full
size and resolution so it is readable, and copy it somewhere public that will
not reduce it to unreadability when viewed in a browser window not as big as
your full screen.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

--
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

      parent reply	other threads:[~2018-02-10 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-10  8:16 Пётр Б.
2018-02-10 10:41 ` Marco Atzeri
2018-02-10 16:18 ` Brian Inglis [this message]

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=a8dcff0d-3e73-96b3-2a20-d966f18c3d02@SystematicSw.ab.ca \
    --to=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).