How about that?
Has there been any decision what to do with pax patches and gradm? We should decide if to keep it around and bump to new eapi or purge from tree.
Please keep the pax patches and gradm around. WilliamH and I will take care of testing and validation that they are working. We have access to the latest patches.
Fair enough, can you add yourself as maintainer to gradm please? I think you guys should talk it though on gentoo-dev mailing list. I remember the mixed opinions about what to do forward with pax patches.
(In reply to Piotr Karbowski from comment #3) > Fair enough, can you add yourself as maintainer to gradm please? I think you > guys should talk it though on gentoo-dev mailing list. I remember the mixed > opinions about what to do forward with pax patches. They're both part of the hardened@ project (and say they handle PaX/grsecurity bits) and last time we discussed it, we just agreed that they'd handle any such bugs, I think. What would be nice is, if possible, going through Bugzilla once a month or every $period and looking for PaX related bugs.
amd64 done
x86 done all arches done
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e3a407a85c2c17018d48b6c7de1e2be7d09a6ffb commit e3a407a85c2c17018d48b6c7de1e2be7d09a6ffb Author: Andreas Sturmlechner <asturm@gentoo.org> AuthorDate: 2022-08-30 18:35:22 +0000 Commit: Andreas Sturmlechner <asturm@gentoo.org> CommitDate: 2022-08-31 05:39:35 +0000 sys-apps/gradm: drop versions, EAPI-6-- Closes: https://bugs.gentoo.org/830874 Signed-off-by: Andreas Sturmlechner <asturm@gentoo.org> sys-apps/gradm/Manifest | 4 --- sys-apps/gradm/gradm-3.1.201603152148.ebuild | 51 ---------------------------- sys-apps/gradm/gradm-3.1.201607172312.ebuild | 51 ---------------------------- sys-apps/gradm/gradm-3.1.201608131257.ebuild | 51 ---------------------------- sys-apps/gradm/gradm-3.1.201708012022.ebuild | 51 ---------------------------- 5 files changed, 208 deletions(-)
