the included snapcraft.yaml means i need to have the whole tree locally
on disk, as someone who maintains a ton of community images for
UbuntuCore i prefer to just have the snapcraft.yaml locally so the disk
is only cluttered during build. along with that i am trying to build the
eoan tree for the core18 Pi4 image i provide, the wlan firmware is not
in the linux-firmware package in bionic, so i need overrides ... beyond
this, a lot of config options that i require to be builtin are modules
and the initramfs handling in snapcraft is still a mess, so i prefer to
build in MMC support and USB disk support... along with this we have a
good bunch of customers building custom kernels with out-of-tree
snapcraft file and brand stores so it helps to know what they
experience.
:)
note that once we have an official core image for the Pi4 i'll drop this
work anyway ...
closing the bug as invalid ...
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851233
Title:
building a snap from the eoan tree using the raspi2 defconfig results
in gigantic snap package
Status in linux package in Ubuntu:
Invalid
Bug description:
typically a kernel snap built from the kernel.ubuntu.com tree using
the raspi2 defconfig results in a snap package that is below 150MB in
size:
$ ls -lh pi2-kernel_raspi2-4.4.0-1110.snap
-rw------- 1 root root 129M Jun 4 15:01 pi2-kernel_raspi2-4.4.0-1110.snap
trying to build a similar snap from the source tree for eoan seems to
add several 100MB of unused modules to the binary, resulting in a
700MB+ snap package
$ ls -lh pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap
-rw-r--r-- 1 ogra ogra 712M Oct 24 15:46
pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap
the snapcraft.yaml used for both cases is
https://paste.ubuntu.com/p/J563CDsdGW/ with modified source tree and
name (one pointing to xenial. the other to eoan) but no other changes
between the two above packages. seems in eoan the defconfig enables a
ton of additional modules (1.6G uncompressed) that have not been there
before:
$ sudo mount -o loop pi4-kernel_raspi2-5.3.0-1008.9_armhf.snap /mnt
$ du -hcs /mnt/*
3.1M /mnt/System.map-5.3.1+
211K /mnt/config-5.3.1+
906K /mnt/dtbs
475M /mnt/firmware
4.5M /mnt/initrd-5.3.1+.img
7.0M /mnt/kernel.img
512 /mnt/meta
1.6G /mnt/modules
2.1G total
$
that will result in unreasonable big ubuntu core images, the list of
included modules should be trimmed for this flavour
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
