From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 2/6] cdrtools-native: fix upstream version check
Date: Wed, 22 Nov 2017 18:32:29 +0200 [thread overview]
Message-ID: <20171122163233.10292-2-alexander.kanavin@linux.intel.com> (raw)
In-Reply-To: <20171122163233.10292-1-alexander.kanavin@linux.intel.com>
Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
---
meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb | 1 +
1 file changed, 1 insertion(+)
diff --git a/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb b/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb
index 0e0be627108..78e1565e474 100644
--- a/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb
+++ b/meta/recipes-devtools/cdrtools/cdrtools-native_3.01.bb
@@ -8,6 +8,7 @@ LICENSE = "GPLv2 & CDDL-1.0 & LGPLv2.1+"
LIC_FILES_CHKSUM = "file://COPYING;md5=32f68170be424c2cd64804337726b312"
SRC_URI = "${SOURCEFORGE_MIRROR}/project/cdrtools/cdrtools-${REALPV}.tar.bz2"
+UPSTREAM_VERSION_UNKNOWN = "1"
SRC_URI[md5sum] = "7d45c5b7e1f78d85d1583b361aee6e8b"
SRC_URI[sha256sum] = "ed282eb6276c4154ce6a0b5dee0bdb81940d0cbbfc7d03f769c4735ef5f5860f"
--
2.15.0
next prev parent reply other threads:[~2017-11-22 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 16:32 [PATCH 1/6] meta-selftest: fix upstream version checks for devtool test recipes Alexander Kanavin
2017-11-22 16:32 ` Alexander Kanavin [this message]
2017-11-22 16:32 ` [PATCH 3/6] m4-native: fix upstream version check Alexander Kanavin
2017-11-22 16:32 ` [PATCH 4/6] opkg-utils: " Alexander Kanavin
2017-11-22 16:32 ` [PATCH 5/6] kern-tools-native: " Alexander Kanavin
2017-11-22 16:32 ` [PATCH 6/6] neon: remove the recipe Alexander Kanavin
2017-11-23 11:28 ` Maxin B. John
2017-11-23 13:46 ` Alexander Kanavin
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=20171122163233.10292-2-alexander.kanavin@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@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