From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Help with an IPFire-3.x pakfire build failure
Date: Mon, 04 Dec 2023 17:38:37 +0000 [thread overview]
Message-ID: <389B91FE-342D-4296-B635-0D9B761BFD90@ipfire.org> (raw)
In-Reply-To: <f07c69e1-56f7-4103-a234-9ffb77b7f752@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
What is the error that you are getting?
> On 3 Dec 2023, at 17:18, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>
> Hi Michael + all,
>
> I was running an update build of lvm2 and the build failed near the end.
>
> I looked through the logs and found that there was an FHS error.
>
> I remember from the weekend on IPFire3 that we held that if I want to look through the built file structure that there was a command to add into the .nm file to cause the build to exit without clearing all the build files away.
>
> Unfortunately
>
> 1) I can't remember what the command to add into the .nm file is. I tried exit but pakfire just said that it couldn't understand the .nm file with that included.
>
> 2) Even if I could cause pakfire to stop, while leaving the build file structure in place, I also can't remember where the build structure in IPFire-3.x is located.
>
> Any help would be gratefully accepted and welcomed.
>
> Regards,
>
> Adolf.
>
next prev parent reply other threads:[~2023-12-04 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 17:18 Adolf Belka
2023-12-04 17:38 ` Michael Tremer [this message]
2023-12-04 18:09 ` Adolf Belka
2023-12-06 12:35 ` Michael Tremer
2023-12-06 14:32 ` Adolf Belka
2023-12-06 15:32 ` Adolf Belka
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=389B91FE-342D-4296-B635-0D9B761BFD90@ipfire.org \
--to=michael.tremer@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