From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Results from latest test of pakfire-builder
Date: Thu, 02 Nov 2023 08:25:27 +0000
Message-ID: <BEFB3A33-70CB-4898-9DF3-54C851874D20@ipfire.org>
In-Reply-To: <125b7178-bc4d-4fb4-ad08-f2ff2ef2ed31@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1358956256498665715=="
List-Id: <development.lists.ipfire.org>

--===============1358956256498665715==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello Adolf,

I have been looking into this in depth and I cannot find a way to make the bu=
ilder work with all its features unless it is running as root.

So please add a =E2=80=9Csudo=E2=80=9D to the command line and let me know if=
 that brings you any further.

-Michael

> On 30 Oct 2023, at 17:56, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>=20
> Hi Michael,
>=20
> On 30/10/2023 11:01, Michael Tremer wrote:
>> Hello Adolf,
>> Thanks for giving this a try. Is there anything in the logs?
>=20
> In the forum I always remind people to look at the logs. On my Arch Linux s=
ystems I always search through the logs when I have a problem.
>=20
> For some reason with this pakfire package I seem to forget to look in the l=
ogs.
>=20
> Here is what I found when running pakfire-builder build beep/beep.nm (addin=
g --debug made no difference)
>=20
> pakfire[2137]: Mounting /var/tmp/pakfire-root-KRBTNG from pakfire_ramdisk (=
tmpfs - (null))
> pakfire[2137]: Could not mount /var/tmp/pakfire-root-KRBTNG: Operation not =
permitted
> pakfire[2137]: Could not mount ramdisk at /var/tmp/pakfire-root-KRBTNG ((nu=
ll)): Unknown error -1
>=20
> Regards,
>=20
> Adolf.
>=20
>> You can add =E2=80=94-debug to get some more output.
>> Best,
>> -Michael
>>> On 29 Oct 2023, at 13:23, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>=20
>>> Hi All,
>>>=20
>>> I updated my pakfire branch by doing a git pull with all the latest chang=
es and built everything again.
>>>=20
>>> Then tested out by running sudo pakfire-builder build beep/beep.nm
>>>=20
>>> Result was again just going to the prompt with nothing happening.
>>>=20
>>> Ran the commands with gdb and got following result.
>>>=20
>>> sudo gdb pakfire-builder
>>> GNU gdb (GDB) 13.2
>>> Copyright (C) 2023 Free Software Foundation, Inc.
>>> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.h=
tml>
>>> This is free software: you are free to change and redistribute it.
>>> There is NO WARRANTY, to the extent permitted by law.
>>> Type "show copying" and "show warranty" for details.
>>> This GDB was configured as "x86_64-pc-linux-gnu".
>>> Type "show configuration" for configuration details.
>>> For bug reporting instructions, please see:
>>> <https://www.gnu.org/software/gdb/bugs/>.
>>> Find the GDB manual and other documentation resources online at:
>>>     <http://www.gnu.org/software/gdb/documentation/>.
>>>=20
>>> For help, type "help".
>>> Type "apropos word" to search for commands related to "word"...
>>> Reading symbols from pakfire-builder...
>>> (gdb) run build beep/beep.nm
>>> Starting program: /usr/bin/pakfire-builder build beep/beep.nm
>>> [Thread debugging using libthread_db enabled]
>>> Using host libthread_db library "/usr/lib/libthread_db.so.1".
>>> [New Thread 0x7ffff57dd6c0 (LWP 12756)]
>>> [Thread 0x7ffff57dd6c0 (LWP 12756) exited]
>>> [Inferior 1 (process 12752) exited with code 0377]
>>> (gdb)
>>>=20
>>>=20
>>> Regards,
>>> Adolf.
>>>=20
>>> --=20
>>> Sent from my laptop
>>>=20
>=20
> --=20
> Sent from my laptop



--===============1358956256498665715==--