From: "Khem Raj" <raj.khem@gmail.com>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Andrej Valek <andrej.valek@siemens.com>,
OE-core <openembedded-core@lists.openembedded.org>,
Oleksandr Kravchuk <open.source@oleksandr-kravchuk.com>
Subject: Re: [OE-core][PATCH] busybox: search stable versions for AUH
Date: Mon, 22 Feb 2021 09:37:13 -0800 [thread overview]
Message-ID: <9ea4df35-c70e-e03e-7fea-e56960ef17c6@gmail.com> (raw)
In-Reply-To: <CANNYZj_1RL9rSJxaaRTQf__mnzEr49Eze5gW44TBtJn7FEhN0Q@mail.gmail.com>
On 2/22/21 8:39 AM, Alexander Kanavin wrote:
> On Mon, 22 Feb 2021 at 17:02, Richard Purdie
> <richard.purdie@linuxfoundation.org
> <mailto:richard.purdie@linuxfoundation.org>> wrote:
>
> > +UPSTREAM_CHECK_URI = "https://busybox.net/ <https://busybox.net/>"
> > +UPSTREAM_CHECK_REGEX = "BusyBox\ (?P<pver>\d+\.\d+\.\d+)\
> \(stable\)"
> I just realised/wondered whether:
>
> inherit upstream-version-is-even
>
> would work here?
>
>
> I don't think so - busybox seems to declare x.y.0 as unstable, and
> everything else as stable.
>
is it documented somewhere that x.y.0 is unstable ?
https://git.busybox.net/busybox/commit/?id=a4c3a341394a1fb25be8c15d2ddfe3ec77cbb83c
seems to indicate its a normal release.
> Alex
>
>
>
>
next prev parent reply other threads:[~2021-02-22 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 15:49 [OE-core][PATCH] busybox: search stable versions for AUH Andrej Valek
2021-02-22 16:02 ` Richard Purdie
2021-02-22 16:39 ` Alexander Kanavin
2021-02-22 17:37 ` Khem Raj [this message]
2021-02-22 18:44 ` Alexander Kanavin
2021-02-22 19:13 ` Khem Raj
2021-02-22 20:00 ` Alexander Kanavin
2021-02-23 9:56 ` Bas Mevissen
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=9ea4df35-c70e-e03e-7fea-e56960ef17c6@gmail.com \
--to=raj.khem@gmail.com \
--cc=alex.kanavin@gmail.com \
--cc=andrej.valek@siemens.com \
--cc=open.source@oleksandr-kravchuk.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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