From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: pakfire-builder problems after git pull Date: Sun, 01 Oct 2023 14:51:42 +0200 Message-ID: <3a11e868-1e5e-49c0-b1a1-bb9a79194165@ipfire.org> In-Reply-To: <2266243C-8D28-4AAE-9F3B-A653A0C9B81E@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0076730201273763685==" List-Id: --===============0076730201273763685== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Michael, On 01/10/2023 14:22, Michael Tremer wrote: > Hello, >=20 >> On 30 Sep 2023, at 13:39, Adolf Belka wrote: >> >> Hi Michael, >> >> I just ran git pull which took me to commit >> >> build: Add implicit dist() when a makefile is passed -- followed by make = and make install. >> >> Running pakfire-builder build beep/beep.nm gave the error message "Segment= ation fault" >=20 > I can confirm this, but it seems to be a crash in libcurl/glibc: >=20 >=20 >=20 >> Rolling back to >> >> cli: pakfire-builder: Implement "image create" >> >> then worked with beep fine. >=20 > However, if you say rolling back works, then we must trigger the crash in P= akfire somehow, because libcurl/glibc stays the same. My earlier rolling back worked. However when I then tried to create a=20 new package, python3-build, it then segfaulted again. Then I rolled back a long way and tried again with the python3-build and=20 again it segfaulted. So it looks like the segfault is not always consistent but rolling back=20 did not actually help as there are still packages that end up with a=20 segfault. Regards, Adolf. >=20 > In IPFire we use c-ares as a resolver for cURL which does not crash like th= is. >=20 >> Then tried git pull, make, make install again and this time beep built wit= hout any problems. Then I tried sqlite and I got the segmentation fault again. >=20 > This is very early when Pakfire is starting up and refreshing its repositor= y information. >=20 >> Then I rolled back and sqlite built okay. Then ran sqlite again and this t= ime part way through building my laptop logged out from my session. >> >> Logged back in and ran sqlite again and this after a short while everythin= g froze and I had to reset the laptop. >> >> So rolling back to >> >> cli: pakfire-builder: Implement "image create" >> >> Does not stop the problem happening it just seems to show itself in differ= ent forms. >> >> I have now rolled back to >> >> cli: pakfire: Implement --yes >> >> which I think is where my last git pull had placed me. >> >> Running pakfire-builder on beep twice and sqlite four times has given no p= roblems so that commit stage is confirmed good. >> >> Let me know if there is anything else I should try to narrow the problem d= own. >=20 > Good question. I have a VM with archlinux where I can reproduce the crash. = I will have a look what I can do to fix this=E2=80=A6 >=20 > -Michael >=20 >> >> Regards, >> Adolf. >> >> >> --=20 >> Sent from my laptop >> >=20 --=20 Sent from my laptop --===============0076730201273763685==--