Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marcus Hoffmann via buildroot <buildroot@buildroot.org>
To: Fiona Klute <fiona.klute@gmx.de>,
	buildroot@buildroot.org, Andreas Ziegler <br025@umbiko.net>,
	Joachim Wiberg <troglobit@gmail.com>
Cc: "Michał Łyszczek" <michal.lyszczek@bofc.pl>
Subject: Re: [Buildroot] [PATCH 0/4] fix shellcheck 0.10 & 0.11 warnings
Date: Wed, 17 Jun 2026 14:28:02 +0200	[thread overview]
Message-ID: <61a708aa-e992-4b77-9d50-adff450cb378@bubu1.eu> (raw)
In-Reply-To: <20260606182032.3803327-1-fiona.klute@gmx.de>

Hi Fiona, Andreas, Joachim

On 6/6/26 20:20, Fiona Klute via buildroot wrote:
> Hi everyone,
> 
> this series fixes shellcheck warnings that appear with shellcheck 0.10
> (as present in Debian Trixie) and 0.11 (Sid) to prepare for updating
> the CI container image to Trixie. With the current image "make
> check-package" still passes with the patches applied, so they can be
> applied at any point before updating the container image.
> 
> Most changes are pretty trivial (the mdnsd init script a little less),
> but only OpenRC has runtime tests, so tests from people actually using
> the packages would be appreciated.

It would indeed be nice if we had more runtime tests, so we can make 
such changes more comfortably. Thanks Andreas for testing the mpd 
changes. Do you think you could submit a runtime test for it at some 
point? :)

Joachim, you submitted and are mentioned in the DEVELOPERS file for 
mdns, do you think you can submit a runtime test for it?

https://nightly.buildroot.org/manual.html#_using_the_runtime_tests_framework

> 
> Best regards,
> Fiona
> 
Series applied to master, thanks!

Marcus
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      parent reply	other threads:[~2026-06-17 12:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-06 18:20 [Buildroot] [PATCH 0/4] fix shellcheck 0.10 & 0.11 warnings Fiona Klute via buildroot
2026-06-06 18:20 ` [Buildroot] [PATCH 1/4] package/mpd/S95mpd: avoid unnecessary exit Fiona Klute via buildroot
2026-06-06 18:20 ` [Buildroot] [PATCH 2/4] package/mpd/S95mpd: do not wait for exit if sending stop failed Fiona Klute via buildroot
2026-06-06 18:20 ` [Buildroot] [PATCH 3/4] package/mdnsd/S50mdnsd: rewrite to match current guidelines Fiona Klute via buildroot
2026-06-06 18:20 ` [Buildroot] [PATCH 4/4] package/openrc/sysv-rcs: fix shellcheck 0.10 warnings Fiona Klute via buildroot
2026-06-07  6:26 ` [Buildroot] [PATCH 0/4] fix shellcheck 0.10 & 0.11 warnings Andreas Ziegler
2026-06-17 12:28 ` Marcus Hoffmann via buildroot [this message]

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=61a708aa-e992-4b77-9d50-adff450cb378@bubu1.eu \
    --to=buildroot@buildroot.org \
    --cc=br025@umbiko.net \
    --cc=buildroot@bubu1.eu \
    --cc=fiona.klute@gmx.de \
    --cc=michal.lyszczek@bofc.pl \
    --cc=troglobit@gmail.com \
    /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