Copied from /var/log/entropy/spm.log: [22:05:04 26/01/2011 MST] INFO: Traceback (most recent call last): File "/usr/lib/entropy/libraries/entropy/spm/plugins/interfaces/portage_plugin/__init__.py", line 1985, 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 562, in doebuild use_cache, mydbapi) File "/usr/lib64/portage/pym/portage/package/ebuild/doebuild.py", line 248, in doebuild_environment ["SRC_URI"], mytree=mytree) TypeError: aux_get() got an unexpected keyword argument 'mytree' [22:05:04 26/01/2011 MST] INFO: [PRE] ATTENTION Cannot properly run SPM prerm phase for dev-db/phpmyadmin-3.3.8.1. Something bad happened. Exception <type 'exceptions.Exception'> [aux_get() got an unexpected keyword argument 'mytree'] This happens for every package I install with equo. I recently installed the latest portage with "emerge portage" Reproducible: Always Steps to Reproduce: 1. Install any package with equo (sabayon linux).
It seems as if entropy is passing in a dbapi instance that implements getFetchMap() but doesn't support the mytree parameter for aux_get(). This is inconsistent with the portage api, where portdbapi is the only class that implements getFetchMap(), and it supports the mytree parameter for both getFetchMap() and aux_get(). So, the entropy api needs to be consistent with the portage api in this way.
Given the discussion we had some time ago with Zac, fakedbapi didn't expose getFetchMap(), if I remember correctly. So, a workaround was applied in commit ed4544228fb45d61437fab6f80b84da2f775ecdb on the entropy.git repository (see URL). User seems having an outdated Entropy version installed, despite we write everywhere to keep entropy updated. The bug has been already fixed, if zmedico thinks there's a better way to fix it, just REOPEN.
(In reply to comment #2) > Given the discussion we had some time ago with Zac, fakedbapi didn't expose > getFetchMap(), if I remember correctly. > So, a workaround was applied in commit ed4544228fb45d61437fab6f80b84da2f775ecdb > on the entropy.git repository (see URL). > User seems having an outdated Entropy version installed, despite we write > everywhere to keep entropy updated. > The bug has been already fixed, if zmedico thinks there's a better way to fix > it, just REOPEN. > Well I don't know if the fix has made it out of git and into the released version or not, but I have the latest entropy installed (1.0_alpha9) as of right now. So despite what you write everywhere, keeping entropy updated isn't helping.
