Summary: | dev-python/pymsn-0.3.3 fails to compile | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | synthil <ilideun> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
synthil
2008-10-23 03:12:25 UTC
Hi synthil, I haven't been able to recreate this I'm afraid. A completely empty /var/tmp/portage still allowed pymsn-0.3.3 to install fine. Could you please attach the build.log file from the failed emerge attempt, so that we can see the exact error message, and figure out what's going wrong and why it's failing? Just reopen the bug when you attach the logs, thanks... 5:) (In reply to comment #1) > Hi synthil, I haven't been able to recreate this I'm afraid. A completely > empty /var/tmp/portage still allowed pymsn-0.3.3 to install fine. > > Could you please attach the build.log file from the failed emerge attempt, so > that we can see the exact error message, and figure out what's going wrong and > why it's failing? > > Just reopen the bug when you attach the logs, thanks... 5:) > Hi, It looks like my steps to reproduce it failed, too. However, since this affected me on two different computers, it is safe to say that, while it can be resolved, it could still affect people at certain times. In that case, I'd advise anyone having problems emerging pymsn, to unmerge pygtk, pygobject and pycrandypto, then emerge them again, and then emerge pymsn immediately afterwards. Cheers for reproducing it, though. I don't know whether or not to close it, though? Re-opened, please read response below. Hiya Synthil, since we haven't been able to recreate it, and so we haven't been able to figure out what the problem actually was, it's not ever going to be something we can fix. If we leave the bug open, it'll stay open forever that way. Instead, we'll mark it as WORKSFORME, and if people do a complete search of the bugs they should still find it and your solution, which may help them with their problem. It also will allow any bug-wranglers to link back to it if they come across a similar problem. I hope this is an acceptable resolution. If you ever do manage to recreate the problem, do reopen this (and attach the logs if you can get them) and we'll look into it further... 5:) |