From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tremer To: development@lists.ipfire.org Subject: Re: pakfire-builder problems after git pull Date: Sun, 01 Oct 2023 13:23:49 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7867853976865339927==" List-Id: --===============7867853976865339927== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable > On 30 Sep 2023, at 19:05, Stefan Schantl wrot= e: >=20 > Hello *, >> Hi Michael, >>=20 >> I just ran git pull which took me to commit >>=20 >> build: Add implicit dist() when a makefile is passed -- followed by=20 >> make and make install. >>=20 >> Running pakfire-builder build beep/beep.nm gave the error message=20 >> "Segmentation fault" >=20 > I can confirm this issue. When the pakfire-builder binary is started it > directly get killed by a SEGV. Is this on Debian? It works fine for me on Debian Bookworm. >>=20 >> Rolling back to >>=20 >> cli: pakfire-builder: Implement "image create" >>=20 >> then worked with beep fine. >>=20 >> Then tried git pull, make, make install again and this time beep >> built=20 >> without any problems. Then I tried sqlite and I got the segmentation=20 >> fault again. >>=20 >> Then I rolled back and sqlite built okay. Then ran sqlite again and >> this=20 >> time part way through building my laptop logged out from my session. >>=20 >> Logged back in and ran sqlite again and this after a short while=20 >> everything froze and I had to reset the laptop. >>=20 >> So rolling back to >>=20 >> cli: pakfire-builder: Implement "image create" >>=20 >> Does not stop the problem happening it just seems to show itself in=20 >> different forms. >>=20 >> I have now rolled back to >>=20 >> cli: pakfire: Implement --yes >>=20 >> which I think is where my last git pull had placed me. >>=20 >> Running pakfire-builder on beep twice and sqlite four times has given >> no=20 >> problems so that commit stage is confirmed good. >=20 > At this stage the pakfire-builder works fine again and is able to build > packages. But I found an additional issue when using this git state: >=20 > https://bugzilla.ipfire.org/show_bug.cgi?id=3D13362 >=20 > Can you please check, if you are affected by this issue too? I cannot reproduce this problem whatsoever. >=20 >>=20 >> Let me know if there is anything else I should try to narrow the >> problem=20 >> down. >>=20 >> Regards, >> Adolf. >>=20 > Best regards, >=20 > -Stefan --===============7867853976865339927==--