From b426f852d8d78c70902c1ae972737cf53e7f168d Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Tue, 1 Feb 2011 01:54:01 -0800 Subject: [PATCH] doebuild: always return success for listonly mode This compensates for changed fetch() return value in commit 394cd4a00d37fd078f8dd40f89f8c810355d7816, which serves to trigger the pkg_nofetch phase inside doebuild(). --- pym/portage/package/ebuild/doebuild.py | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/pym/portage/package/ebuild/doebuild.py b/pym/portage/package/ebuild/doebuild.py index 6fc7489aa..bbc3a4a12 100644 --- a/pym/portage/package/ebuild/doebuild.py +++ b/pym/portage/package/ebuild/doebuild.py @@ -737,6 +737,12 @@ def doebuild(myebuild, mydo, myroot, mysettings, debug=0, listonly=0, if not fetch(fetchme, mysettings, listonly=listonly, fetchonly=fetchonly): spawn_nofetch(mydbapi, myebuild, settings=mysettings) + if listonly: + # The convention for listonly mode is to report + # success in any case, even though fetch() may + # return unsuccessfully in order to trigger the + # nofetch phase. + return 0 return 1 if mydo == "fetch": -- 2.26.2