I usually report bugs on bugs.gentoo. For kernel bugs I either used the mailing list or grsecurity.net forum before. This time I thought it is relevant upstreams. That's how I was confused where to report. Next time I'll use solely bugs.gentoo, therefore you can forward them the issue if it is non-Gentoo specific. I hope this workflow also OK for PaXTeam.
Regards: Dw. -- dr Tóth Attila, Radiológus, 06-20-825-8057 Attila Toth MD, Radiologist, +36-20-825-8057 2012.Június 4.(H) 20:48 időpontban Anthony G. Basile ezt írta: > On 06/01/2012 10:10 PM, PaX Team wrote: > >> >> PS: can you please stick to one way of reporting issues in the future? >> it's kinda >> pointless to track two disconnected threads of discussion... >> > > Yes, please, use bugs.gentoo.org. Its how we track bugs. Tracking by > email or forum is too scattered. We need to keep a history of issues in > one place. > > Some guidelines: > > 1) search for your current bug by using "hardened-sources" in the search > field, since your issue may have been already reported or fixed. > > 2) if its a new issue, open a bug with summary beginning with > =sys-kernel/hardened-sources-<version>: <short summary>, or some > variation that would get hit by the search criterion of step 1. > > 3) give steps to reproduced (if needed) > > 4) give emerge --info > > 5) give your kernel config file > > I look at it and either I fix it if its easy enough or a gentoo-only > issue, else I bounce it upstream, usually within a day or two. > > > -- > Anthony G. Basile, Ph. D. > Chair of Information Technology > D'Youville College > Buffalo, NY 14201 > (716) 829-8197 >
