From: veilleux.cedric@gmail.com
To: openembedded-devel@lists.openembedded.org
Subject: Re: wireguard-module broken in dunfell
Date: Tue, 06 Oct 2020 10:19:37 -0700 [thread overview]
Message-ID: <10765.1602004777092046892@lists.openembedded.org> (raw)
In-Reply-To: <CAAfyv35EHVpu64e8pYG9qrMSGCFBZewXD2dZ+c9aM_mJfxidhw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 853 bytes --]
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.
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.
[-- Attachment #2: Type: text/html, Size: 1014 bytes --]
next prev parent reply other threads:[~2020-10-06 17:19 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 [this message]
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
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=10765.1602004777092046892@lists.openembedded.org \
--to=veilleux.cedric@gmail.com \
--cc=openembedded-devel@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