I had to force ebuild of redland-bindings to get the python package. It seems to work perfectly. On my way, I discovered that equery files XXX returns nothing if XXX is installed but masked (truly confusing). Reproducible: Always Steps to Reproduce: 1. 2. 3. Expected Results: redland-bindings should be (like redland) in ~ppc, so that the remaining bindinngs are tested by other people.
Created attachment 39394 [details] redland-bindings-0.9.18.1.log.gz It failed to compile on my ppc box, that is why I never keyworded it. Build log attached.
OK, I found it. The problem is that the configure script of redland (not redland-bindings) checks for raptor-config and rascal-config, and does not build those parts if already present. This means that the *second* time redland is built it breaks itself in nasty ways, which prevent redland-binding from running. I just emerge -C both and then rebuilt with no problems (subject to more testing, but it looks like this is the problem we're seeing) The problem (for what I see, should affect all platforms) What I don't know is the standard way to solve this kind of problems in gentoo (self-destructing packages :-)
Reassigning to ebuild maintainer.
0.9.19 fixes this
