| Summary: | www-client/seamonkey-2.31-r1 - Traceback (most recent call last): in <module> import os // File ".../work/comm-release/seamonk/_virtualenv/lib/python2.7/os.py", line 2 // SyntaxError: Non-ASCII character '\xc3' in file .../work/comm-release/seamonk/... | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Don Wilburn <bodhisattva> |
| Component: | Current packages | Assignee: | Lars Wendler (Polynomial-C) (RETIRED) <polynomial-c> |
| Status: | RESOLVED OBSOLETE | ||
| Severity: | normal | CC: | mozilla |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | Alpha | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge --info for failed seamonkey emerge
smbuild.log.bz2 |
||
Created attachment 392210 [details]
smbuild.log.bz2
Doesn't look like it's specific for Alpha. Is this still an issue with =www-client/seamonkey-2.33.1? (In reply to Lars Wendler (Polynomial-C) from comment #3) > Is this still an issue with =www-client/seamonkey-2.33.1? I tried 2.32, which failed. Now 2.33 fails at "...(configure stage)" before it really gets started. I don't know if it's just mine or any alpha. I have updated @world a couple times since the original bug, but haven't seen the same sort of error with other program builds. seamonkey-2.31 has been removed from the tree quite a while ago. |
Created attachment 392208 [details] emerge --info for failed seamonkey emerge Seamonkey reported failure when I tried to emerge it. It's not marked stable for alpha, of course. The firefox guy got mad when I tried/failed on that one- ha ha. I will send the build log after I attach --info to this.