| vorlon | tjaalton: why is icl-backport.diff only in the bionic mesa upload, not in the disco one? what happens to users who upgrade from bionic to disco? | 04:33 |
|---|---|---|
| -queuebot:#ubuntu-release- Unapproved: accepted mesa [source] (bionic-proposed) [19.0.8-0ubuntu0~18.04.1] | 04:48 | |
| tjaalton | vorlon: disco kernel doesn't support icl | 05:07 |
| tjaalton | so I thought it wouldn't matter there | 05:08 |
| vorlon | tjaalton: well, a) why not, isn't it expected that the kernels in the later non-LTS releases include the same features as the LTS kernels? (I see linux-oem-osp1 is present in bionic and disco at roughly the same versions) | 05:09 |
| vorlon | and b), what does happen to a user of one of these machines when they upgrade to disco? | 05:09 |
| tjaalton | vorlon: well, true, if a user is on osp1 kernel on bionic it should still have it after upgrade.. | 05:10 |
| tjaalton | but what happens is that things won't suddenly break. in fact we've had the stock disco mesa while enabling icl and I haven't heard any complaints yet | 05:15 |
| tjaalton | the patches do fix some issues like the dri driver complaining that icl is still 'premature' if an app is launched from the terminal, for instance | 05:16 |
| vorlon | ok | 05:16 |
| ginggs | would someone please 'force-badtest python-sparse/0.2.0-1/i386' ? - it has regressed in release | 13:50 |
| ginggs | also please 'force-badtest satpy/0.16.1-1' | 14:37 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!