From: Mark Loeser <halcy0n@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 14:27:55 -0400 [thread overview]
Message-ID: <20100825182755.GA6815@halcy0n.com> (raw)
In-Reply-To: <201008251342.14948.bangert@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1064 bytes --]
Thilo Bangert <bangert@gentoo.org> said:
> 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’
>
> * Please do not file a Gentoo bug and instead report the above QA
> * issues directly to the upstream developers of this software.
> 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."
Personally I think we should be directing our users to our Bugzilla
always. We really don't want to be pissing off upstreams if we put in a
patch that triggers one of these QA warnings and it ends up being our
problem and not theirs.
--
Mark Loeser
email - halcy0n AT gentoo DOT org
email - mark AT halcy0n DOT com
web - http://www.halcy0n.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2010-08-25 19:06 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
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 [this message]
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=20100825182755.GA6815@halcy0n.com \
--to=halcy0n@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