public inbox for gentoo-qa@lists.gentoo.org
 help / color / mirror / Atom feed
From: Markos Chandras <hwoarang@gentoo.org>
To: gentoo-qa@lists.gentoo.org
Subject: Re: [gentoo-qa] QA confusion: Upstream qa issues -> failing to install
Date: Wed, 25 Aug 2010 17:20:24 +0300	[thread overview]
Message-ID: <20100825142023.GA11809@Mystical> (raw)
In-Reply-To: <201008251342.14948.bangert@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2788 bytes --]

On Wed, Aug 25, 2010 at 01:42:12PM +0200, Thilo Bangert wrote:
> Hi guys,
> 
> trying to install openssh on the dev profile one is greated with this 
> bugger:
> 
>  * QA Notice: Package has poor programming practices which may compile
>  *            fine but exhibit random runtime failures.
>  * closefromtest.c:46: warning: implicit declaration of function 
> ‘closefrom’
>
This is a rather common bug for 64bit arches

See relevant patches [1][2]

>  * Please do not file a Gentoo bug and instead report the above QA
>  * issues directly to the upstream developers of this software.
>  * Homepage: http://www.openssh.org/
>  * ERROR: net-misc/openssh-5.5_p1-r2 failed:
>  *   install aborted due to poor programming practices shown above
>  * 
>  * Call stack:
>  *   misc-functions.sh, line 847:  Called install_qa_check
>  *   misc-functions.sh, line 539:  Called die
>  * The specific snippet of code:
>  *                              hasq stricter ${FEATURES} && die "install 
> aborted due to" \
>  * 
>  * If you need support, post the output of 'emerge --info =net-
> misc/openssh-5.5_p1-r2',
>  * the complete build log and the output of 'emerge -pqv =net-
> misc/openssh-5.5_p1-r2'.
>  * The complete build log is located at '/var/tmp/portage/net-
> misc/openssh-5.5_p1-r2/temp/build.log'.
>  * The ebuild environment file is located at '/var/tmp/portage/net-
> misc/openssh-5.5_p1-r2/temp/environment'.
>  * S: '/var/tmp/portage/net-misc/openssh-5.5_p1-r2/work/openssh-5.5p1'
> 
> This looks really really weird. On the one hand we are saying: "Its a QA 
> issue but upstream should fix it." followed by "It so broke, we wont let 
> you install it."
This is not only related to stricter but also related to CFLAGS ( having -ggdb
and -Wall, produce same failures for me even if I don't use stricter )

Diego, any ideas why this happens? -Wall & -ggdb produce extra output on
warning that makes portage abort because of that? I always wondered why this
is happening.
> 
> Perhaps qa warnings that fail when FEATURES="stricter", should not point 
> to upstream for the fix. Instead we should take responsibility for these 
> and consequently allow these bugs to linger in our bugzilla.
> 
> What do you tink?
> kind regards
> Thilo

[1]:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/net-analyzer/nagios-plugins/files/nagios-plugins-1.4.14-implicit-pointer-conversion.patch?view=log
[2]:
http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/app-editors/xemacs/files/xemacs-21.4.22-implicit-pointer-conversion.patch?view=log

-- 
Markos Chandras (hwoarang)
Gentoo Linux Developer
Web: http://hwoarang.silverarrow.org
Key ID: 441AC410
Key FP: AAD0 8591 E3CD 445D 6411 3477 F7F7 1E8E 441A C410

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-08-25 15:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-25 11:42 [gentoo-qa] QA confusion: Upstream qa issues -> failing to install Thilo Bangert
2010-08-25 14:20 ` Markos Chandras [this message]
2010-08-25 15:55   ` Diego Elio Pettenò
2010-08-25 18:59     ` Mike Frysinger
2010-08-25 21:57       ` Thilo Bangert
2010-08-25 19:20     ` Markos Chandras
2010-08-25 21:51       ` Diego Elio Pettenò
2010-08-25 22:33         ` Markos Chandras
2010-08-25 18:27 ` Mark Loeser
2010-08-25 22:02   ` Thilo Bangert
2010-09-03 15:17     ` Mark Loeser

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100825142023.GA11809@Mystical \
    --to=hwoarang@gentoo.org \
    --cc=gentoo-qa@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox