[gentoo-dev] [PATCH] gnome2.eclass: Add EAPI=7 support

2020-12-06 Thread Matt Turner
Closes: https://bugs.gentoo.org/658638 Closes: https://bugs.gentoo.org/717100 Signed-off-by: Matt Turner --- leio noted that banning GNOME2_LA_PUNT from EAPI 7 would mean adding src_install() { gnome2_src_install } to a bunch of ebuilds, which we don't want to do. Implement GNOME2_LA_PUNT with

[gentoo-portage-dev] [PATCH v4] Use default asyncio event loop implementation in API consumer threads

2020-12-06 Thread Zac Medico
Make the _safe_loop function return an AsyncioEventLoop instance, so that the default asyncio event loop implementation will be used in API consumer threads. This is possible because the underlying asyncio.get_event_loop() function returns a separate event loop for each thread. The

[gentoo-portage-dev] Re: [PATCH v3] Use default asyncio event loop implementation in API consumer threads

2020-12-06 Thread Zac Medico
Accidentally encrypted the last email. Here's an unencrypted version. On 12/6/20 2:14 PM, Zac Medico wrote: > Make the _safe_loop function return an AsyncioEventLoop instance, > so that the default asyncio event loop implementation will be used > in API consumer threads. This is possible because

[gentoo-portage-dev] Re: [PATCH v3] Use default asyncio event loop implementation in API consumer threads

2020-12-06 Thread Zac Medico
On 12/6/20 2:14 PM, Zac Medico wrote: > Make the _safe_loop function return an AsyncioEventLoop instance, > so that the default asyncio event loop implementation will be used > in API consumer threads. This is possible because the underlying > asyncio.get_event_loop() function returns a new event

[gentoo-portage-dev] [PATCH v3] Use default asyncio event loop implementation in API consumer threads

2020-12-06 Thread Zac Medico
Make the _safe_loop function return an AsyncioEventLoop instance, so that the default asyncio event loop implementation will be used in API consumer threads. This is possible because the underlying asyncio.get_event_loop() function returns a new event loop for each thread. The AsyncioEventLoop

[gentoo-portage-dev] [PATCH v2] Use default asyncio event loop implementation in API consumer threads

2020-12-06 Thread Zac Medico
Make the _safe_loop function return an AsyncioEventLoop instance, so that the default asyncio event loop implementation will be used in API consumer threads. This is possible because the underlying asyncio.get_event_loop() function returns a new event loop for each thread. Bug:

[gentoo-dev] [PATCH] gnome2.eclass: Add EAPI=7 support

2020-12-06 Thread Matt Turner
Closes: https://bugs.gentoo.org/717100 Signed-off-by: Matt Turner --- leio noted that the previous patch would potentially change the installed .la files in EAPI 5 and 6 ebuilds. So just continue using ltprune in those EAPIs and ban GNOME2_LA_PUNT in EAPI 7. eclass/gnome2.eclass | 18

[gentoo-dev] [PATCH] gnome2.eclass: Add EAPI=7 support

2020-12-06 Thread Matt Turner
Mostly by porting away from ltprune.eclass. Signed-off-by: Matt Turner --- eclass/gnome2.eclass | 19 +-- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/eclass/gnome2.eclass b/eclass/gnome2.eclass index 341802f8c80..4d8dc6c08d6 100644 --- a/eclass/gnome2.eclass

[gentoo-dev] [PATCH] gnome2-utils.eclass: Drop EAPI < 5 support

2020-12-06 Thread Matt Turner
Closes: https://bugs.gentoo.org/566728 Signed-off-by: Matt Turner --- eclass/gnome2-utils.eclass | 25 +++-- 1 file changed, 7 insertions(+), 18 deletions(-) diff --git a/eclass/gnome2-utils.eclass b/eclass/gnome2-utils.eclass index 06643db0f60..bc1f8f20777 100644 ---

Re: [gentoo-dev] [PATCH] gnome2-utils: Drop EAPI < 5 support

2020-12-06 Thread Ulrich Mueller
> On Sun, 06 Dec 2020, Matt Turner wrote: > -[[ ${EAPI:-0} == [012345] ]] && inherit multilib > +[[ ${EAPI:-0} == [5] ]] && inherit multilib Useless brackets. Also you could drop the :-0 here. > case "${EAPI:-0}" in No quotes needed here. > - 0|1|2|3|4|5|6|7) ;; > - *) die

[gentoo-portage-dev] Re: [PATCH] Use default asyncio event loop implementation in API consumer threads

2020-12-06 Thread Zac Medico
On 12/6/20 1:46 AM, Zac Medico wrote: > Make the _safe_loop function an alias for the global_event_loop > function, so that the default asyncio event loop implementation > will be used in API consumer threads. This is possible because > global_event_loop has been fixed (bug 758740) to always use >

[gentoo-dev] Last-rites: more broken LiveOnlyPackages

2020-12-06 Thread Joonas Niilola
# Not keyworded, unmaintained, unbuildable for a long time, EAPI-5. # Removal in ~30 days. List sorted by their bug numbers. # Bugs: #752432, #752435, #752438, #752441, #752444, #752453. media-plugins/kodi-screensaver-crystalmorph media-plugins/kodi-visualization-nastyfft

[gentoo-portage-dev] [PATCH] Use default asyncio event loop implementation in API consumer threads

2020-12-06 Thread Zac Medico
Make the _safe_loop function an alias for the global_event_loop function, so that the default asyncio event loop implementation will be used in API consumer threads. This is possible because global_event_loop has been fixed (bug 758740) to always use AsyncioEventLoop, and that uses

[gentoo-portage-dev] [PATCH] Use default asyncio event loop implementation in child processes

2020-12-06 Thread Zac Medico
Use the default asyncio event loop implementation in child processes, instead of portage's internal EventLoop. After fork, instantiate a new asyncio.DefaultEventLoopPolicy as a workaround for https://bugs.python.org/issue22087, which is necessary for RetryTestCase to succeed. Bug: