From: "Mark Hatle" <mark.hatle@kernel.crashing.org>
To: Outback Dingo <outbackdingo@gmail.com>,
Alexander Kanavin <alex.kanavin@gmail.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] file /etc/ethertypes conflicts between netbase-1:6.2-r0.corei7_64 and ebtables-2.0.10+4-r4.corei7_64
Date: Mon, 14 Dec 2020 06:09:39 -0600 [thread overview]
Message-ID: <1801279e-ec5b-b025-aa45-1338ae835f98@kernel.crashing.org> (raw)
In-Reply-To: <CAKYr3zyZ2N=VHuy+qDwHo4QkR7DNweusO3RrBj+A2zziBHKaDw@mail.gmail.com>
The version in netbase is the correct one.
For a comparison, see the followng for the netbase version:
https://salsa.debian.org/md/netbase/-/blob/master/etc/ethertypes
and see the following for the ebtables version:
http://git.netfilter.org/ebtables/tree/ethertypes?h=ebtables-2.0.10-4
So the correct fix for this would be to remove ethertypes from the ebtables
recipe in meta-oe.
Additionally, it looks like there is a MUCH newer version of ebtables. (2.0.10
was released 6 year ago, while 2.0.11 was released about 1 year ago.)
(Even 2.0.11 has an older version of the ethertypes file then what netbase has.)
--Mark
On 12/14/20 4:55 AM, Outback Dingo wrote:
> On Mon, Dec 14, 2020 at 5:39 PM Alexander Kanavin
> <alex.kanavin@gmail.com> wrote:
>>
>> Sorry, but you need to explain why the file from from ebtables (an optional package from a 3rd party layer) takes precedence over file from netbase (which is a core item).
>
> further to the previous note, it conflicts with ebtables in meta-oe
> from what i can tell
>
> commit c71a08cea8477f69ee3bc511f1f14d99e09c0a49
> Author: Paul Eggleton <paul.eggleton@linux.intel.com>
> Date: Mon Dec 3 15:30:40 2012 +0000
>
> ebtables: add from OE-Classic, update and tidy up
>
> * Update to 2.0.10-4
> * Handle hardcoded paths in initscript
> * Add LIC_FILES_CHKSUM
> * Set SUMMARY (which sets DESCRIPTION)
> * Drop PRIORITY
> * Minor formatting/ordering tweaks
>
> Based on a patch by Vladimir Redzhepoff <vladimir.redzhepoff@promwad.com>
>
> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
>
>
>>
>> Alex
>>
>> On Mon, 14 Dec 2020 at 11:33, Outback Dingo <outbackdingo@gmail.com> wrote:
>>>
>>> ---
>>> meta/recipes-core/netbase/netbase_6.2.bb | 1 -
>>> 1 file changed, 1 deletion(-)
>>>
>>> diff --git a/meta/recipes-core/netbase/netbase_6.2.bb b/meta/recipes-core/netbase/netbase_6.2.bb
>>> index a54d2e7764..262b2cf1bc 100644
>>> --- a/meta/recipes-core/netbase/netbase_6.2.bb
>>> +++ b/meta/recipes-core/netbase/netbase_6.2.bb
>>> @@ -19,5 +19,4 @@ do_install () {
>>> install -m 0644 ${S}/etc/rpc ${D}${sysconfdir}/rpc
>>> install -m 0644 ${S}/etc/protocols ${D}${sysconfdir}/protocols
>>> install -m 0644 ${S}/etc/services ${D}${sysconfdir}/services
>>> - install -m 0644 ${S}/etc/ethertypes ${D}${sysconfdir}/ethertypes
>>> }
>>> --
>>> 2.20.1
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
prev parent reply other threads:[~2020-12-14 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 10:32 [PATCH] file /etc/ethertypes conflicts between netbase-1:6.2-r0.corei7_64 and ebtables-2.0.10+4-r4.corei7_64 Outback Dingo
2020-12-14 10:39 ` [OE-core] " Alexander Kanavin
2020-12-14 10:47 ` Mark Hatle
2020-12-14 10:49 ` Outback Dingo
2020-12-14 10:55 ` Outback Dingo
2020-12-14 12:09 ` Mark Hatle [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=1801279e-ec5b-b025-aa45-1338ae835f98@kernel.crashing.org \
--to=mark.hatle@kernel.crashing.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=outbackdingo@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