public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eli Schwartz <eschwartz93@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] vdr-plugin-2.eclass: make qa warning conditional
Date: Wed, 1 May 2024 11:07:07 -0400	[thread overview]
Message-ID: <4dc6df27-4efa-47b1-8ddd-4bdd08a08b21@gmail.com> (raw)
In-Reply-To: <7e5a29e3-43e4-4af9-b7c5-660501a027a8@gmx.net>


[-- Attachment #1.1.1: Type: text/plain, Size: 1842 bytes --]

On 5/1/24 10:10 AM, Martin Dummer wrote:
> Since Agostino's tinderbox tests now report qa warning, the group
> vdr@gentoo.org has 101 open bugs assigned, most of them caused by qa
> warnings from vdr-plugin-2.eclass.
> 
> Many vdr plugins need small adjustments because API or makefile changes
> in upstream media-video/vdr which can be easily fixed with small changes.
> 
> These warnings are only useful for the vdr plugin maintainers, so I
> propose they should (only) be reported as QA-warnings when the global
> variable
>     VDR_MAINTAINER_MODE="1"
> is set in make.conf
> 
> This patch is also put to github in
> https://github.com/gentoo/gentoo/pull/36504
> 
> The PR is lacking many many "Closes: ...." tags, which I will fill in soon.
> 
> Any comments?


What does "only useful for the vdr plugin maintainers" mean? Why can't
anyone fix them?

There are lots of QA warnings that a package can generate, and lots of
them are "only" relevant to someone editing the upstream source code.
Why should vdr plugins be special?

From a quick glance at the warning messages, my inexpert feeling is that
two of them are a bit "wishy-washy" and could be classified as "a
warning to be picky and do best practices":

- gettext handling
- old Makefile handling

The others seem like worrisome issues that should very much be reported
in tinderboxes and get fixed.

Automatically sed'ing out source code, especially for the one that says
"please recheck", very much looks like the purpose of the qa warning is
that the functionality isn't trusted to be correct, is offered on a
best-effort basis, and needs to be manually reviewed and marked as okay
(by applying as a real patch) in order to squelch the warnings.

In other words, there are "QA issues" and "QA nitpicks".


-- 
Eli Schwartz

[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 18399 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-05-01 15:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-01 14:10 [gentoo-dev] [PATCH] vdr-plugin-2.eclass: make qa warning conditional Martin Dummer
2024-05-01 15:07 ` Eli Schwartz [this message]
2024-05-03  4:39   ` Sam James
2024-05-09 12:08     ` Martin Dummer
2024-05-09 12:13       ` Sam James
2024-05-09 13:02         ` Martin Dummer
2024-05-09 13:08           ` Sam James
2024-05-10 15:42             ` Martin Dummer

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=4dc6df27-4efa-47b1-8ddd-4bdd08a08b21@gmail.com \
    --to=eschwartz93@gmail.com \
    --cc=gentoo-dev@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