It seems barman's setup.py uses exefile() which was removed from Python 3, but the ebuild does not request setup.py to be executed with some Python 2 version, leading to: # emerge barman Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) dev-db/barman-1.2.0 * barman-1.2.0.tar.gz SHA256 SHA512 WHIRLPOOL size ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking barman-1.2.0.tar.gz to /var/tmp/portage/dev-db/barman-1.2.0/work >>> Source unpacked in /var/tmp/portage/dev-db/barman-1.2.0/work >>> Preparing source in /var/tmp/portage/dev-db/barman-1.2.0/work/barman-1.2.0 ... >>> Source prepared. >>> Configuring source in /var/tmp/portage/dev-db/barman-1.2.0/work/barman-1.2.0 ... >>> Source configured. >>> Compiling source in /var/tmp/portage/dev-db/barman-1.2.0/work/barman-1.2.0 ... python3.3 setup.py build Traceback (most recent call last): File "setup.py", line 46, in <module> execfile('barman/version.py', barman) NameError: name 'execfile' is not defined <snipped /> # eselect python list Available Python interpreters: [1] python2.5 [2] python2.6 [3] python2.7 [4] python3.1 [5] python3.2 [6] python3.3 *
Created attachment 349048 [details] Updated ebuild Added SUPPORT_PYTHON_ABIS, PYTHON_DEPEND and RESTRICT_PYTHON_ABIS as per http://www.gentoo.org/proj/en/Python/developersguide.xml, set supported Python versions as per the packages README file and the System Requirements section on http://docs.pgbarman.org/#before_you_start
+ 24 May 2013; Patrick Lauer <patrick@gentoo.org> +barman-1.2.0-r1.ebuild: + Fix python use #471134 a bit nicer That should do, for now :) Thanks for the bug and patch
