X-Authentication-Warning:	delorie.com: mail set sender to geda-user-bounces using -f
X-Recipient:	geda-user AT delorie DOT com
X-Original-DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=content-transfer-encoding:content-type
	:date:from:in-reply-to:message-id:mime-version:references
	:reply-to:subject:to:x-me-proxy:x-me-proxy:x-me-sender
	:x-me-sender:x-sasl-enc; s=fm1; bh=1xS/u3s+d08agV5S80qIDN6p0XdAh
	E166Bqd2VWY5Sg=; b=RIUCZy8qK3COWyeKUbwa7/z+8Y90jrEwcfM1mYEZHowy6
	H15JMlkw/8Tkk8hwYEiKTKNBKKNlMuXgw838ZPAvK6TygTAg9iAE8+F8WCzJfr/A
	wowvf/MuEiLS2KRl48CyS/j2OUWFKRqtgFa3O4mH5dBxYR2ofTXuTPNe+q5Rs2dn
	BbKgc0bJzF01PxUUkdWAfs2qYXhx85Ayhiy81z9f2pn4AzZC51AjonsWvUU1Y6j/
	SmlNuo5K5DmFTJaq4fKwyji0jO9Sswn9i5Nr4EfS5w4WQjyYlIt0M84R8iInjxve
	SUn0b3kARDZ3QBZnEnvUb/wNzrO4CyRcxb9EjgrGg==
X-ME-Sender:	<xms:PxjpX8COUQ0R-H-UaDTq8n1F2bQEiGCqLj_p8_D-llBFeMZAezgKSw>
	<xme:PxjpX-hj8FI2rpYqP3CIADPiWQP6XS98MzwBPM0fNuNI4rYoyMdtFziIslmk0Bn1U
	zlUeiwTxG6C-Fa_VQ>
X-ME-Proxy-Cause:	gggruggvucftvghtrhhoucdtuddrgedujedrvddukedgtdekucetufdoteggodetrfdotf
	fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
	uceurghilhhouhhtmecufedttdenucenucfjughrpehruffvfhfhkffffgggjggtgfesth
	ejredttdefjeenucfhrhhomhepifhirhhvihhnucfjvghrrhcuoehghhgvrhhrlhesfhgr
	shhtmhgrihhlrdgtohhmqeenucggtffrrghtthgvrhhnpedvudelfffgudduieevveelie
	ekveetiefghfehvdfhjedvffejieeileffjefhvdenucfkphepuddtkedrvdduhedrudel
	hedrvddtheenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh
	hmpehghhgvrhhrlhesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy:	<xmx:PxjpX_lRXYvAjHoxB8FKz_Ay8HIdzN_9xU5Be96JCvyDcG8Cf2JMSg>
	<xmx:PxjpXywJ0fLsq6cFYaper1gfOf0T9xmP8qeIdFNzT_BEZQy6OqBXJQ>
	<xmx:PxjpXxQ0EgoKnp0_JxkGaAM09fp9Z8jkjmbZoKzUK1tETIpBKrWu6Q>
	<xmx:QhjpX4cRPc2lci_v-dqJAw5F36yU8VKFO-fJzSyYvXcnJC6HXe7eoZ74O5c>
Subject:	Re: [geda-user] gsymcheck 'make check' failure final analysis
To:	geda-user AT delorie DOT com
References:	<alpine DOT DEB DOT 2 DOT 21 DOT 2012222348500 DOT 521 AT nimbus>
	<09a3adc8-401f-70fd-1ba4-c5cc850f62aa AT fastmail DOT com>
	<5a52e3b4-50a6-2b0e-7d7d-7eb144c5619f AT epilitimus DOT com>
	<ebab350e-1ca4-505f-2155-a376ca8350ac AT fastmail DOT com>
	<1d8bac3a-9787-dd41-9269-ab8d3d681754 AT epilitimus DOT com>
	<54c87596-c5ef-cfba-d74d-2fa6411b555f AT fastmail DOT com>
	<dc4e8a13-d29e-8c22-7957-77acacd2aba9 AT epilitimus DOT com>
	<796bed87-7c91-fe93-fbfa-7090c731be36 AT epilitimus DOT com>
	<alpine DOT DEB DOT 2 DOT 22 DOT 394 DOT 2012271434420 DOT 2232 AT yoga>
	<c037a620-99de-8b31-88ac-ed0b24f4f8a3 AT epilitimus DOT com>
	<e8a3e15b-b7ff-d46d-b4ee-0b1aec553983 AT fastmail DOT com>
	<cce60f7a-d240-3a0c-b1ef-afd44c6a67fd AT epilitimus DOT com>
From:	"Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
Message-ID:	<31e646f5-7595-cda9-7b6a-d9774efce8cc@fastmail.com>
Date:	Sun, 27 Dec 2020 15:24:40 -0800
User-Agent:	Mozilla/5.0 (X11; Linux i686; rv:68.0) Gecko/20100101
	Thunderbird/68.12.0
MIME-Version:	1.0
In-Reply-To:	<cce60f7a-d240-3a0c-b1ef-afd44c6a67fd@epilitimus.com>
Reply-To:	geda-user AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	geda-user AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 12/27/20 2:17 PM, Glenn (glimrick AT epilitimus DOT com) [via 
geda-user AT delorie DOT com] wrote:
> Girvin Herr (gherrl AT fastmail DOT com) [via geda-user AT delorie DOT com] wrote:
>> I have been giving some thought about this problem overnight and I
>> have decided this is not so much a bug in gEDA as it is a problem with
>> my package build process. As observed, this failure only happens when
>> the ~/.gEDA/gafrc file exists. Most people probably build the package
>> as root, where this file is non-existent (if they are smart, they are
>> not running gEDA programs as root), so they will not see this problem.
>> However, my package build process has two stages. First, I build in my
>> user account, which I do use for gEDA projects and it does have the
>> ~/.gEDA/gafrc file. Then, when I am satisfied that that build stage is
>> safe and correct, I go to stage 2, where, as root, I build the final
>> package and install it.
>>
> I use the same technique since as 'me' the build can't write to any
> system directories, which it shouldn't be trying to do anyway.
GH: Yes. I started doing this when a package I was building as root 
changed all /usr/* permissions to 400, with the obvious repercussions. 
It took me a long time to correct it and when I was done, I still wasn't 
sure I got them all right. And this was a respected app supplier. Now, 
when I see a "permission denied" during stage 1, I know it is doing 
something ill-behaved.
>> IMHO, this is not a bug in gEDA and it may not be a good idea to
>> incorporate test-specific code in gEDA, just to keep this "problem"
>> silent. An example would be Volkswagen a few years ago was caught
>> putting factory test code in their engine computers which disabled the
>> emissions functions. This turned sour when the EPA discovered this
>> code was running on their vehicles on the highway and polluting the
>> air. As a result, VW got a stiff fine and their reputation is still
>> not back to what it was before this incident.
>>
> Only reason I think it might be an issue is for people doing an upgrade
> build. But Roland seems to have something up his sleeve that will make
> it all moot. So other than putting in my two cents worth, which I think
> I have, and lending a hand if asked I will probably just drop it.
>
> My brain is happy having solved the problem. :)
>
> Glenn

You have given me far more than 2 cents worth. Thanks very much for the 
help. I will hold off "Solving" this thread until I get it working under 
the new account next week. If that works, then I will consider it solved 
- or at least understood.

Take care and Happy New Year.

Girvin

- Raw text -