[gentoo-portage-dev] [PATCH 4/6] EbuildBuild: use async_lock (bug 614112)

Asynchronously lock the build directory, and use AsyncTaskFuture to fit the resulting future into the CompositeTask framework that EbuildBuild uses. Bug: https://bugs.gentoo.org/614112 --- pym/_emerge/EbuildBuild.py | 7 ++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git

[gentoo-portage-dev] [PATCH 3/6] Binpkg: use async_lock (bug 614112)

Asynchronously lock the build directory, and use AsyncTaskFuture to fit the resulting future into the CompositeTask framework that Binpkg uses. Bug: https://bugs.gentoo.org/614112 --- pym/_emerge/Binpkg.py | 16 +--- 1 file changed, 13 insertions(+), 3 deletions(-) diff --git

[gentoo-portage-dev] [PATCH 2/6] AbstractEbuildProcess: use async_lock (bug 614112)

Asynchronously lock the build directory. The asynchronous lock delays creation of the pid, and it's possible for the _wait method to be called before the pid is available. Therefore, AbstractEbuildProcess._wait() must wait for the pid to become available before it can call the SpawnProcess._wait()

[gentoo-portage-dev] [PATCH 1/6] EbuildBuildDir: add async_lock method (bug 614112)

Asynchronoulsy handle locking of both the category directory and build directory. Bug: https://bugs.gentoo.org/614112 --- pym/_emerge/EbuildBuildDir.py | 76 +++ 1 file changed, 76 insertions(+) diff --git a/pym/_emerge/EbuildBuildDir.py

[gentoo-portage-dev] [PATCH 0/6] EbuildBuildDir: add async_lock method (bug 614112)

Asynchronoulsy handle locking of both the category directory and build directory. Bug: https://bugs.gentoo.org/614112 Zac Medico (6): EbuildBuildDir: add async_lock method (bug 614112) AbstractEbuildProcess: use async_lock (bug 614112) Binpkg: use async_lock (bug 614112) EbuildBuild: use

[gentoo-portage-dev] [PATCH 6/6] EbuildBuildDir: remove synchronous lock method (bug 614112)

The synchronous lock method can trigger event loop recursion if the event loop is already running, which is incompatible with asyncio's default event loop. Therefore, migrate the last consumers to use the async_lock method, and remove the synchronous lock method. Bug:

[gentoo-portage-dev] [PATCH 5/6] PackageUninstall: use async_lock (bug 614112)

Asynchronously lock the build directory, and use AsyncTaskFuture to fit the resulting future into the CompositeTask framework that PackageUninstall uses. Bug: https://bugs.gentoo.org/614112 --- pym/_emerge/PackageUninstall.py | 8 +++- 1 file changed, 7 insertions(+), 1 deletion(-) diff

[gentoo-dev] Last rites: kde-misc/ktexteditorpreviewplugin

# Andreas Sturmlechner (21 Apr 2018) # Package moved into kde-apps/kate as a feature. Masked for removal. kde-misc/ktexteditorpreviewplugin

Re: [gentoo-portage-dev] [PATCH] BinpkgFetcher: use async lock (bug 614110)

On Sat, 21 Apr 2018 12:27:28 -0700 Zac Medico wrote: > In order to avoid event loop recursion, convert the > _BinpkgFetcherProcess.lock() method to an async_lock > method for use by BinpkgFetcher. > > Bug: https://bugs.gentoo.org/614110 > --- > pym/_emerge/BinpkgFetcher.py

[gentoo-portage-dev] [PATCH] BinpkgFetcher: use async lock (bug 614110)

In order to avoid event loop recursion, convert the _BinpkgFetcherProcess.lock() method to an async_lock method for use by BinpkgFetcher. Bug: https://bugs.gentoo.org/614110 --- pym/_emerge/BinpkgFetcher.py | 53 +++- 1 file changed, 33 insertions(+), 20