OpenSSH fails to install when using FEATURES="stricter". As you can see, I am using a "stable"/"not-~x86"-system. How did this get into "stable"? (And should QA-bugs be reported at all?) I am thinking about taking "stricter" out of my features (since this is already the second package after mailx which failed today)... but I like the idea of having some extra "line of quality-checking" on a 24/7-online-computer ;-) What would you suggest? Reproducible: Always Steps to Reproduce: 1. FEATURES="stricter" emerge -u openssh Actual Results: [...] >>> Completed installing openssh-4.5_p1-r1 into /var/tmp/portage/net-misc/openssh-4.5_p1-r1/image/ ecompressdir: bzip2 -f9 /usr/share/man/man1 ecompressdir: bzip2 -f9 /usr/share/man/man5 ecompressdir: bzip2 -f9 /usr/share/man/man8 strip: i686-pc-linux-gnu-strip --strip-unneeded usr/sbin/sshd usr/lib/misc/ssh-keysign usr/lib/misc/sftp-server usr/bin/scp usr/bin/ssh-keygen usr/bin/ssh usr/bin/ssh-add usr/bin/ssh-agent usr/bin/ssh-keyscan usr/bin/sftp * QA Notice: Package has poor programming practices which may compile * fine but exhibit random runtime failures. * dns.c:266: warning: implicit declaration of function `uuencode' !!! ERROR: net-misc/openssh-4.5_p1-r1 failed. Call stack: misc-functions.sh, line 570: Called install_qa_check misc-functions.sh, line 325: Called die !!! poor code kills airplanes !!! If you need support, post the topmost build error, and the call stack if relevant. !!! A complete build log is located at '/var/log/portage/net-misc:openssh-4.5_p1-r1:20070404-215159.log'. !!! install_qa_check failed; exiting. tatooine ~ # emerge --info Portage 2.1.2.2 (hardened/x86/2.6, gcc-3.4.6, glibc-2.3.6-r5, 2.6.18-hardened i686) ================================================================= System uname: 2.6.18-hardened i686 AMD Duron(tm) processor Gentoo Base System release 1.12.9 Timestamp of tree: Wed, 04 Apr 2007 03:30:09 +0000 dev-lang/python: 2.4.3-r4 dev-python/pycrypto: 2.0.1-r5 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.60 sys-devel/automake: 1.9.6-r2, 1.10 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.14 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.17-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -pipe -march=i686 -fomit-frame-pointer -ftracer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/terminfo" CXXFLAGS="-O2 -pipe -march=i686 -fomit-frame-pointer -ftracer" DISTDIR="/usr/portage/distfiles" FEATURES="distlocks metadata-transfer parallel-fetch sandbox sfperms strict stricter" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/linux/distributions/gentoo" LANG="en_US.utf8" LC_ALL="en_US.utf8" LINGUAS="en" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude=/distfiles --exclude=/local --exclude=/packages --filter=H_**/files/digest-*" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="acl berkdb caps crypt hardened ncurses nptl pam pic readline skey ssl unicode x86 xinetd zlib" ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route share shm softvol" ELIBC="glibc" INPUT_DEVICES="mouse keyboard" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="en" USERLAND="GNU" Unset: CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS
Try w/ 4.6_p1-r1; and yeah, FEATURES=stricter is not intended for users.
I added ~x86 for openssh and tried net-misc/openssh-4.6_p1-r1. But nothing changed. After taking "stricter" out of my FEATURES installing of OpenSSH, mailx and gamin worked. Is "stricter" just a FEATURE for future use and is currently ignored by the package maintainers? Or did something go wrong and some "bad" packages slipped through the QA-process? Thanks :)
