From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Joachim Wiberg <troglobit@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ssdp-responder; drop systemd unit installation, not needed
Date: Fri, 10 Feb 2023 23:38:57 +0100 [thread overview]
Message-ID: <20230210233857.1d8ba4a5@windsurf> (raw)
In-Reply-To: <20230210184704.3381562-1-troglobit@gmail.com>
On Fri, 10 Feb 2023 19:47:04 +0100
Joachim Wiberg <troglobit@gmail.com> wrote:
> When systemd is enabled the ssdp-responder build system already installs
> the unit file, with the correct name, so we can safely drop this.
>
> This fixes the recurring autobuilder problems that cropped up the last
> week+ or so after fixing the spelling error in 6e0ba6b.
>
> - http://autobuild.buildroot.net/results/f6912d6f79155c5d12811beeb6cb43860e37e7e7
> - http://autobuild.buildroot.net/results/7ee4ed26de7e45b52a9f6f36b839e578d2319247
> - http://autobuild.buildroot.net/results/33d9c10ea58a7cd3b3e2ed75d586007a92ccdaf0
> - http://autobuild.buildroot.net/results/f1238081fc94e3004aebb8e849fdd567a92a2d39
> - http://autobuild.buildroot.net/results/f7f2cf790f51e6224dca258c52bd31d21d621074
>
> Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
> ---
> package/ssdp-responder/ssdp-responder.mk | 5 -----
> 1 file changed, 5 deletions(-)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-02-10 22:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-10 18:47 [Buildroot] [PATCH 1/1] package/ssdp-responder; drop systemd unit installation, not needed Joachim Wiberg
2023-02-10 22:38 ` Thomas Petazzoni via buildroot [this message]
2023-02-28 20:34 ` Peter Korsgaard
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=20230210233857.1d8ba4a5@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.