Summary: | portage.exception.InvalidAtom: !build | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Anders Rune Jensen <anders> |
Component: | Unclassified | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | Keywords: | InVCS |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 210077 | ||
Attachments: | handle the InvalidAtom exception |
Description
Anders Rune Jensen
2008-10-01 19:59:19 UTC
Created attachment 166943 [details, diff]
handle the InvalidAtom exception
If this patch is saved as /tmp/invalid_atom.patch, then it can be applied as follows:
patch /usr/lib/portage/pym/_emerge/__init__.py /tmp/invalid_atom.patch
Thanks. It now doesn't crash, but a emerge -upD world gives: !!! Invalid or corrupt dependency specification: Invalid Atom: !build ('installed', '/', 'sys-devel/gcc-3.4.2-r2', 'nomerge') virtual/libc >=sys-devel/gcc-config-1.3.1 >=sys-libs/zlib-1.1.4 !sys-devel/hardened-gcc !uclibc? ( >=sys-libs/glibc-2.3.3_pre20040420-r1 hardened? ( >=sys-libs/glibc-2.3.3_pre20040529 ) ) amd64? ( multilib? ( >=app-emulation/emul-linux-x86-glibc-1.1 ) ) !build? ( gcj? ( gtk? ( >=x11-libs/gtk+-2.2 ) >=media-libs/libart_lgpl-2.1 ) >=sys-libs/ncurses-5.2-r2 nls? ( sys-devel/gettext ) ) >=sys-apps/texinfo-4.2-r4 >=sys-devel/bison-1.875 >=sys-devel/binutils-2.14.90.0.8-r1 amd64? ( >=sys-devel/binutils-2.15.90.0.1.1-r1 ) !bootstrap? ( sys-devel/patch ) !bootstrap? ( sys-devel/patch ) !bootstrap? ( sys-devel/patch ) sys-devel/gnuconfig !bootstrap? ( sys-devel/patch ) virtual/libc >=sys-devel/gcc-config-1.3.1 >=sys-libs/zlib-1.1.4 !sys-devel/hardened-gcc !uclibc? ( >=sys-libs/glibc-2.3.3_pre20040420-r1 hardened? ( >=sys-libs/glibc-2.3.3_pre20040529 ) ) amd64? ( multilib? ( >=app-emulation/emul-linux-x86-glibc-1.1 ) ) !build? ( gcj? ( gtk? ( >=x11-libs/gtk+-2.2 ) >=media-libs/libart_lgpl-2.1 ) >=sys-libs/ncurses-5.2-r2 nls? ( sys-devel/gettext ) ) sys-devel/gcc-config !nocxx? ( !n32? ( !n64? ( !uclibc? ( !build ( sys-libs/libstdc++-v3 ) ) ) ) ) Portage is unable to process the dependencies of the 'sys-devel/gcc-3.4.2-r2' package. In order to correct this problem, the package should be uninstalled, reinstalled, or upgraded. As a temporary workaround, the --nodeps option can be used to ignore all dependencies. For reference, the problematic dependencies can be found in the *DEPEND files located in '/var/db/pkg/sys-devel/gcc-3.4.2-r2/'. Thought you might find that interesting. Somewhere in /var/db/pkg/sys-devel/gcc-3.4.2-r2/*DEPEND you've got "!build" which is supposed to be "!build?". These commands should correct it: sed 's:!build :!build? :g' -i /var/db/pkg/sys-devel/gcc-3.4.2-r2/*DEPEND touch /var/db/pkg/sys-devel/gcc-3.4.2-r2 rm /var/cache/edb/vdb_blockers.pickle This is fixed in 2.2_rc12. |