for the last little bit i've been looking into packages that fail their test phases with the new maketest feature. some of these are easy fixes, some are gentoo specific, most are upstream, or sloppy and unmaintained, but they're all a pain in the ass. anyways, what i want to focus on here are maketest failures in base system packages. ie. if a user has the maketest feature enabled, and does an 'emerge system', these packages will error and the emerge will fail. combine this with the fact that 'emerge system' is a critical step in even installing Gentoo, and it's a big problem. maketest being off by default lessens the damage, but IMHO these need to be fixed. i've just completed a fresh x86 bootstrap and emerge system, and the following packages are causing trouble and need to be taken care of in one way or another (fix, workaround, or disable the tests entirely). sys-devel/gettext-0.12.1-r2 (bug #70358) looks like it wontfix dev-lang/python-2.3.4 (bug #67970) dev-libs/popt-1.7-r1 (bug #71610) sys-apps/coreutils-5.2.1 (bug #69216) sys-apps/grep-2.5.1-r6 (bug #63507) i have a patch for this one but i don't think anyone's looked at it sys-devel/libtool-1.5.2-r7 (bug #70350) again, none of these are broken packages, just broken tests. is there any way you could remove them somehow, so at least the portage forum could cut down on the 'HELPP emeerge borked!!!!!!!11' posts? =P Reproducible: Always Steps to Reproduce: 1. 2. 3.
See http://forums.gentoo.org/viewtopic.php?t=254145 for one person's view regarding maketest in general. I am surprised that there was only one response on that thread.
broken tests in base-system will be taken seriously we have no policy atm on whether developers should fix maketest or ignore it
thanks, it's a relief to see these are being taken seriously. i've run into everything from 'thanks for fixing' that to 'we don't do %$@#$ maketests'. anyways, as a user, i'll find and fix what i can, and leave the policy decisions to the bigwigs.
coreutils-5.2.1-r3 fixed (bug #69216 removed from depends)
forgot about this guy. removing #63507 (grep), #70350 (libtool), & #70358 (gettext).
Hi, As i'm using 'test' (former 'maketest') as default in my FEATURES-list think of using this as a meta-bug tracker as it's now. Yesterday had my first test-broken package - kde-base/kdelibs-3.3.2-r9 which fails with 'test' but compiles OK w/o. BUG-91522 filed on kdelibs. kdelibs-3.3.2-r9 went to my /etc/portage/package.features file using '-test' till the bug is solved, already have a hint. Thanks Rumen
kdelibs is not a base system package...
Hi again, Sorry for kdelibs-package, just didn't saw this is for base-packages only. Have two more entries here: glibc-2.3.4.20041102-r1 & GCC-3.4.3.20050110-r2 (from ~x86) both fail with 'test' emerge OK otherwise (will see for glibc-2.3.5). Currently using X86-system with some testing-packages. Found such bug for glibc: 90526,89843 dups of 86515 which seems to be resolved. Also found 86384 for gcc-3.4.3.20050110-r1 - marked as NEW. Haven't tried the solutions, maybe will do later. Do i post my logs on this bugs? Thanks. Rumen
no. this bug is for tracking other bugs. generally nothing gets posted here. glibc and gcc will probably always fail, but you can post your logs on the other bugs that you found. thanks for the help.
Looks like all of the bugs this one depended on are now fixed, so....resolving.
