Re: [arch-dev-public] providing grsecurity in [community]
[Including In-reply-to header so as not to break threading] On 22/04/14 10:43 AM, Daniel Micay wrote:
2) A few years back we specifically reduced the number of kernels in our repos to one. Then the LTS kernel appeared. Now this. The problem with adding a non-vanilla kernel to the repos is now for kernel bug reports we have to verify which kernel is running. If it is linux-grsec, we then need to figure out if the issue a generic linux one, or with the other patchset. This is a burden to all our the kernel maintainers and not just the packager and is part of the reason the variety of kernels was reduced. Output from `uname -a` or `dmesg` is a pretty basic requirement for a kernel issue, especially since problems like /boot not being mounted and new upgrades installed to the wrong place often happen. I don't mind being the one who asks for this on any [linux] issues missing it.
I'll have to dig up the old discussion because I wasn't around for it.
It's not just a matter of asking "what kernel are you using". You'll probably have to ask the bug submitter to install linux from [core], wait a day, and start comparing two sets of output. But since you're prepared to do all the work, I don't think there's a reason to drop linux-grsec. That should happen if / when another packager has to work around it.
On 22.04.2014 21:21, Connor Behan wrote:
[Including In-reply-to header so as not to break threading]
Thanks for trying, but thunderbird still has issues here. Either it's because there are 2 In-Reply-To headers or it's because the message id in the one you added isn't surrounded by <>. If adding the brackets doesn't help, try using mailman's archive and clicking the links there (email addr link at the top of each post), that should work just fine.
On 22/04/14 03:21 PM, Connor Behan wrote:
It's not just a matter of asking "what kernel are you using". You'll probably have to ask the bug submitter to install linux from [core], wait a day, and start comparing two sets of output.
Yeah, that's fine. If I'm already looking at them I might as well just be helping with bug triage in general. It's usually as easy as asking a few questions, pointing upstream or finding an existing bugzilla issue to follow upstream progress. The package could include a reminder in the install script to report issues to the [community] issue tracker but I'm not sure it would be any use.
participants (3)
-
Connor Behan
-
Daniel Micay
-
Florian Pritz