From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Steve Sakoman <steve@sakoman.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core][dunfell 1/8] Revert "package: get_package_mapping: avoid dependency mapping if renamed package provides original name"
Date: Sat, 17 Oct 2020 08:55:17 +0100 [thread overview]
Message-ID: <c4b7539b1a57fb2b32bb68345aaaa8b807a7349d.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAOSpxdbZ9yKWyLkALJctu5BCP77AX=PSNWuBffNa8snxMOEgjw@mail.gmail.com>
On Fri, 2020-10-16 at 04:34 -1000, Steve Sakoman wrote:
> I've included this revert patch for comment because I have gotten
> several requests to revert and I'd like wider discussion of the
> issue.
>
> At the moment wireguard is the only known recipe that is failing and
> there are no proposed fixes.
>
> If you are aware of recipes in other layers that are affected, please
> let me know.
>
> And if someone would like to tackle fixing wireguard in
> meta-openembedded that would be much preferred to a revert.
It would also be good to know if the issue exists on master or not. I'm
worried we may have the issue there as well which is a reason I'd
favour looking into and understanding this rather than blindly
reverting. I've not seen anyone have a full understanding of what the
issue is as yet.
Cheers,
Richard
next prev parent reply other threads:[~2020-10-17 7:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 14:15 [OE-core][dunfell 0/8] Patch review Steve Sakoman
2020-10-15 14:15 ` [OE-core][dunfell 1/8] Revert "package: get_package_mapping: avoid dependency mapping if renamed package provides original name" Steve Sakoman
2020-10-15 14:15 ` [OE-core][dunfell 2/8] timezone: update to 2020b Steve Sakoman
2020-10-15 14:15 ` [OE-core][dunfell 3/8] scripts/oe-build-perf-report: Allow operation with no buildstats Steve Sakoman
2020-10-15 14:15 ` [OE-core][dunfell 4/8] oe-build-perf-report: Ensure correct data is shown for multiple branch options Steve Sakoman
2020-10-15 14:15 ` [OE-core][dunfell 5/8] bitbake-bblayers/create: Make the example recipe print its message Steve Sakoman
2020-10-15 14:15 ` [OE-core][dunfell 6/8] uninative: Fix typo in error message Steve Sakoman
2020-10-15 14:15 ` [OE-core][dunfell 7/8] qemu: add 34Kf-64tlb fictitious cpu type Steve Sakoman
2020-10-18 14:27 ` Richard Purdie
2020-10-19 15:48 ` Steve Sakoman
2020-10-15 14:15 ` [OE-core][dunfell 8/8] qemumips: use 34Kf-64tlb CPU emulation Steve Sakoman
[not found] ` <163E30094343B958.12811@lists.openembedded.org>
2020-10-16 14:34 ` [OE-core][dunfell 1/8] Revert "package: get_package_mapping: avoid dependency mapping if renamed package provides original name" Steve Sakoman
2020-10-17 7:55 ` Richard Purdie [this message]
2020-10-22 10:59 ` Martin Jansa
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=c4b7539b1a57fb2b32bb68345aaaa8b807a7349d.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=steve@sakoman.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