public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: pakfire-builder problems after git pull
Date: Sun, 01 Oct 2023 12:24:55 +0200	[thread overview]
Message-ID: <5ae77b7d-d239-4ef5-a1c8-75e966a5225d@ipfire.org> (raw)
In-Reply-To: <d3ee0e35f33e88a203125361c7cb1f1542507855.camel@ipfire.org>

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

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.
> 
> 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

       reply	other threads:[~2023-10-01 10:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d3ee0e35f33e88a203125361c7cb1f1542507855.camel@ipfire.org>
2023-10-01 10:24 ` Adolf Belka [this message]
2023-10-01 11:36   ` Adolf Belka
2023-10-01 11:57     ` Adolf Belka
2023-10-01 12:23 ` Michael Tremer
     [not found] <2266243C-8D28-4AAE-9F3B-A653A0C9B81E@ipfire.org>
2023-10-01 12:51 ` Adolf Belka
2023-10-01 14:24   ` Adolf Belka
2023-10-01 16:11     ` Adolf Belka
2023-10-08 16:14       ` Michael Tremer
2023-10-08 16:14         ` Adolf Belka
2023-10-08 16:14           ` Adolf Belka
2023-10-11 13:08           ` Adolf Belka
2023-10-11 13:34             ` Michael Tremer
2023-10-11 14:27               ` Adolf Belka
2023-11-02  8:26                 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5ae77b7d-d239-4ef5-a1c8-75e966a5225d@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox