I suppose there could be multiple ways of fixing this bug, and I'm uncertaing regarding what's the best strategy. Calling the usual portage.doebuild() on a binpkg tree causes this: Traceback (most recent call last): File "../libraries/entropy/spm/plugins/interfaces/portage_plugin/__init__.py", line 2124, in _pkg_fooinst self._pkg_setup(package_metadata, skip_if_found = True) File "../libraries/entropy/spm/plugins/interfaces/portage_plugin/__init__.py", line 2102, in _pkg_setup licenses = package_metadata.get('accept_license')) File "../libraries/entropy/spm/plugins/interfaces/portage_plugin/__init__.py", line 1970, in _portage_doebuild debug = etpUi['debug'] File "/usr/lib64/portage/pym/portage/proxy/objectproxy.py", line 31, in __call__ return result(*args, **kwargs) File "/usr/lib64/portage/pym/portage/package/ebuild/doebuild.py", line 696, in doebuild alist = mydbapi.getFetchMap(mycpv, useflags=useflags, AttributeError: 'fakedbapi' object has no attribute 'getFetchMap' You can view the caller function code here: http://gitweb.sabayon.org/?p=entropy.git;a=blob;f=libraries/entropy/spm/plugins/interfaces/portage_plugin/__init__.py;hb=HEAD#l1826 In the meantime, we're reverting to portage 2.1.9.x. Which works just fine (beside pkgsets, preserved-libs functionalities are disabled via portage.const). Reproducible: Always
Workarounding the bug above, generates another problem: !!! Manifest file not found: '/var/tmp/entropy/packages/amd64/5/net-analyzer_metasploit-3.5.0~1.tbz2/xpak/data/Manifest'
This should fix it: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=49f2974e15f7e37dde4cfbcef84abf14e6dd4e4a
This is fixed in 2.2.0_alpha10.
Thanks Zac.
