From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] prelink: fix upstream version check
Date: Fri, 13 Oct 2017 09:56:21 -0500 [thread overview]
Message-ID: <077b5862-bb57-8447-4cca-5301740ff945@windriver.com> (raw)
In-Reply-To: <20171013141832.24325-1-alexander.kanavin@linux.intel.com>
On 10/13/17 9:18 AM, Alexander Kanavin wrote:
> Instead of reporting that we can update to a bogus version
> report that upstream version is not known.
You do know that there are release branches for prelink right?
http://git.yoctoproject.org/cgit/cgit.cgi/prelink-cross/refs/heads
cross_prelink and master are both 'release' quality branches.
Anything put there is a new version.
There is nothing for us to 'tag', since there are no formal versions.
Should be easy enough for the system to compare the SRCREV to the top of
cross_prelink. If they don't match, an upgrade is needed.
--Mark
> Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
> ---
> meta/recipes-devtools/prelink/prelink_git.bb | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/meta/recipes-devtools/prelink/prelink_git.bb b/meta/recipes-devtools/prelink/prelink_git.bb
> index a137a864921..570ef36a3cc 100644
> --- a/meta/recipes-devtools/prelink/prelink_git.bb
> +++ b/meta/recipes-devtools/prelink/prelink_git.bb
> @@ -32,6 +32,8 @@ SRC_URI = "git://git.yoctoproject.org/prelink-cross.git;branch=cross_prelink \
> file://prelink.cron.daily \
> file://prelink.default \
> file://macros.prelink"
> +UPSTREAM_CHECK_GITTAGREGEX = "upstream has no usable tags"
> +UPSTREAM_VERSION_UNKNOWN = "1"
>
> TARGET_OS_ORIG := "${TARGET_OS}"
> OVERRIDES_append = ":${TARGET_OS_ORIG}"
>
next prev parent reply other threads:[~2017-10-13 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 14:18 [PATCH] prelink: fix upstream version check Alexander Kanavin
2017-10-13 14:56 ` Mark Hatle [this message]
2017-10-16 10:22 ` Alexander Kanavin
2017-10-16 14:48 ` Mark Hatle
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=077b5862-bb57-8447-4cca-5301740ff945@windriver.com \
--to=mark.hatle@windriver.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