The-going

> Well, yes, but 22.11 > 22.08 which means it should probably be 22.08.1 to 22.11.0-armbian-5.15.64 ? Maybe yes. Probably not. If you think about backward compatibility with existing packages...

Today we are collecting packages in ubuntu `jammy` and distributing them for all supported OS. This is not correct.

Soon I will have more free time and I will state my point of view in an expanded version and propose an algorithm.

> Well, yes, but 22.11 > 22.08 which means it should probably be 22.08.1 to 22.11.0-armbian-5.15.64 ? An idea! REVISION=22.11.0-armbian Until we implement something more significant.

@hzyitc Thanks. I saw it. In fact, it looks like an unfinished job. The choice of packages to install in the future image should occur somewhere at the very beginning...

> Is there a parameter to tell `compile.sh` to leave the intermediate build artifacts form uboot and the kernel instead of removing them? @DaveWK Please decipher in more detail what...

> @The-going what I would like to do is generate the dts/dtsi files that are created/modified by the combination of all the .patch files for a particular board (in this...

> if I could preserve the board-specific u-boot loader files and kernel files My bananapi is connected to a local network via ethernet. And I just unload the collected packages...

@Myron-S There are two main reasons for this failure. 1. The free space has run out. 2. Incorrect spelling of the package name In your log file: debootstrap-list.log ``` PACKAGE_LIST_DESKTOP...

> KERNEL_CONFIGURE="prebuilt" Can take the values `yes` or `no` > [ .... ] Creating device node [ /dev/loop22p1 ] > [ .... ] Creating rootfs [ ext4 on /dev/loop22p1 ]...