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 13:36:57 +0200 Message-ID: In-Reply-To: <5ae77b7d-d239-4ef5-a1c8-75e966a5225d@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============9095793020388679096==" List-Id: --===============9095793020388679096== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hi Michael, On 01/10/2023 12:24, Adolf Belka wrote: > Hi Stefan, > > On 30/09/2023 20:05, Stefan Schantl wrote: >> Hello *, >>> 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 >>> "Segmentation fault" >> >> I can confirm this issue. When the pakfire-builder binary is started it >> directly get killed by a SEGV. >>> >>> Rolling back to >>> >>> cli: pakfire-builder: Implement "image create" >>> >>> then worked with beep fine. >>> >>> Then tried git pull, make, make install again and this time beep >>> built >>> without any problems. Then I tried sqlite and I got the segmentation >>> fault again. >>> >>> Then I rolled back and sqlite built okay. Then ran sqlite again and >>> this >>> time part way through building my laptop logged out from my session. >>> >>> Logged back in and ran sqlite again and this after a short while >>> everything 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 >>> different 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 >>> problems so that commit stage is confirmed good. >> So far running a build of any existing packages seems to work without a problem. I am then creating a python3-build-0.9.0 build as that version still has setup.py to use that as the bootstrap for the newer python3-build package. Tested running python3-build-0.9.0 and it goes to download the package and then has a segmentation fault. I changed the package name to just python3-build but the same segmentation fault occurred. Maybe I need to roll back to an even earlier commit of the git branch. Regards, Adolf. >> 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: >> >> https://bugzilla.ipfire.org/show_bug.cgi?id=13362 >> >> Can you please check, if you are affected by this issue too? > I have added my input into the bug report. > > Regards, > Adolf >> >>> >>> Let me know if there is anything else I should try to narrow the >>> problem >>> down. >>> >>> Regards, >>> Adolf. >>> >> Best regards, >> >> -Stefan >> > -- Sent from my laptop --===============9095793020388679096==--