I been running my own images with great success thanks to rock solid build environment but one thing that catches me by surprise every now and then is that updating the system can also overwrite my custom kernel, which is is far from ideal. Up until now I been issuing an apt hold command for the packages but I was thinking maybe there is a better way. Because even with the hold in place if I don't pay close attention and do an apt dist-upgrade for example they will still be replaced despite the hold. Is there a better way to prevent my kernels from being updated by the stock kernel?

 

Cheers!

What may help is adding a custom version string in menuconfig when building the kernel package.

Ohh that's a very clever solution! Thank you very much 

Unfortunately it didn't work 

 

use a different package name or higher enough version

or just add SUBREVISION=.99999 to your build command line

31 minutes ago, ning said:

or just add SUBREVISION=.99999 to your build command line

That will be good enough until we bump to 20.08

On 3/9/2020 at 3:40 PM, ning said:

or just add SUBREVISION=.99999 to your build command line

 

Will try, thanks for the suggestion.

 

On 3/9/2020 at 4:13 PM, Igor said:

That will be good enough until we bump to 20.08

 

What would the best way to prevent these kernel upgrades from ever happening? If that's possible of course.

17 minutes ago, stut said:

What would the best way to prevent these kernel upgrades from ever happening? If that's possible of course.

By patching packaging patches or best, implement this as a feature to the build engine.

Edited March 11, 20206 yr by Igor
link to wrong word

Setting the sub-revision seems to have sorted it, but it may be too early to tell as I just build this fresh image. For now looking good, thanks for the pointers everyone.

the simplest way: remove armbian software repo.