public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: jon <jon.murphy@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Error message at end of build for a package that I have not touched
Date: Sat, 12 Oct 2024 10:11:35 -0500	[thread overview]
Message-ID: <B5AFA931-F86D-400F-85F9-B1EAEC577973@ipfire.org> (raw)
In-Reply-To: <981F2AEF-F28C-43B9-820D-C55BD392AD02@ipfire.org>

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

But the build is not completing (no images, no packages).

How do I get the build to finish?



> On Oct 12, 2024, at 4:22 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
> 
> You can ignore this for now.
> 
>> On 12 Oct 2024, at 00:15, jon <jon.murphy(a)ipfire.org> wrote:
>> 
>> I see the same error but I am not sure of the fix.
>> 
>> python3-click (8.1.3)                                                                               [        0 ][ DONE ]
>> Checking for missing rootfiles...
>> 8812au-20210629-e6a0d1704ccd31145800ff5eb09ec2435a02f995-kmod-6.6.47-ipfire is missing a rootfile               [ FAIL ]
>> Checking for rootfile consistency...
>> *** Build Finished                                                                                  [  2:42:50 ][ DONE ]
>> jon(a)deb12HPZ:~/development/ipfire-2.x$ 
>> 
>> My build does not properly end.
>> 
>> Do I need to add something to a rootfile somewhere?
>> 
>> Thank you!
>> Jon
>> 
>>> On Aug 27, 2024, at 5:02 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>>> 
>>> No, this is not really new… It is because of the braindead kernel root file system. I am going to ignore this for now.
>>> 
>>>> On 27 Aug 2024, at 10:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>> 
>>>> Hi Michael,
>>>> 
>>>> The last few build I have been doing I get the following message at the end of the build.
>>>> 
>>>> Checking for missing rootfiles...
>>>> 8812au-20210629-e6a0d1704ccd31145800ff5eb09ec2435a02f995-kmod-6.6.47-ipfire is missing a rootfile    [ FAIL ]
>>>> 
>>>> Not touched that file.
>>>> 
>>>> It doesn't show up in the list of changed files so no problem with doing my builds for update patches.
>>>> 
>>>> Regards,
>>>> 
>>>> Adolf.
>>>> 
>>> 
>> 
>> 
> 





  reply	other threads:[~2024-10-12 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D5CF923E-FABA-4665-B1D7-6521F0D3D702@ipfire.org>
2024-10-12  9:22 ` Michael Tremer
2024-10-12 15:11   ` jon [this message]
2024-10-12 15:12     ` Michael Tremer
2024-10-12 15:56       ` Adolf Belka
2024-08-27  9:58 Adolf Belka
2024-08-27 10:02 ` 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=B5AFA931-F86D-400F-85F9-B1EAEC577973@ipfire.org \
    --to=jon.murphy@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