Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Andre McCurdy <armccurdy@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [morty][PATCH 1/3] upstream-version-is-even.bbclass: ensure that the full version is matched.
Date: Tue, 15 May 2018 13:37:23 -0700	[thread overview]
Message-ID: <1526416645-4896-2-git-send-email-armccurdy@gmail.com> (raw)
In-Reply-To: <1526416645-4896-1-git-send-email-armccurdy@gmail.com>

From: Alexander Kanavin <alexander.kanavin@linux.intel.com>

Previously 4.3.2.1 would match as 3.2.1.

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
(cherry picked from commit b066910f64ba964a8a0bb452925591eed1e16940)
Signed-off-by: Andre McCurdy <armccurdy@gmail.com>
---
 meta/classes/upstream-version-is-even.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/upstream-version-is-even.bbclass b/meta/classes/upstream-version-is-even.bbclass
index 89556ed..99714cb 100644
--- a/meta/classes/upstream-version-is-even.bbclass
+++ b/meta/classes/upstream-version-is-even.bbclass
@@ -2,4 +2,4 @@
 # accepts even minor versions (i.e. 3.0.x, 3.2.x, 3.4.x, etc.)
 # This scheme is used by Gnome and a number of other projects
 # to signify stable releases vs development releases.
-UPSTREAM_CHECK_REGEX = "(?P<pver>\d+\.(\d*[02468])+(\.\d+)+)"
+UPSTREAM_CHECK_REGEX = "[^\d\.](?P<pver>\d+\.(\d*[02468])+(\.\d+)+)"
-- 
1.9.1



  reply	other threads:[~2018-05-15 20:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 20:37 [morty][PATCH 0/3] morty backports Andre McCurdy
2018-05-15 20:37 ` Andre McCurdy [this message]
2018-05-15 20:37 ` [morty][PATCH 2/3] upstream-version-is-even.bbclass: exclude various alphas, betas, pre-releases etc Andre McCurdy
2018-05-15 20:37 ` [morty][PATCH 3/3] nativesdk-packagegroup-sdk-host.bb: add cmake Andre McCurdy

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=1526416645-4896-2-git-send-email-armccurdy@gmail.com \
    --to=armccurdy@gmail.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