Created attachment 306533 [details] emerge --info Conclusion of merge process with failure: Build purple plugin PURPLE_CFLAGS : -I/usr/include/libpurple -I/usr/include/glib-2.0 -I/usr/lib64/glib-2.0/include PURPLE_LIBS : -lpurple -lglib-2.0 Voice and video: disabled Not building telepathy plugin Not building with Kerberos 5 support Debugging not enabled Compiler checks disabled configure complete. Now run 'make' >>> Source configured. --------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE "/var/log/sandbox/sandbox-8362.log" VERSION 1.0 FORMAT: F - Function called FORMAT: S - Access Status FORMAT: P - Path as passed to function FORMAT: A - Absolute Path (not canonical) FORMAT: R - Canonical Path FORMAT: C - Command Line F: mkdir S: deny P: /root/.purple A: /root/.purple R: /root/.purple C: ./conftest --------------------------------------------------------------------------------
Created attachment 306535 [details] build log
Created attachment 306537 [details] Emerge environment
Annoyingly I cannot replicate on my machines... I will have to spend some time looking into this one.
To get past this error run: # mkdir -p /root/.purple/mbpurple Somewhere it checks for this directory and runs mkdir if it does not exist.
(In reply to comment #4) > To get past this error run: > # mkdir -p /root/.purple/mbpurple > > Somewhere it checks for this directory and runs mkdir if it does not exist. On the one hand - not difficult to do. On the other - should I, really? Is there no way to fix the ebuild properly? Not saying I can see how, though, yet at least.
Those directories dont exist on my system and it still builds without issue for me. If I could reproduce it would make this a lot easier. I suspect its a compile test that uses libpurple which then tries to create its prefs dir, so I may have to just strip them out.
So, I created an empty /root/.purple/mbpurple directory and tried again; the emerge completed without error. I used 'emerge -d' for a failed attempt and the successful attempt, but it did not reveal anything useful. Perhaps there would have been a better approach. I deleted the directory, un-emerged and emerged again. Again, the sandbox access violation. So, at least I can consistently cause the emerge to fail. What would be the best approach to determine the root cause?
I've just commited x11-plugins/pidgin-sipe-1.13.2 to the tree which should hopefully fix this issue. Please give it a try Thanks
1.13.2 is found by pidgin 2.10.4 (I see it opening the library in strace) but isn't to be found in the protocols list. My Lync account doesn't connect, and when I edit it I don't see Office Communicator as an option. I dropped back to 1.13.1 and my Lync connection came back.
(In reply to comment #9) Please open a new bug for that issue attaching your emerge --info, pidgin logs and anything you deem helpful. Thanks!
Fixed in Tree.
