Summary: | libgnomecanvas-2.8.0 ebuild fails when FEATURES=maketest (on remote machine) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | John Altstadt <altstadt> |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | rockoo, Sergiy.Borodych |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
John Altstadt
2004-11-13 08:31:50 UTC
I have just verified that the build works okay with FEATURES=-maketest. I just thought of something else specific to this build. I was running the emerge as root in an xterm with an rsh to a remote machine. I.e. xterm -> su - -> rsh remote -> emerge libgnomecanvas. Perhaps the X authentication failed due to userpriv. Note that everything is set up correctly to launch other X apps from the same xterm/rsh session, as I used it to open an emacs session to change FEATURES for this particular build. Ran into the same problem with bug #71070 and tried FEATURES=-userpriv, but it didn't help. *** This bug has been marked as a duplicate of 69343 *** How is this in any way a duplicate of bug #69343? The referenced bug is a failure in a specific test once the tests were underway. This bug is a problem with making a connection to an X server that works perfectly fine for other applications. This failure happens long before it starts running the test that failed in the other bug. As another data point, I have now verified that the emerge works correctly using the exact same USE and FEATURE flags (including maketest) if it is run on a local machine. Therefore this is most likely an upstream problem with the gnome tests not working across a network. Don't pretend you don't know why this is a dupe, it's dupe because the 'problems' come from the same FEATURE. The other bug has a sufficient explanation why we don't want to take these 'bugs'. *** This bug has been marked as a duplicate of 69343 *** *** Bug 95234 has been marked as a duplicate of this bug. *** |