From: "Steve Sakoman" <sakoman@gmail.com>
To: Marek Belisko <marek.belisko@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>, akuster <akuster808@gmail.com>,
veilleux.cedric@gmail.com,
openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [oe] wireguard-module broken in dunfell
Date: Fri, 9 Oct 2020 09:14:30 -1000 [thread overview]
Message-ID: <CAGDS+nmT-nLT1Kj713ihDAGtwU2361OHmaD7+Hhoii0PReKgQg@mail.gmail.com> (raw)
In-Reply-To: <CAAfyv34i61gF_LsojeLDaasie67h=fyVyC3-TCAbzGxnDNQ8Lg@mail.gmail.com>
On Fri, Oct 9, 2020 at 8:22 AM Marek Belisko <marek.belisko@gmail.com> wrote:
>
> On Tue, Oct 6, 2020 at 9:21 PM Khem Raj <raj.khem@gmail.com> wrote:
> >
> > On Tue, Oct 6, 2020 at 12:04 PM Belisko Marek <marek.belisko@gmail.com> wrote:
> > >
> > > On Tue, Oct 6, 2020 at 8:25 PM Khem Raj <raj.khem@gmail.com> wrote:
> > > >
> > > > On Tue, Oct 6, 2020 at 11:20 AM akuster <akuster808@gmail.com> wrote:
> > > > >
> > > > >
> > > > >
> > > > > On 10/6/20 10:19 AM, veilleux.cedric@gmail.com wrote:
> > > > > > I had the same issue and could not figure out what broke the
> > > > > > wireguard-module package.
> > > > > >
> > > > > > I had to resort to bissecting changes in meta-yocto.
> > > > > >
> > > > > > I finally isolated the change that breaks wireguard-module:
> > > > > >
> > > > > > 87c9d29635 package: get_package_mapping: avoid dependency mapping if
> > > > > > renamed package provides original name
> > > > > >
> > > > > > http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=87c9d296357638082f5a7131a87365285fc813c4
> > > > > >
> > > > > > It seems the package renaming that wireguard-module does (PKG_${PN} =
> > > > > > "kernel-module-${MODULE_NAME}") no longer works after the above commit.
> > > > >
> > > > > I have not seen this on any of my dunfell world builds.
> > > >
> > > > it only happens with master.
> > > hmm nope. I have it on dunfell also.
> >
> > Oh right, it got backported it dunfell recently hmm
> Can we please revert backport so we have working wireguard again? Thanks.
I'll revert this in oe-core dunfell.
To be sure I see requests like this in the future it would be best to
copy the oe-core list and/or myself.
Thanks for reporting the issue!
Steve
> > > > > Do you mind providing a reproducer e.g local.conf ?
> > > > >
> > > > > -armin
> > > > > >
> > > > > > At this point I do not understand the change regarding renamed package
> > > > > > names and dependencies enough to recommend the appropriate fix to
> > > > > > wireguard-module. I have been able to workaround the issue by renaming
> > > > > > the package kernel-module-wireguard and thus avoiding the rename
> > > > > > altogether.
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > as simple and primitive as possible
> > > -------------------------------------------------
> > > Marek Belisko - OPEN-NANDRA
> > > Freelance Developer
> > >
> > > Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> > > Tel: +421 915 052 184
> > > skype: marekwhite
> > > twitter: #opennandra
> > > web: http://open-nandra.com
>
>
>
> --
> as simple and primitive as possible
> -------------------------------------------------
> Marek Belisko - OPEN-NANDRA
> Freelance Developer
>
> Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
> Tel: +421 915 052 184
> skype: marekwhite
> twitter: #opennandra
> web: http://open-nandra.com
>
>
>
next prev parent reply other threads:[~2020-10-09 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 6:33 wireguard-module broken in dunfell Marek Belisko
2020-10-06 17:19 ` veilleux.cedric
2020-10-06 17:56 ` [oe] " Khem Raj
2020-10-06 18:20 ` akuster
2020-10-06 18:22 ` Khem Raj
2020-10-06 19:04 ` Marek Belisko
2020-10-06 19:20 ` Khem Raj
2020-10-09 18:19 ` Marek Belisko
2020-10-09 19:14 ` Steve Sakoman [this message]
2020-10-09 19:40 ` veilleux.cedric
2020-10-13 6:06 ` c.finck
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=CAGDS+nmT-nLT1Kj713ihDAGtwU2361OHmaD7+Hhoii0PReKgQg@mail.gmail.com \
--to=sakoman@gmail.com \
--cc=akuster808@gmail.com \
--cc=marek.belisko@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=veilleux.cedric@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.