Incomplete installs of several latest mainline kernels

[bkw777]

Incomplete installs of several latest mainline kernels

[brmmm3]

I've observed the same issue several times. Only the headers got downloaded and installed. A check at the repo showed that only the headers are available. To solve this issue please implement a check if all necessary files are available and only mark these kernel versions as installable.

[gubagu]

Same here on Ubuntu 20.04.1 LTS.

[StatusCode404]

@bkw777 any ideas on the above?

[tosziro]

Looks like its broken build on Ubuntu side.
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.9.13/

Status is - Build failed

[nseb]

5.10.0-rc7 same problem

[niculw]

No files showing at all for 5.10.0 release

[bkw777]

No files showing at all for 5.10.0 release

5.10.0 worked just fine for me just now.

Are we just seeing internet transientness? Anything that relies on getting something from the net will sometimes fail to be able to get something. It doesn't necessarily mean it's not there or doesn't work, it just means try again later. Maybe one second later, maybe 2 days later. Sometimes the network is fine but the files really don't exist, like broken builds. Sometimes the build was complete but the path from you to the server is temporarily bad, or the server is temporarily bad from load. Sometimes it's this app actually borking up it's cache or tmp files.

We definitely need to get some better form of error reporting so the user can tell the difference between some of those different cases above. If the build failed or the server isn't responding or the server isn't reachable, we should be able to tell that in each case and say so to the user.

[StatusCode404]

No files showing at all for 5.10.0 release

5.10.0 worked just fine for me just now.

Are we just seeing internet transientness? Anything that relies on getting something from the net will sometimes fail to be able to get something. It doesn't necessarily mean it's not there or doesn't work, it just means try again later. Maybe one second later, maybe 2 days later. Sometimes the network is fine but the files really don't exist, like broken builds. Sometimes the build was complete but the path from you to the server is temporarily bad, or the server is temporarily bad from load. Sometimes it's this app actually borking up it's cache or tmp files.

We definitely need to get some better form of error reporting so the user can tell the difference between some of those different cases above. If the build failed or the server isn't responding or the server isn't reachable, we should be able to tell that in each case and say so to the user.

Hi Brian,
I believe what niculw is describing is what shows when you hover your mouse pointer over 5.10.0 release in the Mainline GUI. Basically shows nothing. But if you install anyway it picks up the correct files and installs them correctly.
Then after install the GUI shows the right packages/files from there on. If you uninstall it from that point, it will still continue to show the correct packages even if not installed. it is just that first time where no packages are shown.

However that said I just tried now 5.9.13 and 5.9.14 and they both downloaded just one package and finished with no error when it should have shown a failure message.
After refresh, both kernels where not installed and were both correctly showing not being in place in the GUI. That adds to the confusion because it didn't fail during the install.

[niculw]

No i litterally mean the program says “amd64 directory doesnt exist” and then quits. No downloading of any files. Im gonna try to rebuild.

[niculw]

This is what happens if i use terminal to try and install 5.10.0:

[bkw777]

please implement a check if all necessary files are available

There is no consistent rule to define "all necessary files"

So that's rather easier to demand than to accomplish.

We could maybe parse index.html for the "failed" notice, but that isn't consistent either.

It probably needs a table of different parsers or rules for different ranges of dates or kernel versions.

Maybe doable, but I have never been bothered by this enough to prioritize it.

[Matoran]

please implement a check if all necessary files are available

There is no consistent rule to define "all necessary files"

So that's rather easier to demand than to accomplish.

We could maybe parse index.html for the "failed" notice, but that isn't consistent either.

It probably needs a table of different parsers or rules for different ranges of dates or kernel versions.

Maybe doable, but I have never been bothered by this enough to prioritize it.

You can check the status file if it's 0 build is ok, otherwise isn't.

[bkw777]

fixed some time ago