From 06a976e53c40fe26bf2047c5f0fcf22949d98d77 Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Mon, 17 Jan 2011 10:55:42 -0800 Subject: [PATCH] spawn_nofetch: fix PORTAGE_BUILDIR_LOCKED state We need to correct the state of this variable here, in order to avoid erroneous "ebuild phase 'nofetch' has exited unexpectedly" messages. --- pym/portage/package/ebuild/_spawn_nofetch.py | 2 ++ 1 file changed, 2 insertions(+) diff --git a/pym/portage/package/ebuild/_spawn_nofetch.py b/pym/portage/package/ebuild/_spawn_nofetch.py index 175d88bd1..9ae801050 100644 --- a/pym/portage/package/ebuild/_spawn_nofetch.py +++ b/pym/portage/package/ebuild/_spawn_nofetch.py @@ -54,6 +54,8 @@ def spawn_nofetch(portdb, ebuild_path, settings=None): private_tmpdir = tempfile.mkdtemp(dir=portage_tmpdir) settings['PORTAGE_TMPDIR'] = private_tmpdir settings.backup_changes('PORTAGE_TMPDIR') + # private temp dir was just created, so it's not locked yet + settings.pop('PORTAGE_BUILDIR_LOCKED', None) try: doebuild_environment(ebuild_path, 'nofetch', -- 2.26.2