From: "Zhang, Xiao" <xiao.zhang@windriver.com>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [oe-core][PATCH] iptables: Use update alternatives for "ebtables"
Date: Fri, 3 Apr 2026 14:21:59 +0800 [thread overview]
Message-ID: <12ffee1a-0ce2-4e8d-9cd0-64fbeeba37bc@windriver.com> (raw)
In-Reply-To: <DHIUPHZ23X2B.3QKIWJ5KM2Y92@bootlin.com>
On 4/3/2026 1:39 AM, Mathieu Dubois-Briand wrote:
> On Thu Apr 2, 2026 at 3:49 PM CEST, ZhangXiao via lists.openembedded.org wrote:
>> The ebtables utility can be provided by both ebtables and iptables
>> packages. Set higher priority for the version provided by iptables
>> to prefer it.
>>
>> Signed-off-by: Zhang Xiao <xiao.zhang@windriver.com>
>> ---
> Hi Zhang,
>
> Thanks for your patch.
>
> We can see this warning on the autobuilder:
>
> WARNING: iptables-1.8.13-r0 do_package: iptables: alternative target (/usr/sbin/ebtables or /usr/sbin/ebtables.iptables) does not exist, skipping...
> ...
> WARNING: iptables-1.8.13-r0 do_package: iptables: NOT adding alternative provide /usr/sbin/ebtables: /usr/sbin/ebtables.iptables does not exist
> WARNING: iptables-1.8.13-r0 do_package: iptables: alt_link == alt_target: /usr/sbin/ebtables == /usr/sbin/ebtables
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/11/builds/3484
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/50/builds/3548
>
> Can you have a look at the issue?
Patch V2 sent, thank you for your kindly remind!
Thanks
Xiao
> Thanks,
> Mathieu
>
prev parent reply other threads:[~2026-04-03 6:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 13:49 [oe-core][PATCH] iptables: Use update alternatives for "ebtables" Zhang Xiao
2026-04-02 17:39 ` Mathieu Dubois-Briand
2026-04-03 0:50 ` Zhang, Xiao
2026-04-03 6:21 ` Zhang, Xiao [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=12ffee1a-0ce2-4e8d-9cd0-64fbeeba37bc@windriver.com \
--to=xiao.zhang@windriver.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.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