Summary: | sys-apps/portage-2.2.9 - Error during set creation: Could not import 'smartliverebuild.sets.SmartLiveRebuildSet' for section 'smart-live-rebuild' | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Pavel Volkov <ao> |
Component: | Third-Party Tools | Assignee: | Michał Górny <mgorny> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | darkbasic, dev-portage, egorov_egor, jer, kingjon3377, newchief, xmw |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 530268 | ||
Bug Blocks: |
Description
Pavel Volkov
2014-03-23 06:19:05 UTC
No longer appears with app-portage/smart-live-rebuild-1.3.4 Looks like it's back with portage-2.2.10 and s-l-r-1.3.4 Could you provide 'emerge --info smart-live-rebuild' please? My guess is that the python version you're running portage with is not included in PYTHON_TARGETS for smart-live-rebuild. Original poster here. No problems so far. # eselect python list Available Python interpreters: [1] python2.7 [2] python3.2 [3] python3.3 * [4] python3.4 # emerge -vp app-portage/smart-live-rebuild sys-apps/portage Error during set creation: Could not import 'smartliverebuild.sets.SmartLiveRebuildSet' for section 'smart-live-rebuild' These are the packages that would be merged, in order: [ebuild R ] app-portage/smart-live-rebuild-1.3.3 PYTHON_TARGETS="python2_7 python3_3 (-python3_2)" 0 KiB [ebuild R ~] sys-apps/portage-2.2.14_rc1 USE="(ipc) xattr -build -doc -epydoc -selinux" LINGUAS="-ru" PYTHON_TARGETS="python2_7 python3_3 python3_4 -pypy (-python3_2)" 0 KiB Total: 2 packages (2 reinstalls), Size of downloads: 0 KiB It is fixed in smart-live-rebuild-1.3.4. Perhaps it's time to stabilize that version. First run is with s-m-l-1.3.3 installed. brian@big_daddy ~ $ emerge -1 =app-portage/smart-live-rebuild-1.3.3 =sys-apps/portage-2.2.14_rc1 -vp !!! Repository 'vdr-devel' has sync-type attribute set to unsupported value: 'layman' !!! Repository 'wtk' has sync-type attribute set to unsupported value: 'layman' Error during set creation: Could not import 'smartliverebuild.sets.SmartLiveRebuildSet' for section 'smart-live-rebuild' These are the packages that would be merged, in order: Calculating dependencies /... done! Exiting on signal 2 brian@big_daddy ~ $ eselect python list Available Python interpreters: [1] python2.5 [2] python2.6 [3] python2.7 [4] python3.1 [5] python3.2 [6] python3.3 * [7] python3.4 brian@big_daddy ~ $ emerge -1 =app-portage/smart-live-rebuild-1.3.3 =sys-apps/portage-2.2.14_rc1 -vp !!! Repository 'vdr-devel' has sync-type attribute set to unsupported value: 'layman' !!! Repository 'wtk' has sync-type attribute set to unsupported value: 'layman' These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild UD ] app-portage/smart-live-rebuild-1.3.3 [1.3.4] PYTHON_TARGETS="python2_7 python3_3 (-python3_2) (-python3_4%*)" 0 KiB [ebuild R ] sys-apps/portage-2.2.14_rc1 USE="doc epydoc (ipc) -build (-selinux) -xattr" LINGUAS="-ru" PYTHON_TARGETS="pypy python2_7 python3_3 python3_4 (-python3_2)" 0 KiB Total: 2 packages (1 downgrade, 1 reinstall), Size of downloads: 0 KiB Yes. Happens again after today update of app-portage/smart-live-rebuild-1.3.6 which drops python2_7 target still used by sys-apps/portage. I've unmerged app-portage/smart-live-rebuild and now sys-apps/portage seems to work just fine... First experienced after upgrade to 1.3.7, just now. Determined reason: smart-live-rebuild must support python version, used to run emerge. At least one previous post here already showed it, but not so directly, so I missed it. Runing it with explicit python executable helps to avoid it: $ python3.7 `which emerge` ... |