Summary: | =app-portage/gentoolkit-0.3.0.9-r2: equery list exception when trying to use @set as pkgspec | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sergey S. Starikoff <Ikonta> |
Component: | Current packages | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | beelzebubbie.logs, esigra |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=550862 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 346443 |
Description
Sergey S. Starikoff
2015-04-16 07:32:58 UTC
Actually, equery list is supposed to support sets, so this is an actual bug in the set handling. I'm currently tracking what the bug actually is. This is now fixed in git. You can test with gentoolkit-9999 Working set support is actually quite cool, for example: $ equery list @live-rebuild * Searching for @live-rebuild ... [IP-] [ ] app-portage/epm-9999:0 [IP-] [ ] app-portage/esearch-9999:0 [IP-] [ ] app-portage/gentoolkit-9999:0 [IP-] [ ] app-portage/gentoolkit-dev-9999:0 [IP-] [ ] app-portage/layman-9999:0 $ equery list @unavailable * Searching for @unavailable ... [I--] [??] sys-kernel/gentoo-sources-3.10.7:3.10.7 [I--] [??] sys-kernel/gentoo-sources-3.10.63:3.10.63 Just ran into this, when it's going to be released? (Sorry for stupid question. Maybe if you linked the git commit ID, I'd have figured it out myself.) (In reply to Juraj Variny from comment #3) > Just ran into this, when it's going to be released? It is released in gentoolkit-0.3.1 However, revdep-rebuild changes to a new python version in that version so depending on why you are using ACCEPT_KEYWORDS="amd64", you may or may not want to keyword that package. |