Re: pakfire-builder problems after git pull

[Michael Tremer <michael.tremer@ipfire.org>]

[-- Attachment #1: Type: text/plain, Size: 2093 bytes --]



> On 30 Sep 2023, at 19:05, Stefan Schantl <stefan.schantl(a)ipfire.org> 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.

Is this on Debian? It works fine for me on Debian Bookworm.

>> 
>> 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.
> 
> 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 cannot reproduce this problem whatsoever.

> 
>> 
>> Let me know if there is anything else I should try to narrow the
>> problem 
>> down.
>> 
>> Regards,
>> Adolf.
>> 
> Best regards,
> 
> -Stefan