From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: NEW DEFECT: Basic cygwin Update Fails to Complete
Date: Wed, 25 Jul 2018 22:11:00 -0000 [thread overview]
Message-ID: <dfc1404f-11fb-9fa9-3d64-5389d6fc78f0@SystematicSw.ab.ca> (raw)
In-Reply-To: <6e331c0a-5a5a-1126-1a47-9b662805b939@t-online.de>
On 2018-07-25 12:29, Hans-Bernhard Bröker wrote:
> Am 25.07.2018 um 12:39 schrieb John Delaney:
>
>> 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.
>
> "Failed to complete" or did it actually report and error and terminate? If the
> former: how long did you give before you decided it would never finish?
Hung in /etc/postinstall/texlive-collection.basic.sh or failed and setup
completed? Postinstall scripts autorebase, man-db, texlive, and a few others
sometimes take minutes to run: YMMV.
> "/usr/bin" does not normally exist on Cygwin installations.
>
> Whatever gave you _that_ idea?
Only /bin/ and /lib/ are created under the Cygwin root: /usr/bin/ and /usr/lib/
(also / and /proc/cygdrive/?/) appear as mount points under Cygwin processes.
If you use a Cygwin shell you can see /usr/{bin,lib}/, etc.; if you use a
Windows shell you can not.
--
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
next prev parent reply other threads:[~2018-07-25 18:50 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
2018-07-25 21:27 ` Hans-Bernhard Bröker
2018-07-25 22:11 ` Brian Inglis [this message]
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=dfc1404f-11fb-9fa9-3d64-5389d6fc78f0@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).