| ohsix | anyone know offhand which script or part of the build process adds Supported: <time> to the resulting control package control file | 01:17 |
|---|---|---|
| ohsix | http://bazaar.launchpad.net/~ubuntu-core-dev/update-manager/main/view/head:/ubuntu-support-status#L122 the ones used for this | 01:24 |
| === nelhage_ is now known as nelhage | ||
| === Trevinho_ is now known as Trevinho | ||
| === Guest19932 is now known as sts | ||
| === ghostcube_ is now known as ghostcube | ||
| === JanC is now known as Guest52941 | ||
| === JanC_ is now known as JanC | ||
| asd213 | Hi guys. Are kernels from this url: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D valid for Ubuntu 16.04 too? The latest ones end in -wil | 13:06 |
| asd213 | y | 13:06 |
| apw | asd213, that -wily tells you which release the configs come from IIRC ...which for the higher version numbers is suspect | 13:08 |
| apw | asd213, that said none of those kernels are valid for anything other than non-production testing | 13:08 |
| asd213 | apw. So what does a ubuntu user do when the default kernel is buggy, and an older one works just fine? | 13:10 |
| apw | asd213, well one would hope that those kernels are not the solution ... we use those when users file a bug to try and find the solution | 13:11 |
| asd213 | oh | 13:11 |
| asd213 | ok | 13:11 |
| apw | asd213, in general we would ask you to file a bug, and let us know the bug number. If you have tested mainline kernels (such as those) and found which ones work and which not then that inforamtion would be sensibly added to the bug report | 13:12 |
| === _ruben_ is now known as _ruben | ||
| === shadeslayer_ is now known as shadeslayer | ||
| === unixpro1970 is now known as _unixpro1970 | ||
| === tsimonq2alt is now known as tsimonq2 | ||
| === Guest78380 is now known as adrian | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!