Updates and fixes are desirable most of the time (specially as final user). However, in my experience when building custom images and adding custom changes, not controlling if/when the latest patch is applied can be undesirable, e.g. when validating your own changes. So, I'd say this type of feature would help determinism and reliability for users customizing images. Finally, when a new version of the system does not work as intended, is cool being able to build a previous version and continue working on some other features/modifications. Thanks anyway, I am aware of the effort put in Armbian, being as is very useful for people like me.
Hi guys, New over here. I have been building custom images without issues for some time for Nano Pi M4. From last week it seems it is not longer building them. In case my build env was corrupted, image build process was tested on a clean VM build env with Ubuntu 18.04, without any customization, following instructions in https://docs.armbian.com/Developer-Guide_Build-Preparation/). I am just trying to buildi kernel image at the moment. In any case, I am seeing some of the rockchip kernel patches are not being applied for some reason, and a compiler error is produced when building the kernel (specifically: looback block dev module). Anybody else is experiencing this? By the way, is there any way to keep a "frozen" build environment with kernel and image components not being updated for sequential builds in time? I couldn't find any information searching out there on this aspect, and definitely is a nice to have feature. Thank you in advance.