Re: [gentoo-dev] 'pax_kernel' USE flag
On 2021-06-23 08:43, Matt Turner wrote: On Tue, Jun 22, 2021 at 3:19 PM Thomas Deutschmann wrote: The PaX community in Gentoo is still big and active. Many Gentoo users received free access to upstream sources or became paying customers. It's just not available for everyone for free/without registration anymore. But it is still a thing in Gentoo. Can you substantiate that claim? I am probably not the right person to answer that, given that I was never active in Gentoo's hardened/PaX project but let me try: When I got in touch with that stuff (via Debian) and was looking for help, I always run into a community full of helpful Gentoo users. The project itself always had a very good connection with the Gentoo project. Before they stopped providing unrestricted access, the Gentoo PaX/hardened community was around ~30 *active* people with additional ~40-60 changing people hanging around which I believe is a lot for such a niche. That's why upstream also mentioned Gentoo in https://grsecurity.net/passing_the_baton.php. Regarding numbers: I am not sure what you are expecting. All I can tell you is that people who were active, interested and probably known to upstream had the chance to get free access for their personal use (there was even an offer for Gentoo infrastructure...). I don't know how many are still using Gentoo. There was a pax-kernel USE flag on Mesa and I don't recall anyone saying a word when I removed it. As you probably know, I am not a Linux desktop user (yet). My complete experience with that PaX stuff is limited to servers. If there are paying customers that have PaX kernels, perhaps they'd be interested in providing some support for Gentoo if we're being asked to retain support for something we cannot test. Yeah, would be nice to hear something from Gentoo hardened project at all (I am looking at you, mschiff, zorry or blueness ;)). I think slashbeast could also provide more information. I still remember when I reworked firefox/thunderbird ebuild and broke PaX marking there (https://bugs.gentoo.org/756679). So yes, we have at least some users ;-) -- Regards, Thomas Deutschmann / Gentoo Linux Developer fpr: C4DD 695F A713 8F24 2AA1 5638 5849 7EE5 1D5D 74A5 OpenPGP_signature Description: OpenPGP digital signature
Re: [gentoo-dev] 'pax_kernel' USE flag
On Tue, Jun 22, 2021 at 11:43 PM Matt Turner wrote: > > On Tue, Jun 22, 2021 at 3:19 PM Thomas Deutschmann wrote: > > The PaX community in Gentoo is still big and active. > > > > Many Gentoo users received free access to upstream sources or became > > paying customers. > > > > It's just not available for everyone for free/without registration > > anymore. But it is still a thing in Gentoo. > > Can you substantiate that claim? > > There was a pax-kernel USE flag on Mesa and I don't recall anyone > saying a word when I removed it. > > If there are paying customers that have PaX kernels, perhaps they'd be > interested in providing some support for Gentoo if we're being asked > to retain support for something we cannot test. I'd still like an answer to any of this.
Re: [gentoo-dev] [PATCH] lua*.eclass: standardize the guard variables
> On 6 Jul 2021, at 22:59, William Hubbs wrote: > > Change the _R0 suffix on these variable names to _ECLASS. > Signed-off-by: William Hubbs Seems good, thanks William! > [snip] best, sam signature.asc Description: Message signed with OpenPGP
[gentoo-dev] [PATCH] lua*.eclass: standardize the guard variables
Change the _R0 suffix on these variable names to _ECLASS.
Signed-off-by: William Hubbs
---
eclass/lua-single.eclass | 8
eclass/lua-utils.eclass | 8
eclass/lua.eclass| 8
3 files changed, 12 insertions(+), 12 deletions(-)
diff --git a/eclass/lua-single.eclass b/eclass/lua-single.eclass
index ab4fdb3c75a..8b3692b2f18 100644
--- a/eclass/lua-single.eclass
+++ b/eclass/lua-single.eclass
@@ -68,9 +68,9 @@ case ${EAPI} in
*) die "${ECLASS}: EAPI ${EAPI:-0} not supported" ;;
esac
-if [[ ! ${_LUA_SINGLE_R0} ]]; then
+if [[ ! ${_LUA_SINGLE_ECLASS} ]]; then
-if [[ ${_LUA_R0} ]]; then
+if [[ ${_LUA_ECLASS} ]]; then
die 'lua-single.eclass cannot be used with lua.eclass.'
fi
@@ -275,7 +275,7 @@ _lua_single_set_globals() {
_lua_single_set_globals
unset -f _lua_single_set_globals
-if [[ ! ${_LUA_SINGLE_R0} ]]; then
+if [[ ! ${_LUA_SINGLE_ECLASS} ]]; then
# @FUNCTION: _lua_gen_usedep
# @USAGE: [...]
@@ -531,5 +531,5 @@ lua-single_pkg_setup() {
[[ ${MERGE_TYPE} != binary ]] && lua_setup
}
-_LUA_SINGLE_R0=1
+_LUA_SINGLE_ECLASS=1
fi
diff --git a/eclass/lua-utils.eclass b/eclass/lua-utils.eclass
index 278bbca58a3..52ba290e544 100644
--- a/eclass/lua-utils.eclass
+++ b/eclass/lua-utils.eclass
@@ -23,7 +23,7 @@ case ${EAPI} in
*) die "${ECLASS}: EAPI ${EAPI:-0} not supported" ;;
esac
-if [[ ! ${_LUA_UTILS_R0} ]]; then
+if [[ ! ${_LUA_UTILS_ECLASS} ]]; then
inherit toolchain-funcs
@@ -376,7 +376,7 @@ lua_enable_tests() {
busted)
test_directory="${2:-spec}"
test_pkg="dev-lua/busted"
- if [[ ! ${_LUA_SINGLE_R0} ]]; then
+ if [[ ! ${_LUA_SINGLE_ECLASS} ]]; then
eval "lua_src_test() {
busted --lua=\"\${ELUA}\"
--output=\"plainTerminal\" \"${test_directory}\" || die \"Tests fail with
\${ELUA}\"
}"
@@ -395,7 +395,7 @@ lua_enable_tests() {
local test_deps=${RDEPEND}
if [[ -n ${test_pkg} ]]; then
- if [[ ! ${_LUA_SINGLE_R0} ]]; then
+ if [[ ! ${_LUA_SINGLE_ECLASS} ]]; then
test_deps+=" ${test_pkg}[${LUA_USEDEP}]"
else
test_deps+=" $(lua_gen_cond_dep "
@@ -528,5 +528,5 @@ lua_get_version() {
echo "${LUA_VERSION}"
}
-_LUA_UTILS_R0=1
+_LUA_UTILS_ECLASS=1
fi
diff --git a/eclass/lua.eclass b/eclass/lua.eclass
index e9a5c117560..d6fe7201779 100644
--- a/eclass/lua.eclass
+++ b/eclass/lua.eclass
@@ -56,9 +56,9 @@ case ${EAPI} in
*) die "${ECLASS}: EAPI ${EAPI:-0} not supported" ;;
esac
-if [[ ! ${_LUA_R0} ]]; then
+if [[ ! ${_LUA_ECLASS} ]]; then
-if [[ ${_LUA_SINGLE_R0} ]]; then
+if [[ ${_LUA_SINGLE_ECLASS} ]]; then
die 'lua.eclass cannot be used with lua-single.eclass.'
fi
@@ -196,7 +196,7 @@ fi
# lua_targets_lua5-1(-)?,lua_targets_lua5-2(-)?
# @CODE
-if [[ ! ${_LUA_R0} ]]; then
+if [[ ! ${_LUA_ECLASS} ]]; then
# @FUNCTION: _lua_validate_useflags
# @INTERNAL
@@ -313,7 +313,7 @@ lua_foreach_impl() {
multibuild_foreach_variant _lua_multibuild_wrapper "${@}"
}
-_LUA_R0=1
+_LUA_ECLASS=1
fi
# @FUNCTION: _lua_set_globals
--
2.31.1
[gentoo-dev] Re: [gentoo-dev-announce] Last rites: dev-python/contextlib2, dev-python/linecache2, dev-python/traceback2, dev-python/unittest2
On Tue, 2021-07-06 at 00:27 +0200, Michał Górny wrote: > # Michał Górny (2021-07-06) > # Various Python 2-specific backports. All the reverse dependencies > # (except for deps between these packages) have been eliminated. > # Removal on 2021-08-05. Bug #800698. > dev-python/contextlib2 > dev-python/linecache2 > dev-python/traceback2 > dev-python/unittest2 > + dev-python/pathlib2 -- Best regards, Michał Górny
[gentoo-dev] Last rites: dev-ruby/nagios, dev-ruby/notify, dev-ruby/rash
# Hans de Graaff (2021-07-06) # Last release in 2013, no tests, no dependencies. # Masked for removal in 30 days. dev-ruby/nagios # Hans de Graaff (2021-07-06) # Last release in 2013, no tests, no dependencies. # Masked for removal in 30 days. dev-ruby/notify # Hans de Graaff (2021-07-06) # Last release in 2013, all dependencies have switched to rash_alt. # Masked for removal in 30 days. dev-ruby/rash signature.asc Description: This is a digitally signed message part
