=== amitk_ is now known as amitk [09:12] tharrrk, failed in what sense [09:12] as i do not expect builds for i386 as it is no longer supported on the higher numbers [15:55] good morning all [15:56] I noticed that there's a kernel update today. I'm wondering whether it will overwrite my custom-patched kernel. [15:56] aberrant, that would depend on what version you have on your custom-patched kernel [15:56] 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] apw: it looks like apt installed 5.3.0-24 on my other system [15:57] 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] 5.3.10 or 5.3.0? [15:57] if the package is also called 5.3.10, then it should have a higher version [15:57] .10 [15:58] I built the custom kernel off of the master branch, I guess [15:58] seth@hydrogen:~/dev/kernel/eoan$ git status │On branch master │Your branch is ahead of 'origin/master' by 1 commit. [15:58] yup [15:59] and how did you biuld it, as if you used ubuntu packaging it would have suppressed the .10 [15:59] apw: I followed connor_k's instructions :) [15:59] make -j6 bindeb-pkg [16:00] yeah so using debian's build, so sounds like you have higher versions, so you will be ok [16:00] so an apt upgrade will not overwrite my kernel? [16:00] I guess I can always reinstall it, but... [16:00] it would be great to get this patch into the mainline kernel. [16:01] running custom makes me nervous. === henrix_ is now known as henrix === ben_r_ is now known as ben_r