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=fastmail.com; h=
	cc:content-type:content-type:date:date:from:from:in-reply-to
	:in-reply-to:message-id:mime-version:references:reply-to:sender
	:subject:subject:to:to; s=fm3; t=1689273926; x=1689360326; bh=zq
	pXR/TmctiztxlaeQnfuyesj4thPuLvE0E/ZhArtlE=; b=K9hzzyyf3NVWMWJ9Qi
	hD/DKcguUGSc6akXz5bIitoTI4AiBBf44ePBeJQZwSO70u/Iyi2jDfaS0MS7bnjn
	d4/XXXdw3UXWEk+hZN0Es6DeWr/OxFIJ9EJi/GteKu8siuUXoetTPj7mmuhSHs4i
	Ynvq1QsBKnVd93Ua/VRD0ykZNe1YdFl9su013ileFn5py8wCXdg22qMtznREWgT8
	Odc0vv405jNO0LCo5gSmivxO/iZPp///ILuhPoaBdOBZqL3PUyTmN5f9/tEP4lXi
	N4vDpkmThDaPXcuSbDTAtQOfqMC+LgAny3R6eG1wpoGeL7mYeYXg8r3dfVxw4dWb
	pA5g==
X-Original-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
	messagingengine.com; h=cc:content-type:content-type:date:date
	:feedback-id:feedback-id:from:from:in-reply-to:in-reply-to
	:message-id:mime-version:references:reply-to:sender:subject
	:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender
	:x-sasl-enc; s=fm3; t=1689273926; x=1689360326; bh=zqpXR/Tmctizt
	xlaeQnfuyesj4thPuLvE0E/ZhArtlE=; b=TnwUvFHHQBXoqCzZMFmxodvF4K8wU
	2BTn7ci0SffYahWnMTy/yPkb2GrJ6qpss72qA0pdaJstPBY30C7uAQ9IF87O/qRV
	rLRfgjx6Cj6HEUSNiau7kHvSIfUPS2/bv8YDRcaiWwn/ZVK1ub61Xzq4K87zFBlq
	LyMjuleQZBnk3x8ex46tZBNJZx3mmB81FUN0IuqONUzCGUWQTdsJWeTu66zHitum
	yninQknYCAau5f3IBpCJ9ctXgeR8c0HR66Da/AHarVI0ibP8cnwTRvvAlDKbg7FH
	mhK3I9O9QI2rTnZUe5zd6PZXSF6pzlifWEkUkXdAgVBMbT6HWvndeeFRw==
X-ME-Sender: <xms:RUawZAALHfLgvs47PSOiy1XAshoI2VVPkq4zipPt4oHImqf338O_DA>
    <xme:RUawZCjLNZqhyO6z9nULm4SFhQFC8xB0d-cgUP3OiBStanskOc0VWEFVDtoqPJ9oy
    U28zvYeOWz1ttG6Ag>
X-ME-Received: <xmr:RUawZDnIre1kBkFEb8wDHAFdUK-uxiDkr_snRyh4_n57o8zc8USZ4W326uSuwcJ3F9FlWy4FPz_KS5Lq6eIBfB5Hw8rR64PNNXZ48Nts5ibbmZCFUrKBDUeS8Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrfeeggdduvdekucetufdoteggodetrfdotf
    fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen
    uceurghilhhouhhtmecufedttdenucenucfjughrpegtkfffgggfuffvfhfhjgesrgdtre
    ertdefjeenucfhrhhomhepifhirhhvihhnucfjvghrrhcuoehghhgvrhhrlhdvsehfrghs
    thhmrghilhdrtghomheqnecuggftrfgrthhtvghrnhepvdeujefhffejleekjeejtdeihe
    fghfffjeefkedtieekleeigfegtddvkeffueeknecuffhomhgrihhnpehslhgrtghksghu
    ihhlughsrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh
    hfrhhomhepghhhvghrrhhlvdesfhgrshhtmhgrihhlrdgtohhm
X-ME-Proxy: <xmx:RUawZGziUJw1FIN9XvGDRtzEHRzGLFt2sZeBqGgH2CS6pDO29TziiQ>
    <xmx:RUawZFQ0sdkj0Co01SgIOsy8-JbCyFXlumGNebbpKs76m2koGr08Tg>
    <xmx:RUawZBZczXvQ96UVX7WYQW-wf4pMPm6HcX7jtCNEFayG7VYAPxVnyw>
    <xmx:RkawZAM7qe6ZM3jgl3c83mhiNly-t9_WXJVfes1s2GQynfIyGPCIow>
Feedback-ID: iee494631:Fastmail
Content-Type: multipart/alternative;
 boundary="------------XjIMgP6G9kHlmlku5Il4rDmw"
Message-ID: <2013e57f-eb6a-6d4f-9ea9-766838a077a2@fastmail.com>
Date: Thu, 13 Jul 2023 11:43:39 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.11.2
Subject: Re: [geda-user] geda-gaf 1.10.2 make check test failure
Content-Language: en-US
To: geda-user AT delorie DOT com
References: <968ccc54-0513-8444-1944-5f98c662eaf2 AT fastmail DOT com>
 <c036e3c-9d7d-83ef-9014-505e19e8cbb3 AT grinsen-ohne-katze DOT de>
From: "Girvin Herr (gherrl2 AT fastmail DOT com) [via geda-user AT delorie DOT com]" <geda-user AT delorie DOT com>
In-Reply-To: <c036e3c-9d7d-83ef-9014-505e19e8cbb3@grinsen-ohne-katze.de>
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
Precedence: bulk

This is a multi-part message in MIME format.
--------------XjIMgP6G9kHlmlku5Il4rDmw
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi Roland,

Thanks for your prompt reply.

With all due respect, in the case of building Slackware-installable 
packages, I must build them as root. Step #4 in the following:

    https://www.slackbuilds.org/howto/

_My_ Slackware package BuildScripts for packages do allow me to build 
the package as a regular user, but that is just to first verify the 
build does not do anything ill-behaved, like directly messing with 
root-privileged system files, or not complying with $DESTDIR in make 
install, that would succeed as root, but fail as a user. Yes, that has 
happened to me, with disastrous results. That said, I agree that the 
risk is low in this case and I am going ahead and building the Slackware 
package without the make check. I was just wondering if anyone knew of a 
better solution.

No, I am not running the geda-gaf programs as root.

Thanks again. If I determine any other issues with this, I will update you.

Girvin


On 7/13/23 05:20, Roland Lutz wrote:
> Hi Girvin,
>
> thank you for reporting this issue!
>
> On Wed, 12 Jul 2023, Girvin Herr (gherrl2 AT fastmail DOT com) [via 
> geda-user AT delorie DOT com] wrote:
>> I am building geda-gaf 1.10.2 on my Slackware64 15.0 system for the 
>> first time. It is my policy to build a package twice - once in a user 
>> mode corral to make sure the program builds without going out and 
>> trying to change root-privileged files on my disk and then if it 
>> builds fine there, I go on to build in root for installation.
>
> Building packages doesn't require root privileges, so it shouldn't be 
> done as root.  I'd recommend to either configure gEDA/gaf to use a 
> user-local prefix (e.g., ~/.local/) or just run the "make install" 
> command as root.
>
>> This geda-gaf version built fine in user mode with "make check", but 
>> when I build in root, I am getting a fatal test error:
>>     "unit-tests/t0402-config.scm"
>> Just the one error that I can tell. It appears to pass all the other 
>> tests.
>
> gEDA/gaf isn't intended to be run as root, so it isn't surprising that 
> configuration doesn't behave as expected in this situation, causing 
> the test to fail.  As long as this is the only symptom, I don't feel 
> like it is worth investing the time to look into this, though.
>
> Roland
--------------XjIMgP6G9kHlmlku5Il4rDmw
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi Roland,</p>
    <p>Thanks for your prompt reply.</p>
    <p>With all due respect, in the case of building
      Slackware-installable packages, I must build them as root. Step #4
      in the following:<br>
    </p>
    <blockquote>
      <p><a class="moz-txt-link-freetext" href="https://www.slackbuilds.org/howto/">https://www.slackbuilds.org/howto/</a><br>
      </p>
    </blockquote>
    <p><u>My</u> Slackware package BuildScripts for packages do allow me
      to build the package as a regular user, but that is just to first
      verify the build does not do anything ill-behaved, like directly
      messing with root-privileged system files, or not complying with
      $DESTDIR in make install, that would succeed as root, but fail as
      a user. Yes, that has happened to me, with disastrous results.
      That said, I agree that the risk is low in this case and I am
      going ahead and building the Slackware package without the make
      check. I was just wondering if anyone knew of a better solution.</p>
    <p>No, I am not running the geda-gaf programs as root.<br>
    </p>
    <p>Thanks again. If I determine any other issues with this, I will
      update you.<br>
    </p>
    <p>Girvin</p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 7/13/23 05:20, Roland Lutz wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:c036e3c-9d7d-83ef-9014-505e19e8cbb3 AT grinsen-ohne-katze DOT de">Hi
      Girvin,
      <br>
      <br>
      thank you for reporting this issue!
      <br>
      <br>
      On Wed, 12 Jul 2023, Girvin Herr (<a class="moz-txt-link-abbreviated" href="mailto:gherrl2 AT fastmail DOT com">gherrl2 AT fastmail DOT com</a>) [via
      <a class="moz-txt-link-abbreviated" href="mailto:geda-user AT delorie DOT com">geda-user AT delorie DOT com</a>] wrote:
      <br>
      <blockquote type="cite">I am building geda-gaf 1.10.2 on my
        Slackware64 15.0 system for the first time. It is my policy to
        build a package twice - once in a user mode corral to make sure
        the program builds without going out and trying to change
        root-privileged files on my disk and then if it builds fine
        there, I go on to build in root for installation.
        <br>
      </blockquote>
      <br>
      Building packages doesn't require root privileges, so it shouldn't
      be done as root.  I'd recommend to either configure gEDA/gaf to
      use a user-local prefix (e.g., ~/.local/) or just run the "make
      install" command as root.
      <br>
      <br>
      <blockquote type="cite">This geda-gaf version built fine in user
        mode with "make check", but when I build in root, I am getting a
        fatal test error:
        <br>
            "unit-tests/t0402-config.scm"
        <br>
        Just the one error that I can tell. It appears to pass all the
        other tests.
        <br>
      </blockquote>
      <br>
      gEDA/gaf isn't intended to be run as root, so it isn't surprising
      that configuration doesn't behave as expected in this situation,
      causing the test to fail.  As long as this is the only symptom, I
      don't feel like it is worth investing the time to look into this,
      though.
      <br>
      <br>
      Roland
      <br>
    </blockquote>
  </body>
</html>

--------------XjIMgP6G9kHlmlku5Il4rDmw--