Thank you for merging https://bugs.gentoo.org/672522 but I would like to have that for new release as well. Merged version was for in that time latest version 1.8.26 but during time of merge new version 1.8.27 was released and this change was left out as it was based on original package version. Would it be possible to have package with secure-path use flag and have it as base for future release? I am not sure if I should not just edit 1.8.27 ebuild directly but I want to make sure that use flags are updated by portage so I instead created 1.8.27-r1.
It wasn't added to the live ebuild either. Comparing the live ebuild and 1.8.27 with 1.8.26, it looks like the live ebuild is now two USE flags behind on 1.8.26 whereas 1.8.27 is lagging by one USE flag.
commit f946718065a714d430fe7bea0ef0ccf67ea1c9af Author: Karel Kočí <cynerd@email.cz> Date: Sun Feb 10 15:28:09 2019 app-admin/sudo: add secure-path use to 1.8.27 as well secure-path was merged at the same time as 1.8.27 was release but new version was based on original ebuild so new version once again misses this use flag. Bug: https://bugs.gentoo.org/672522 Signed-off-by: Karel Kočí <cynerd@email.cz> Closes: https://github.com/gentoo/gentoo/pull/11022 Signed-off-by: Lars Wendler <polynomial-c@gentoo.org> app-admin/sudo/{sudo-1.8.27.ebuild => sudo-1.8.27-r1.ebuild} | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
