[OE-core][PATCH] busybox: search stable versions for AUH

[OE-core][PATCH] busybox: search stable versions for AUH

[Andrej Valek]

Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
---
 meta/recipes-core/busybox/busybox.inc | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc
index 47fcb59302..253168e2b9 100644
--- a/meta/recipes-core/busybox/busybox.inc
+++ b/meta/recipes-core/busybox/busybox.inc
@@ -13,6 +13,9 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=de10de48642ab74318e893a61105afbb \
 
 SECTION = "base"
 
+UPSTREAM_CHECK_URI = "https://busybox.net/"
+UPSTREAM_CHECK_REGEX = "BusyBox\ (?P<pver>\d+\.\d+\.\d+)\ \(stable\)"
+
 # Whether to split the suid apps into a seperate binary
 BUSYBOX_SPLIT_SUID ?= "1"
 
-- 
2.11.0

Re: [OE-core][PATCH] busybox: search stable versions for AUH

[Richard Purdie]

On Mon, 2021-02-22 at 16:49 +0100, Andrej Valek wrote:
> Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
> ---
>  meta/recipes-core/busybox/busybox.inc | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/meta/recipes-core/busybox/busybox.inc b/meta/recipes-core/busybox/busybox.inc
> index 47fcb59302..253168e2b9 100644
> --- a/meta/recipes-core/busybox/busybox.inc
> +++ b/meta/recipes-core/busybox/busybox.inc
> @@ -13,6 +13,9 @@ LIC_FILES_CHKSUM = "file://LICENSE;md5=de10de48642ab74318e893a61105afbb \
>  
> 
> 
> 
>  SECTION = "base"
>  
> 
> 
> 
> +UPSTREAM_CHECK_URI = "https://busybox.net/"
> +UPSTREAM_CHECK_REGEX = "BusyBox\ (?P<pver>\d+\.\d+\.\d+)\ \(stable\)"
> +
>  # Whether to split the suid apps into a seperate binary
>  BUSYBOX_SPLIT_SUID ?= "1"
>  
> 

I just realised/wondered whether:

inherit upstream-version-is-even

would work here?

Cheers,

Richard

Re: [OE-core][PATCH] busybox: search stable versions for AUH

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 428 bytes --]

On Mon, 22 Feb 2021 at 17:02, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> > +UPSTREAM_CHECK_URI = "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.

Alex

[-- Attachment #2: Type: text/html, Size: 876 bytes --]

Re: [OE-core][PATCH] busybox: search stable versions for AUH

[Khem Raj]

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
> 
> 
> 
> 

Re: [OE-core][PATCH] busybox: search stable versions for AUH

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 970 bytes --]

Right here: https://busybox.net/

Alex


On Mon, 22 Feb 2021 at 18:37, Khem Raj <raj.khem@gmail.com> wrote:

>
>
> 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
> >
> >
> > 
> >
>

[-- Attachment #2: Type: text/html, Size: 1947 bytes --]

Re: [OE-core][PATCH] busybox: search stable versions for AUH

[Khem Raj]

On Mon, Feb 22, 2021 at 10:44 AM Alexander Kanavin
<alex.kanavin@gmail.com> wrote:
>
> Right here: https://busybox.net/
>
I see.
Gap between 1.32.0 and 1.32.1 release was about 6 months, I am not
sure if all distros are waiting for dot releases or not. I see that
upcoming fedora 34 ( due in April )
is already packaging busybox 1.33.0

> Alex
>
>
> On Mon, 22 Feb 2021 at 18:37, Khem Raj <raj.khem@gmail.com> wrote:
>>
>>
>>
>> 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
>> >
>> >
>> > 
>> >

Re: [OE-core][PATCH] busybox: search stable versions for AUH

[Alexander Kanavin]

[-- Attachment #1: Type: text/plain, Size: 1823 bytes --]

I am also not sure if there's actual meaning behind this unstable marker.
It's not explained anywhere, there are no release announcements where it's
explicitly mentioned, and the branch in git has no commits since 1.33.0
https://git.busybox.net/busybox/log/?h=1_33_stable

I am leaning towards just taking the .0 versions.

Alex

On Mon, 22 Feb 2021 at 20:14, Khem Raj <raj.khem@gmail.com> wrote:

> On Mon, Feb 22, 2021 at 10:44 AM Alexander Kanavin
> <alex.kanavin@gmail.com> wrote:
> >
> > Right here: https://busybox.net/
> >
> I see.
> Gap between 1.32.0 and 1.32.1 release was about 6 months, I am not
> sure if all distros are waiting for dot releases or not. I see that
> upcoming fedora 34 ( due in April )
> is already packaging busybox 1.33.0
>
> > Alex
> >
> >
> > On Mon, 22 Feb 2021 at 18:37, Khem Raj <raj.khem@gmail.com> wrote:
> >>
> >>
> >>
> >> 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
> >> >
> >> >
> >> > 
> >> >
>

[-- Attachment #2: Type: text/html, Size: 3283 bytes --]

Re: [OE-core][PATCH] busybox: search stable versions for AUH

[Bas Mevissen]

On 2021-02-22 21:00, Alexander Kanavin wrote:

> I am also not sure if there's actual meaning behind this unstable 
> marker. It's not explained anywhere, there are no release announcements 
> where it's explicitly mentioned, and the branch in git has no commits 
> since 1.33.0
> https://git.busybox.net/busybox/log/?h=1_33_stable
> 
> I am leaning towards just taking the .0 versions.
> 

I agree that is fine for master. The project seems to be just very 
conservative in what it calls stable. The delta between unstable and the 
consecutive stable is small. For the branches, they can start with the 
then current version from master and get updated when there are stable 
updates.

So Gatesgarth should go to 1.32.1 and master to 1.33.0 IMHO.

Bas.

> Alex
> 
> On Mon, 22 Feb 2021 at 20:14, Khem Raj <raj.khem@gmail.com> wrote:
> 
>> On Mon, Feb 22, 2021 at 10:44 AM Alexander Kanavin
>> <alex.kanavin@gmail.com> wrote:
>>> 
>>> Right here: https://busybox.net/
>>> 
>> I see.
>> Gap between 1.32.0 and 1.32.1 release was about 6 months, I am not
>> sure if all distros are waiting for dot releases or not. I see that
>> upcoming fedora 34 ( due in April )
>> is already packaging busybox 1.33.0
>> 
>>> Alex
>>> 
>>> 
>>> On Mon, 22 Feb 2021 at 18:37, Khem Raj <raj.khem@gmail.com> wrote:
>>>> 
>>>> 
>>>> 
>>>> 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
>>>>> 
>>>>> 
>>>>> 
>>>>> 
> 
>