From: Cliff Hones <cliff@hones.org.uk>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: http://cygwin.com/setup*.exe
Date: Tue, 23 Jul 2013 16:16:00 -0000 [thread overview]
Message-ID: <51EE9D70.80709@hones.org.uk> (raw)
In-Reply-To: <announce.20130722152325.GA495@ednor.casa.cgf.cx>
On 22/07/2013 16:23, Christopher Faylor wrote:
> We have updated the setup.exe executables on cygwin.com in preparation
> for the upcoming release of Cygwin 1.7.22.
> ...
I hit a couple of problems using the new 32-bit setup yesterday -
during which it managed to break my installation.
System is XP SP3 32-bit - no BLODA issues encountered before.
I usually have no problems upgrading Cygwin - I normally stop
any Cygwin processes if necessary to ensure the update can
complete without a reboot, but even if I don't the fixup-on-reboot
mechanism works fine. However, setup V2.814 (32 bit) didn't
behave as well - it popped up a dialog box warning of processes in use,
but no processes were listed. Clicking on "Stop processes" didn't
stop any processes, and the dialog was redisplayed. Clicking on
"Continue" allowed the install to complete, but after a reboot
I had a broken installation - investigation showed several
dlls (including cygwin1.dll) in /usr/bin and an exe in /usr/sbin had not
been updated, and the new ones were still there with extension .new.
Manually deleting and renaming fixed this issue - but clearly this shouldn't
have happened! A look at setup.log showed nothing amiss - setup reported
that it couldn't update the dlls/exes, and that a reboot was necessary - so
it should have scheduled the renames for reboot.
A second problem I hit was that I had a system crash (unrelated to Cygwin)
while setup was downloading updated packages. This lost cached disk
data, so when setup was restarted it detected several corrupt packages
(MD5 sumchecks failed). It offered the choice of installing anyway or
omitting the affected packages - but I couldn't see a way to make setup
re-download them. Selecting reinstall didn't work - that would
reinstall the old version but updating again complained of a corrupt
new package (and choosing the install anyway option is *not* a good
idea as it tries to use the corrupt package and fails to unpack).
Manually deleting the affected packages from my install directory
fixed this - but am I missing a better way?
I also had a problem with cygports - I use the setup -K option -
and yesterday the cygports site was missing the setup .ini/.bz2
files - but today I see that's fixed :-)
-- Cliff
--
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
prev parent reply other threads:[~2013-07-23 15:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 16:08 Christopher Faylor
2013-07-23 16:16 ` Cliff Hones [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=51EE9D70.80709@hones.org.uk \
--to=cliff@hones.org.uk \
--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).