| Summary: | Please stabilise app-misc/gramps-3.1.1 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Christian Faulhammer (RETIRED) <fauli> |
| Component: | New packages | Assignee: | Steve Dibb (RETIRED) <beandog> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | Keywords: | STABLEREQ |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 264323 | ||
|
Description
Christian Faulhammer (RETIRED)
2009-04-17 00:07:19 UTC
amd64 stable x86 stable ping ppc, sparc This presents a problem on sparc. For me, gramps-3.1.1 triggers an immediate bus error if byte-compiled (.py[co]) files are used. If I get rid of them, gramps seems to run, but some operations also trigger a bus error. We can be pretty sure that generally python builds good .py[co] files because portage works. I have no clue what to do with this. Hm. If I get rid of my original ~/.gramps directory it works better, but now segfaults if given the data.gramps file from the examples. I can't tell at this point if it's working or not (it's better than -3.0.4 at least, I think). Grrr. With a reinstall with USE='gnome spell reports' and a refreshed examples directory, now gramps can import data.gramps. I'd appreciate it if some other sparc person could confirm. Right now, gramps seems to be working as it should (it can import files, export files, generate reports, ...), but the process to get there was a bit unusual and it took me several installs (all of which should have been identical). What I *think* happened is this: I suspect gramps does not run well with USE='-gnome'. ppc stable (In reply to comment #6) > Grrr. With a reinstall with USE='gnome spell reports' and a refreshed examples > directory, now gramps can import data.gramps. I'd appreciate it if some other > sparc person could confirm. Right now, gramps seems to be working as it should > (it can import files, export files, generate reports, ...), but the process to > get there was a bit unusual and it took me several installs (all of which > should have been identical). What I *think* happened is this: I suspect > gramps does not run well with USE='-gnome'. The code is normally well capsulated with several try statements and on x86 it runs well without USE=gnome. Anyway, I updated dependencies for 3.1.1-r1 but all of them are USE dependant. Sparc stable (problem seems to have been stale data) and closing. |