From: f.louveau@lacroix.group
To: poky@lists.yoctoproject.org
Subject: [LINUX-FIRMWARE] all pacakges in image
Date: Fri, 04 Aug 2023 05:45:29 -0700 [thread overview]
Message-ID: <6Y6K.1691153129635207131.6RdY@lists.yoctoproject.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
Hi,
I encounter some issues with linux-firmware.
My build was configured with tag kirkstone-4.0.8, and today I try to update to latest commit of kirkstone branch (fa7dd8ac75a98c04a4ca2cf90882c2b1c27b9679).
The build leads to an error:
>
> ERROR: <image>-1.0-r0 do_image_tar: The rootfs size 1456576(K) exceeds
> IMAGE_ROOTFS_MAXSIZE: 768000(K)
> ERROR: Logfile of failure stored in:
> /home/user/workspace/kirkstone/build-mymachine/tmp/work/mymachine-poky-linux/<image>/1.0-r0/temp/log.do_image_tar.3783805
>
> ERROR: Task
> (/home/user/workspace/kirkstone/sources/meta-layer/recipes-images/image/<image>.bb:do_image_tar)
> failed with exit code '1'
Using buildhistory, I can see that all linux-firmware packages are embedded in image that is not the case before.
After some bisect analysis, I found that the commit 1752b29e7c8d4c104c99b04400fd88ea985348a5 adds this weird behavior.
Temporarily, I will use tag kirkstone-4.0.11 but want to notice this issue.
Fabrice
[-- Attachment #2: Type: text/html, Size: 1059 bytes --]
next reply other threads:[~2023-08-04 12:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 12:45 f.louveau [this message]
2023-08-04 13:07 ` [poky] [LINUX-FIRMWARE] all pacakges in image Alexander Kanavin
2023-08-04 13:46 ` f.louveau
2023-08-04 14:20 ` [poky] " Martin Jansa
2023-08-04 15:39 ` f.louveau
2023-08-04 15:50 ` [poky] " Alexander Kanavin
2023-08-04 16:04 ` Martin Jansa
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=6Y6K.1691153129635207131.6RdY@lists.yoctoproject.org \
--to=f.louveau@lacroix.group \
--cc=poky@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).