| Summary: | libbonoboui-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 | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
John Altstadt
2004-11-13 09:23:33 UTC
I just tried FEATURES=-userpriv and it didn't help. I will set FEATURES=-maketest next, which is certain to work. Oops. Step 3 above should be "ssh to remote machine", not rsh. As expected, FEATURES=-maketest fixed the problem. yeah as expected.. it silly to use that option to build your system afaic. and search before filing bugs *** This bug has been marked as a duplicate of 69347 *** What an odd attitude. The maketest feature was added to portage to help ensure that stuff got tested. Other develpers are quite happily accepting maketest bugs and either resolving them or passing them upstream. In most cases maketest is finding upstream problems. I did search before posting. I also try to read and understand the bug reports I find before adding to them or creating another. In this case, the bug I described was clearly not the same as bug #69347. If anything it is another instance of bug #71061 using another gnome package. The gnome tests have a problem with connecting to a remote X server. And as per bug #71061 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. it is an upstream issue, as the bug it was duped against said. It is also an issue that gentoo doesn't have time for, as the other bug said(see why it was duped to that bug). The problem with using maketest for packages like these is that lots of the gnome packages contain tests that have not been updated in years(most people don't use them) Maketests are probably more valid/useful in core system packages and servers where anything is considered mission critical(and the packages keep up to date and valid tests). We aren't trying to blow off your bug as invalid, but rather something with very low priority in gentoo. It doesn't effect how the package actually runs, its just an out of date test. There are lots of other bugs filed that do effect the package in a more serious way, and those are where dev time needs to go. If you want to file upstream gnome bugs about the tests failing and try to get more updated tests in, that would be great(always nice to get community help)...but its just something we don't have the time for atm. I'm going to propose something for these maketest "bugs". While we, the GNOME team, are not in any way opposed to fixing bugs in the software we maintain, we do not currently have the time required to catch these "maketest bugs", and patch them. This is compounded by the fact that only a small number of users use FEATURES="maketest". Although we will not have the time to fix these "bugs" ourselves, we will happily test any patch you can supply to us, or any formed solution to the problem. Should you be unable to provide such a patch, then the easiest course of action may be upstream - where they have a better understanding of the software, even than us. While FEATURES="maketest" is available in portage, you must understand it is not uniformly supported across all upstream developers. |
