public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jeremy Ramer <jdramer@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Postinstall script errors
Date: Thu, 12 Aug 2010 13:38:00 -0000	[thread overview]
Message-ID: <AANLkTim0EAbuHF81OC0RX_qz2jMf_Sqhj0tNOCyQNV8c@mail.gmail.com> (raw)
In-Reply-To: <20100812095930.GX14202@calimero.vinschen.de>

On Thu, Aug 12, 2010 at 3:59 AM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> On Aug 11 09:18, Jeremy Ramer wrote:
>> I recently upgraded from cygwin 1.5 to 1.7. At the end of the install
>> there were errors with some of the postinstall scripts.  From the
>> setup.full.log:
>>
>> 2010/08/11 08:39:53 running: C:\cygwin\bin\bash.exe --norc --noprofile
>> /etc/postinstall/bash.sh
>> ln: creating symbolic link `/dev/stdin': File exists
>> 2010/08/11 08:39:54 abnormal exit: exit code=1
>> 2010/08/11 08:39:54 running: C:\cygwin\bin\bash.exe --norc --noprofile
>> /etc/postinstall/passwd-grp.sh
>> 2010/08/11 08:39:55 abnormal exit: exit code=1
>>
>>
>> I tried manually running the scripts with mixed results
>>
>> $ bash --norc --noprofile /etc/postinstall/bash.sh ; echo $?
>> 0
>>
>> $ bash --norc --noprofile /etc/postinstall/passwd-grp.sh ; echo $?
>> 1
>>
>> I tired manually running the commands inside passwd-grp.sh and they
>> all return 0. So I'm not sure what exactly is failing.  Is there
>> anything I should do to investigate?
>
> That's probably a fault in the postinstall scripts.  It would be nice if
> you could provide more details about what fails exactly in the script,
> or better, what in the script has a non-0 exit code.  That would help us
> lazy maintainers to fix the scripts faster.

The issue with the passwd-grp.sh script seems to be the last two lines.

[ "$created_passwd" = "yes" ] && /bin/chgrp --silent root /etc/passwd
[ "$created_group" = "yes"  ] && /bin/chgrp --silent root /etc/group

I verified that $created_passwd and $created_group were both no so
both conditionals will fail. But because the last conditional is the
last thing run, the script returns 1.  Adding an exit 0 to the script
fixes it, but I'm not sure if that accomplishes what you want from the
script.

Jeremy

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

  reply	other threads:[~2010-08-12 13:38 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-11 15:18 Jeremy Ramer
2010-08-12  9:59 ` Corinna Vinschen
2010-08-12 13:38   ` Jeremy Ramer [this message]
2010-08-12 14:05     ` Corinna Vinschen
2010-08-12 14:10     ` Matthias Andree
2010-08-12 14:41       ` Corinna Vinschen
2010-08-12 14:52         ` Matthias Andree
2010-08-12 14:54           ` Corinna Vinschen
2010-08-12 15:04             ` Matthias Andree
2010-08-12 15:15               ` Corinna Vinschen
2010-08-12 16:02                 ` Matthias Andree
2010-08-12 17:56   ` Tilman Hausherr
2010-08-13  9:48     ` Corinna Vinschen
2010-08-20 19:32       ` Tilman Hausherr
     [not found] <58C73DA23112384988EEB999F2EC04DC1E78D328@ATLEISEXCMBX1.eis.equifax.com>
2016-04-11 18:51 ` Ken Brown

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=AANLkTim0EAbuHF81OC0RX_qz2jMf_Sqhj0tNOCyQNV8c@mail.gmail.com \
    --to=jdramer@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).