Doug Newgard <dnewgard@xxxxxxxxxxx> wrote:
> On Fri, 25 Aug 2023 18:53:07 -0500
> "David C. Rankin" <drankinatty@xxxxxxxxx> wrote:
>
> > On 8/25/23 18:30, Doug Newgard wrote:
> > > On Fri, 25 Aug 2023 17:49:03 -0500
> > > "David C. Rankin" <drankinatty@xxxxxxxxx> wrote:
> > >
> > >> All,
> > >>
> > >> This shouldn't happen, but the linux-6.4.11 to linux-6.4.12 broke the
> > >> dkms build of virtualbox 6.1.46 modules. Specifically from the log:
> > >
> > > Pretty normal, actually. If you want to run an old version, it's your
> > > responsibility to make it work. Kernels breaking compatibility happens all
> > > of the time.
> > >
> > >> Should I open a bug with Arch?
> > >
> > > No, this is not an Arch issue, as Arch doesn't ship virtualbox 6.1.46
> > > modules.
> > >
> > > Doug
> >
> > True but was that a kernel change or an Arch change to the kernel that broke
> > it?
> >
>
> What do you think Arch does to the kernel?
Doesn't usually everything arch does to the kernel are the few lines in
between `Arch Linux kernel vA.B.CC-arch1' and `Linux A.B.CC'? As in
$ git log --oneline -n6
477b5e926a64 Arch Linux kernel v6.4.12-arch1
879f0f7fc0f9 sphinx: kfigure.py: Convert outdir to str before using len
e5f6f3e36b5e tpm: Don't make vendor check required for probe
3720e1b0eb7d drivers/firmware: skip simpledrm if nvidia-drm.modeset=1 is set
093ed5b87ed2 ZEN: Add sysctl and CONFIG to disallow unprivileged CLONE_NEWUSER
05d8970cca01 Linux 6.4.12
?
--
u34
> But really, does it even matter?
> Arch keeps the modules in the repo up to date, including patching them when
> necessary for newer kernels. Again, if you want to run an old version that Arch
> doesn't maintain, that part is up to you. Maybe check what Arch does? Or see if
> upstream has patches?
>
> > Additionally,
> >
> > This is not an old version. 6.1.46 was released July 31, 2023, less than
> > 30 days ago.
>
> Nobody cares if its lts/still supported, 6.1 is an old version; end of story.
> Even upstream lists it under "Old Builds". Arch is on 7.0 and maintains that. If
> you don't want to use that, it's on you.
>
> And 6.1.46 was July 18th, not 31st, and is only supported for a few more months.
>
> Doug
