[09:12] <apw> tharrrk, failed in what sense
[09:12] <apw> as i do not expect builds for i386 as it is no longer supported on the higher numbers
[15:55] <aberrant> good morning all
[15:56] <aberrant> I noticed that there's a kernel update today. I'm wondering whether it will overwrite my custom-patched kernel.
[15:56] <apw> aberrant, that would depend on what version you have on your custom-patched kernel
[15:56] <apw> aberrant, it will have a newer version that our old one, depends what version you picked; well and what package name used if different etc
[15:56] <aberrant> apw: it looks like apt installed 5.3.0-24 on my other system
[15:57] <aberrant> the system that has the custom kernel is Linux elemental 5.3.10+ #1 SMP Mon Dec 16 15:03:53 PST 2019 x86_64 x86_64 x86_64 GNU/Linux
[15:57] <connor_k> 5.3.10 or 5.3.0?
[15:57] <apw> if the package is also called 5.3.10, then it should have a higher version
[15:57] <aberrant> .10
[15:58] <aberrant> I built the custom kernel off of the master branch, I guess
[15:58] <aberrant> seth@hydrogen:~/dev/kernel/eoan$ git status                                                                                                  │On branch master                                                                                                                             │Your branch is ahead of 'origin/master' by 1 commit.
[15:58] <aberrant> yup
[15:59] <apw> and how did you biuld it, as if you used ubuntu packaging it would have suppressed the .10
[15:59] <aberrant> apw: I followed connor_k's instructions :)
[15:59] <aberrant> make -j6 bindeb-pkg
[16:00] <apw> yeah so using debian's build, so sounds like you have higher versions, so you will be ok
[16:00] <aberrant> so an apt upgrade will not overwrite my kernel?
[16:00] <aberrant> I guess I can always reinstall it, but...
[16:00] <aberrant> it would be great to get this patch into the mainline kernel.
[16:01] <aberrant> running custom makes me nervous.