> I believe we can close this bug.

The change to the wiki is welcome, since it now reflects the current
situation.

However, in my opinion, the real problem uncovered here has not been
addressed:

Ubuntu should provide mainline kernels built with the latest LTS
toolchain alongside the current one that uses bleeding edge toolchains,
so that using/testing more recent kernels becomes more accessible to a
wider audience (i.e., the vast majority who does not compile their
kernels from source).

Historically, Ubuntu has had a major barrier to adoption: new users who
buy their hardware in between LTS cycles will usually have a very sub-
par experience with Ubuntu because of the outdated kernel. Their choice
is to either:

- use the latest intermediate release, which may still not provide a recent 
enough kernel and is a bad choice for a first time user anyway
- use the latest LTS which may not be usable at all on their systems with the 
very outdated kernel (this tends to happen a lot with laptops in particular).

With all due respect to the user who put up 
https://launchpad.net/~tuxinvader/+archive/ubuntu/kernel-build-tools and their 
efforts in doing so, there should be an official PPA/infrastructure in place 
for this. We all know users installing lots of PPAs without thinking is a huge 
risk and a practice that is advised against.
But then you can't just leave the user with only one remaining, untenable 
choice, which is for their system to be unusable, in the name of security 
concerns that they don't quite understand.
This is a common criticism of Ubuntu: it effectively _forces_ users into 
installing a whole bunch of random PPAs willy-nilly to get certain basic 
features.

Until something is done about this, "LTS" releases are actually unusable
(or usable with many jarring bugs) for many users. The HWE releases are
better than nothing, but not nearly enough.

A post above put it very nicely:

> If you are telling people that you are going to support it for 5
years, then that means being able to provide security updates to them as
well as allowing them to use hardware that was created during the 5
years following April 2020 within reason. To do that, people must be
able to update the kernel plain and simple.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1926938

Title:
  Recent mainline packages are built with Hirsuite 21.04, not Focal
  20.04 LTS

Status in linux package in Ubuntu:
  In Progress

Bug description:
  Hi all,

  The Mainline wiki states that the mainline kernels are built with the
  previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are
  being built with Hirsuite 21.04, and before that Groovy? If this is
  intentional, then the wiki should be updated to reflect the change in
  policy.

  From https://wiki.ubuntu.com/Kernel/MainlineBuilds

    Mainline kernel build toolchain
    These kernels are built with the toolchain (gcc, g++, etc.) from the 
previous Ubuntu LTS release. 
    (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic 
Beaver", etc.) Therefore, 
    out-of-tree kernel modules you already have built and installed for use 
with your release kernels 
    are not likely to work with the mainline builds.

  The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On
  my Focal LTS system I have GCC 9.3.0.

  The Mainline kernel build toolchain
  These kernels are built with the toolchain (gcc, g++, etc.) from the previous 
Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 
18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already 
have built and installed for use with your release kernels are not likely to 
work with the mainline builds.

  The *linux-headers-generic* packages have unmet dependencies on 20.04
  LTS.

  I could install Groovy built kernels fine, but the Hirsuite ones built
  with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels
  can't be installed on Focal (libc 2.31).

  Thanks,
  Mark

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to