unsolved dependency with 5.14.6 kernel - libc6 >=2.34 in Ubuntu 20.04 LTS
edmundlaugasson opened this issue · comments
Currently not possible to install newest kernel 5.14.6 as in latest Ubuntu LTS is libc6 still v2.31, although in Ubuntu 21.10 presumably will be v2.34, but it is not LTS, therefore not used in mission critical computers. Would it be possible to solve? E.g. add newer libc6...
EDIT: found - https://askubuntu.com/questions/1334633/mainline-kernel-now-depends-on-libc6-2-33-non-installable-in-focal
These repos are free from that dependency:
It has always been the case since day one (ie, long before any convenience front-end app like this ever existed) that any given mainline kernel package might not be usable on any given system. This libc thing is just one of countless possible reasons. The only answer to this, right from the mainline-ppa site itself since day one has only ever been (paraphrased) "If a kernel package doesn't work, then modify your system to be compatible, or don't use it, there is no support or promises".
https://wiki.ubuntu.com/Kernel/MainlineBuilds
So, if they change the way the packages are built, and we can't upgrade dependecies to match, then we can't use those packages, simple as that.
It's outside the scope of a .deb installer like this (or muon/aptitude/synaptic/etc) to try to analyse a package and predict whether it will work on the users system. The scope of this app is only: Download .debs and run dpkg -i . That's it.
We might possibly make the main download url into a configurable option so that you could download from an alternate source like those tuxraiser ppa's but then the problem is, half of what this app does is parse the index.html's and directoris on the mainline-ppa site. So an alternative url would only work if the alternate site replicates all the same directory structure and index.htmls and other files just like the mainline-ppa site.
For an ordinary ppa, just install the ppa like any other ppa and you don't need an app like this to stay up to date.
I thought your app is meant to use, which currently isn't possible with newer kernels. I thought you can fix it or know, who can. Just closing issue doesn't solve it... As you see, there is already someone from community, who fixed the issue and proposed own repo for that. This issue renders mainline app useless for Ubuntu 20.04 LTS if it cannot be fixed by Canonical.
You don't seem to understand what's going on, despite my explaination. You want something which doesn't exist. No one from the community "fixed this issue" They simply compiled the kernels themselves in a different environment from what the mainline-ppa web site uses. That in no way resolves the problem that the mainline-ppa site produces kernel packages that aren't installabe on every system.
If you want to build the kernels frm sources, or use some other PPA where someone else did that, go ahead. It has nothing to do with this app. When you use a reglar PPA, you don't need this app. You can just use Muon or Synaptic etc. This app's only reason for existing is to deal with the fact that the mainline-ppa site is NOT a normal PPA and can't be installed in apt like other repos.
Sorry, but you seem not to understand, what I understood (or know). I understand pretty well, what people did and how repos work. Just mention with current issue, that newer kernels cannot be installed with current latest Ubuntu LTS (either with or without your software). Using fancy labels with current issue doesn't fix it or help your software users in any way. I guess providing appropriate warning(s) in your app would be appreciated, so people won't try to install inappropriate kernel(s) and get errors. Fixing those errors needs usually command-line. It would be even friendlier against your program users to let them know, how to fix the issue, when they still installed inappropriate kernel. Currently your app is not capable of fixing that. Perhaps even avoid of installing newest kernels to current latest Ubuntu LTS with appropriate message due to unfixed dependency in mainline-ppa.
At the same time this issue renders your software useless on current latest Ubuntu LTS with newest kernels. I understand, that using someone else's PPA is complex to add into your app. At the same time it could be the solution, as you probably do not plan to start compiling kernels by your own to fix it, which is pointless, as someone is already doing it by providing even PPAs for that. I guess using existing PPA in case of appropriate Ubuntu LTS-version would be much easier than start compiling kernels by your own. Certainly such kernel compiling can be automated but still using already existing repo would be more easier for you to make your software usable again in case of latest Ubuntu LTS with newest kernels.
As you deal more with kernels, then perhaps you know right people to communicate, so it could be fixed at mainline-ppa site. I posted in Ubuntu Kernel Team IRC but it might not the way to reach right people. At the same time it is weird, that Canonical doesn't support their current latest LTS-version...