Summary: | >=sys-apps/portage-2.2_pre8882: portageq fails | ||
---|---|---|---|
Product: | Portage Development | Reporter: | drftcicfn |
Component: | Core - External Interaction | Assignee: | Portage team <dev-portage> |
Status: | VERIFIED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2.2 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
drftcicfn
2007-12-17 12:31:56 UTC
(In reply to comment #0) > portageq doesn't work, cannot emerge some packages: > /usr/lib/portage/bin/portageq:415: SyntaxWarning: name 'portage' is assigned to > before global declaration > def main(): The above is only a warning. I don't receive that warning with python-2.5.1-r4. > *** stack smashing detected ***: python - terminated > python: stack smashing attack in function symtable_node - terminated It seems like something is wrong with python. Maybe to can us a binary package to install a working version python. I have unmasked python-2.5.*, after emerging it, portage is working again. (In reply to comment #2) > I have unmasked python-2.5.*, after emerging it, portage is working again. Thanks for information! It seems that Portage 2.2* requires Python >=2.5, so I will adjust dependencies. (In reply to comment #3) > (In reply to comment #2) > > I have unmasked python-2.5.*, after emerging it, portage is working again. > > Thanks for information! It seems that Portage 2.2* requires Python >=2.5, so I > will adjust dependencies. It shouldn't require 2.5, and I don't see anything in that area of portageq that could trigger such a warning, so I'm pretty sure that this was just some local issue with python. (In reply to comment #4) > It shouldn't require 2.5, and I don't see anything in that area of portageq > that could trigger such a warning, so I'm pretty sure that this was just > some local issue with python. I unpacked 2007.0 stage3 with Python 2.4*, chrooted into it, updated Portage to 2.2* and I'm confirming that warning (without stack smashing), so I think that it is worth to depend on Python >=2.5 to not have that warning. Thanks, I've moved the global statement in svn r9004 and python no longer produces the warning. |