All of lore.kernel.org
 help / color / mirror / Atom feed
From: "akuster" <akuster808@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: [dunfell 06/11] wireguard-module: remove PKG assignment
Date: Mon, 15 Feb 2021 17:58:14 -0800	[thread overview]
Message-ID: <38836bb67436336b9e504769c30f8cf84082da6f.1613440394.git.akuster808@gmail.com> (raw)
In-Reply-To: <cover.1613440394.git.akuster808@gmail.com>

From: Martin Jansa <Martin.Jansa@gmail.com>

* it's not clear why it was added in first place and it's causing issues since:
  "package: get_package_mapping: avoid dependency mapping if renamed package provides original name"
  commit in oe-core as discussed in:
  https://lists.openembedded.org/g/openembedded-core/message/143672
  https://github.com/openembedded/meta-openembedded/issues/285

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 304f660f880bdf7dd5c51695875ab0a73aaed8b2)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
(cherry picked from commit f9502868169715ee4945f5d8bef7c845dbb7b9e0)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
 .../wireguard/wireguard-module_1.0.20200401.bb             | 7 -------
 1 file changed, 7 deletions(-)

diff --git a/meta-networking/recipes-kernel/wireguard/wireguard-module_1.0.20200401.bb b/meta-networking/recipes-kernel/wireguard/wireguard-module_1.0.20200401.bb
index 45324c02a1..e8891c4428 100644
--- a/meta-networking/recipes-kernel/wireguard/wireguard-module_1.0.20200401.bb
+++ b/meta-networking/recipes-kernel/wireguard/wireguard-module_1.0.20200401.bb
@@ -22,13 +22,6 @@ MAKE_TARGETS = "module"
 RRECOMMENDS_${PN} = "kernel-module-xt-hashlimit"
 MODULE_NAME = "wireguard"
 
-# Kernel module packages MUST begin with 'kernel-module-', otherwise
-# multilib image generation can fail.
-#
-# The following line is only necessary if the recipe name does not begin
-# with kernel-module-.
-PKG_${PN} = "kernel-module-${MODULE_NAME}"
-
 module_do_install() {
     install -d ${D}${nonarch_base_libdir}/modules/${KERNEL_VERSION}/kernel/${MODULE_NAME}
     install -m 0644 ${MODULE_NAME}.ko \
-- 
2.17.1


  parent reply	other threads:[~2021-02-16  1:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16  1:58 [dunfell 00/11] Patch review Feb 15th akuster
2021-02-16  1:58 ` [dunfell 01/11] openldap: upgrade 2.4.50 -> 2.4.51 akuster
2021-02-16  1:58 ` [dunfell 02/11] openldap: upgrade 2.4.51 -> 2.4.56 akuster
2021-02-16  1:58 ` [dunfell 03/11] openldap: upgrade 2.4.56 -> 2.4.57 akuster
2021-02-16  1:58 ` [dunfell 04/11] libuv: fix CVE-2020-8252 akuster
2021-02-16  1:58 ` [dunfell 05/11] python-urllib3/python3-urllib3: fix CVE-2020-7212 akuster
2021-02-16  1:58 ` akuster [this message]
2021-02-16  1:58 ` [dunfell 07/11] enca: Fix SRC_URI akuster
2021-02-16  1:58 ` [dunfell 08/11] meta-oe/README: add Ubuntu prerequisite information akuster
2021-02-16  1:58 ` [dunfell 09/11] celt051: update SRC_URI akuster
2021-02-16  1:58 ` [dunfell 10/11] dnsmasq: Fix systemd service akuster
2021-02-16  1:58 ` [dunfell 11/11] python-grpcio-tools: Add missing space for append akuster
2021-02-16  9:55 ` [oe] [dunfell 00/11] Patch review Feb 15th Martin Jansa
2021-02-16 15:58   ` akuster
2021-02-19 18:33     ` 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=38836bb67436336b9e504769c30f8cf84082da6f.1613440394.git.akuster808@gmail.com \
    --to=akuster808@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 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.