| # 00:43:53 | cpackham | :zagura, :milkylainen I'm not against ct-ng carrying the CVE fix (if someone were to supply a patch, hint, hint) timing is annoying but can't be helped. We did get a GCC CVE in just before the release so we're 1 for 2 which ain't bad |
| # 00:44:53 | cpackham | by the time we get to the next ct-ng release I expect we'll be shipping a glibc version with the fix but these things tend to have a long tail |
| # 00:45:12 | cpackham | plus I know some users are just working from ct-ng master |
| # 02:29:35 | cpackham | quits : Ping timeout: 240 seconds |
| # 02:33:41 | cpackham | joins #crosstool-ng |
| # 02:55:35 | cpackham | quits : Ping timeout: 240 seconds |
| # 03:06:48 | cpackham | joins #crosstool-ng |
| # 03:58:14 | cpackham | quits : Ping timeout: 255 seconds |
| # 04:57:12 | milkylainen | cpackham: I was thinking that when selecting a git versioned source for glibc, ct-ng points to the sourceware repo by default. It could also help by pointing to release/$(GLIBC_VERSION)/master by default. That would automatically give you the stable fixes of your branch if rebuilding? |