From: Thilo Bangert <bangert@gentoo.org>
To: gentoo-qa@lists.gentoo.org
Subject: Re: [gentoo-qa] QA confusion: Upstream qa issues -> failing to install
Date: Thu, 26 Aug 2010 00:02:10 +0200 [thread overview]
Message-ID: <201008260002.14965.bangert@gentoo.org> (raw)
In-Reply-To: <20100825182755.GA6815@halcy0n.com>
[-- Attachment #1: Type: Text/Plain, Size: 1352 bytes --]
Mark Loeser <halcy0n@gentoo.org> said:
> 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.
i would agree, that all issues should be reported in our own bugzilla
(also).
It would be really nice if we somehow could annotate the bug, in the
ebuild, so that the warning already includes the bug number (or is
silenced by it) in an effort to reduce the number of duplicates.
where are these qa checks implemented anyway?
thanks
Thilo
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-08-25 22:04 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
2010-08-25 22:02 ` Thilo Bangert [this message]
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=201008260002.14965.bangert@gentoo.org \
--to=bangert@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