| *** mavrick61 has joined #crux-devel | 02:53 | |
| *** Romster has joined #crux-devel | 07:31 | |
| *** Lukc` has joined #crux-devel | 09:32 | |
| *** Romster has quit IRC | 15:21 | |
| *** Romster has joined #crux-devel | 15:22 | |
| *** Amnesia has joined #crux-devel | 19:38 | |
| jaeger | frinnst: have you seen a 3.12 patch for the ptrace thing yet? | 19:44 |
|---|---|---|
| jaeger | It was CVE-2014-4699, right? | 19:48 |
| frinnst | I looked for a patch late last night, didnt find any | 19:52 |
| frinnst | yes CVE-2014-4699 | 19:52 |
| jaeger | hrmm, ok | 19:54 |
| jaeger | regarding jue's concern about shipping a newer kernel than that used by the glibc headers, was that technical or aesthetic? I don't think I've ever seen an issue caused by using a newer kernel than your system headers | 19:55 |
| jaeger | All I can find from searching online is that if you run a glibc with older headers than the running kernel binary "new features might not work as expected" | 19:58 |
| jaeger | no specifics or examples | 19:58 |
| jaeger | with all that said, distros aren't repackaging glibc for every kernel upgrade | 19:59 |
| jaeger | So to me, shipping a 3.14.x kernel instead is a viable option. | 19:59 |
| jaeger | Opinions? | 19:59 |
| jaeger | 08:11 < jue> Romster: I mean more the cosmetic side | 20:02 |
| jaeger | found that which answers my question about aesthetic vs. technical | 20:02 |
| teK__ | +1 for the kernel pi | 20:15 |
| jaeger | heh | 20:16 |
| jaeger | I assumed that 3.12.25 would be along soon and fix the issue but it's not yet | 20:17 |
| frinnst | yeah I dont think anybody's suggested older glibc headers will cause problems with newer kernels. its the other way around | 20:27 |
| frinnst | and I dont object to 3.14 on the ISO | 20:27 |
| frinnst | its probably a good thing with better hardware support | 20:27 |
| jaeger | I think if 3.12.25 doesn't come along today I'll rebuild the ISO with no package changes but with the newer kernel. If we test that and find no issues, any objections from you guys to releasing that as 3.1? | 20:28 |
| frinnst | no please go ahead :) | 20:28 |
| frinnst | Is there anything that remains? iirc all the docs are up to date? | 20:29 |
| jaeger | I think we've got it all (except maybe adding compat-32 to the section of the handbook that talks about contrib?) but would appreciate any double-checking. | 20:30 |
| jaeger | we talked about it back on july 4th in the logs | 20:31 |
| frinnst | yes i remember, just doublechecking :) | 20:32 |
| jaeger | I'm busy with some database pruning at work at the moment but I'll add compat-32 to section 5.2.5 in a bit | 20:34 |
| jaeger | actually I'll add a separate section with slightly different wording for compat-32 to be clear | 20:59 |
| jaeger | ok, that's added | 21:11 |
| nrxtx | frinnst fix should be upstream, you could fetch the commit? | 21:16 |
| nrxtx | https://security-tracker.debian.org/tracker/CVE-2014-4699 see the commit url at the end of the page | 21:20 |
| jaeger | I might try applying it to 3.12.24, then | 21:53 |
| nrxtx | altough its a cleaner way to provide 3.12.25 with the iso | 22:09 |
| nrxtx | 3.15.5 already includes the fix | 22:12 |
| nrxtx | 3.14.12 also | 22:14 |
| nrxtx | 3.10.48 also, why are they behind with 3.12 branch? Oo | 22:15 |
| nrxtx | who has choosen 3.12 for crux? :D | 22:15 |
| jaeger | I chose it because things like vmware tools, zfs, etc. are slow to update but it's still LTS | 22:16 |
| jaeger | 3.12 is maintained by someone else upstream | 22:16 |
| nrxtx | i hope i get all that bumblebee stuff working with newer kernels | 22:17 |
| nrxtx | did not try 3.12 yet | 22:17 |
| teK__ | hey jaeger ;) | 22:48 |
| teK__ | ERROR contrib/xorg-font-terminu header not found: Maintainer | 22:48 |
| jaeger | oops | 23:31 |
Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!