On Sat, 5 Aug 2006 11:49:53 +0200 Danny van Dyk <[EMAIL PROTECTED]> wrote:
> Please re-read the list of packages that fail tests: > * glibc > * autoconf > * gettext > * tar > That makes _4_ system packages. Before I would consider making > FEATURES=test a default, I would add least want the system set to > actually merge with it. So you're happy to let users install these packages without them knowing the tests would fail? I certainly agree they should pass their tests. autoconf-2.60, gettext-0.15 and tar-1.15.1-r1, which are the latest versions I have installed here, all pass on my system. If they fail on your platform, then you should make sure bugs are open and the relevant maintainers are doing something about it, and IMO they should not go to arch (i.e. should remain ~arch) until the test issues are resolved. Thing is, at the moment you have a bunch of packages installed that fail their tests. This may mean the tests are broken, however it may also mean the packages are not working correctly on your system, and I'd be concerned if I were you. Avoiding the test phase doesn't make the packages work, obviously. glibc is somewhat of a special case; it is especially sensitive to the environment - many of the tests assume a vanilla RedHat environment, and often the test failures in glibc are not actual problems with glibc but limitations of the test suite. However we should not be encouraging people to install glibc versions where the test failures are not understood. Clearly if something in glibc is not behaving properly, the effects can be nasty. -- Kevin F. Quinn
signature.asc
Description: PGP signature
