From: Kenneth Wolcott <kennethwolcott@gmail.com>
To: Andrey Repin <cygwin@cygwin.com>
Cc: Charles Wilson <cygwin@cwilson.fastmail.fm>
Subject: Re: setup-x86_64: postinstall errors: Package bash 1, Package a2ps 2 and xinit 134
Date: Thu, 25 Jul 2013 07:11:00 -0000 [thread overview]
Message-ID: <CADex0xynZvSvXCZ7TNFoqO-djtijKcNSvibVnYyO4KEwTftirg@mail.gmail.com> (raw)
In-Reply-To: <1358868658.20130724173406@mtu-net.ru>
Hi All;
Again, first of all, thanks for Cygwin! And thanks for Cygwin 64!
Since almost all pertinent context in this email thread is now
scattered (at least for me), I have removed all prior content in this
reply.
I just ran an update using the same mirror (kernel.org) I usually use.
I was warned that my setup.ini was newer than my setup*.exe so I
terminated the update.
I downloaded a fresh setup-x86_64.exe from cygwin.com and then ran
the update again.
Now I get only this postinstall error:
Package: xinit
xinit.sh exit code 134
The a2ps and bash postinstall errors have vanished.
The output of uname -a is: CYGWIN_NT-6.1 User-PC 1.7.22(0.268/5/3)
2013-07-22 17:06 x86_64 Cygwin
Thanks,
Ken Wolcott
--
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:[~2013-07-25 4:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 4:41 Kenneth Wolcott
2013-07-23 7:21 ` Yaakov (Cygwin/X)
2013-07-23 8:20 ` Corinna Vinschen
2013-07-23 9:00 ` Yaakov (Cygwin/X)
2013-07-23 9:57 ` Corinna Vinschen
2013-07-23 19:57 ` Yaakov (Cygwin/X)
2013-07-24 12:53 ` Corinna Vinschen
2013-07-23 18:50 ` Charles Wilson
2013-07-23 19:08 ` Corinna Vinschen
2013-07-23 19:44 ` Charles Wilson
2013-07-23 19:51 ` Corinna Vinschen
2013-07-24 13:23 ` Charles Wilson
2013-07-24 13:35 ` Corinna Vinschen
2013-07-24 19:37 ` Andrey Repin
2013-07-25 7:11 ` Kenneth Wolcott [this message]
2013-07-29 1:36 ` Jon TURNEY
2013-07-29 5:19 ` Charles Wilson
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=CADex0xynZvSvXCZ7TNFoqO-djtijKcNSvibVnYyO4KEwTftirg@mail.gmail.com \
--to=kennethwolcott@gmail.com \
--cc=cygwin@cwilson.fastmail.fm \
--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).