From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] prelink: fix upstream version check
Date: Mon, 16 Oct 2017 13:22:05 +0300 [thread overview]
Message-ID: <c4d752b8-c0c5-bfd7-ca5b-e7958a9f31f3@linux.intel.com> (raw)
In-Reply-To: <077b5862-bb57-8447-4cca-5301740ff945@windriver.com>
On 10/13/2017 05:56 PM, Mark Hatle wrote:
> 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.
The system currently supports only comparing tags, not comparing
commits. I've filed a bug for it long time ago:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=8133
and no progress happened. In the meantime, for projects where commit ==
release, the best we can do is to mark them as 'upstream version cannot
be established'. For prelink, also an exclusion of a bogus tag is
needed, so you, as the maintainer, won't get reminders to update to it.
Alex
next prev parent reply other threads:[~2017-10-16 10:25 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
2017-10-16 10:22 ` Alexander Kanavin [this message]
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=c4d752b8-c0c5-bfd7-ca5b-e7958a9f31f3@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=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