From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: NEW DEFECT: Basic cygwin Update Fails to Complete
Date: Wed, 25 Jul 2018 18:50:00 -0000 [thread overview]
Message-ID: <d44e8d5d-78ad-0ab2-d85e-2e2c784c7980@gmail.com> (raw)
In-Reply-To: <CAAgdLC17StJfXG-gb2cxJGBbGkuFiJ0=4buzV3C6ZG=dazJvzw@mail.gmail.com>
Am 25.07.2018 um 12:39 schrieb John Delaney:
> Cygwin Developer Team -
>
> My basic Cygwin update failure means that file redirection does work quite
> right. I had to manually
> add the cygcheck data.
>
> - John Delaney
Hi John,
you should attach the cygcheck.out not put in line
> Cygwin Developer Team:
>
> I am an experienced UNIX / Linux person who has built many UNIX / Linux
> kernels.
> I have successfully updated my 32-bit Cygwin installation at least 100
> times over the last 25+ years.
>
> As I have done many times before, I attempted to update my 32-bit
> Cygwin installation around midnight 7/24-25/ 2018.
> This time the process failed at about 99% complete. " /etc/postinstall/
> texlive-collection.basic.sh" failed to complete repeatedly
> and consistently.
I have seen similar issues.
There is any recent /var/log/setup.log.run* file ?
It should contain some hint of the problem.
What is the output of
grep wow64 /proc/self/maps | head -n1 | awk '{ print $1}'
and
rebase -si | awk '{print $3}'| head -n 5
> time cygcheck -s -v -r
>
> Cygwin Configuration Diagnostics
> Current System Time: Wed Jul 25 11:19:40 2018
>
> Windows 10 Home Ver 10.0 Build 17134
>
> Running under WOW64 on AMD64
Have you tried a 64bit installation ?
Regards
Marco
---
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus
--
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-07-25 11:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 18:29 John Delaney
2018-07-25 18:50 ` Marco Atzeri [this message]
2018-07-25 21:27 ` Hans-Bernhard Bröker
2018-07-25 22:11 ` Brian Inglis
2018-07-26 14:46 ` Hans-Bernhard Bröker
2018-07-26 14:54 ` 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=d44e8d5d-78ad-0ab2-d85e-2e2c784c7980@gmail.com \
--to=marco.atzeri@gmail.com \
--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).