From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: setup complains about cygwin-doc package update
Date: Wed, 05 Jul 2017 19:52:00 -0000 [thread overview]
Message-ID: <73c6d340-012c-b6f7-e82c-804b7031e713@SystematicSw.ab.ca> (raw)
In-Reply-To: <20170705142723.GH30902@calimero.vinschen.de>
On 2017-07-05 08:27, Corinna Vinschen wrote:
> On Jul 5 13:32, Nellis, Kenneth wrote:
>> Curious about an error that setup.exe reported today related to upgrading
>> package cygwin-doc to 2.8.1-1, saying:
>>
>> Postinstall script errors
>> These do not necessarily mean that affected packages will fail to function
>> properly, but please check /var/log/setup.log.full and report any problems.
>>
>> Package: _/cygwin-doc
>> cygwin-doc.sh exit code 2
>>
>> A subsequent setup.exe run with nothing pending gave a different message:
>>
>> Package: _/Unknown package
>> cygwin-doc.sh exit code 2
>>
>> Looking in setup.log.full I see:
>>
>> 2017/07/05 09:13:33 running: C:\cygwin64\bin\bash.exe --norc --noprofile "/etc/postinstall/cygwin-doc.sh"
>> Can't find directory '/proc/cygdrive/c/ProgramData/Microsoft/Windows/Start Menu/Programs/Cygwin'
>> 2017/07/05 09:13:34 abnormal exit: exit code=2
>>
>> Indeed, there is no Cygwin directory in existing directory
>> '/proc/cygdrive/c/ProgramData/Microsoft/Windows/Start Menu/Programs'.
>>
>> Looking at cygwin-doc.sh, it seems that the script is trying to put some things in that directory.
>>
>> So, I manually created the directory and reran setup. This time no errors reported,
>> and the newly created directory contains the following files:
>>
>> $ ls -l
>> total 24
>> -rwxr-xr-x+ 1 knellis Domain Users 1233 Jul 5 09:30 'API (HTML).lnk'
>> -rwxr-xr-x+ 1 knellis Domain Users 1041 Jul 5 09:30 'API (PDF).lnk'
>> -rwxr-xr-x+ 1 knellis Domain Users 1248 Jul 5 09:30 FAQ.lnk
>> -rwxr-xr-x+ 1 knellis Domain Users 1224 Jul 5 09:30 'Home Page.lnk'
>> -rwxr-xr-x+ 1 knellis Domain Users 1242 Jul 5 09:30 'User Guide (HTML).lnk'
>> -rwxr-xr-x+ 1 knellis Domain Users 1050 Jul 5 09:30 'User Guide (PDF).lnk'
>> $
>>
>> So, these are handy links to have, I guess, but is it appropriate for
>> cygwin-doc.sh to presume that the directory exists? Maybe it should create it
>> rather than simply bail out and complain if it doesn't exist.
I am a big fan and hoarder of shortcuts, bookmarks, links, URLs, etc.
> In theory, the script should only create the files if the directory
> exists. Brian?
Assumption made was that setup would create SM/Programs/Cygwin, but the
postinstall/preremove scripts should check and exit if not there.
Presumably if no shortcuts are desired, that dir is not created?
I can change the scripts to check and fail quietly if not there.
--
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
prev parent reply other threads:[~2017-07-05 19:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 13:32 Nellis, Kenneth
2017-07-05 14:27 ` Corinna Vinschen
2017-07-05 19:52 ` Brian Inglis [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=73c6d340-012c-b6f7-e82c-804b7031e713@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).