X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:references:to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=ReoPWC6ow1lgIPl5
	TICAZ9nfSU9uZaNHLBzQWzWy+jEtUbST/B43NymbA8bSBi7n7CHWv8LY3R31uRnX
	v39GTfTrMr/8xmZK1KDa9E9THqVdfCNQvHAsJ980FSNrWlepKdHv1HkH3RQdPZNG
	/d+Nh2eAsc8eztPKDoi+Ps6wwB8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:reply-to:subject:references:to:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=PCBIAzavQSTn8wkSDsemqq
	CbTM0=; b=oyRDjKyfPha2QJ/+1cG/gkPV1Q9G+v0663g/IFpH4H/ogQkX0IXBYL
	1UE5txU9dAlOTUSlkcP/UEHxd/z+UntIwDBpPy1lj1DEo2BeMJQdTn/mq/EYoisY
	9GEqnN7UO+L0DfGvbYbPvVi9P1rXsPOQtSQLW82XXn7bb6gW7AH0Y=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=Home, H*R:D*ca
X-HELO: smtp-out-no.shaw.ca
X-Authority-Analysis: v=2.2 cv=a+JAzQaF c=1 sm=1 tr=0 a=MVEHjbUiAHxQW0jfcDq5EA==:117 a=MVEHjbUiAHxQW0jfcDq5EA==:17 a=IkcTkHD0fZMA:10 a=P7CjZ8JU4-64GukRjp8A:9 a=QEXdDO2ut3YA:10
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: setup complains about cygwin-doc package update
References: <BN6PR2001MB10741D95D8FAAD06783E1C63F1D40 AT BN6PR2001MB1074 DOT namprd20 DOT prod DOT outlook DOT com> <20170705142723 DOT GH30902 AT calimero DOT vinschen DOT de>
To: cygwin AT cygwin DOT com
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Message-ID: <73c6d340-012c-b6f7-e82c-804b7031e713@SystematicSw.ab.ca>
Date: Wed, 5 Jul 2017 13:52:01 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170705142723.GH30902@calimero.vinschen.de>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-CMAE-Envelope: MS4wfLnijcMtK7swU8/SFvjFKFRGexGjnLd9bKfOTagxLxshVat3OiEM50y0tmXbqiesUgXl9yoxqhT9r/zjkh5Cp7PIWq2eDut1QPOeyYpV4tU4b5XyJudV 3B2f4YCvgwD5GyJ8lCZbggAEvSL+zukY42zcPDPe/FSBoSpNvAvvOyZXKOFCF3Fnczad5vIou5/XJA==
X-IsSubscribed: yes

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