diff mbox series

[walnascar,2.12,2/2] bitbake: Bump version to 2.12.1

Message ID a7d07075ed20f11a9bc068b495d739cab71b07c6.1757519577.git.steve@sakoman.com
State New
Headers show
Series [walnascar,2.12,1/2] Use a "fork" multiprocessing context | expand

Commit Message

Steve Sakoman Sept. 10, 2025, 3:55 p.m. UTC 
From: Martin Jansa <martin.jansa@gmail.com>

To indicate compatibility with python 3.14

[YOCTO #15858]

Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
Signed-off-by: Steve Sakoman <steve@sakoman.com>
---
 bin/bitbake        | 2 +-
 lib/bb/__init__.py | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

Comments

Martin Jansa Sept. 17, 2025, 7:27 a.m. UTC | #1 
Hello Steve,

I've noticed today that 1.12.3 tag was pushed for current 1.12 branch:

commit 710f98844ae30416bdf6a01b655df398b49574ec (tag: yocto-5.2.3,
tag: 2025-04.3-walnascar, tag: 2.12.3, origin/2.12, oe/2.12,
github/2.12, github.oe/2.12, 2.12)
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date:   Tue Jul 29 16:42:25 2025 -0400

    utils: Optimise signal/sigmask performance

Should I redo this as 2.12.4 and adjust the related change for oe-core
to bump the minimal version to 2.12.4 as well?

Similarly for scarthgap and 2.8 bitbake, which has 2.8.12 tag already,
so instead of 2.8.1 I would bump it to 2.8.13.

commit 982645110a19ebb94d519926a4e14c8a2a205cfd (tag: yocto-5.0.12,
tag: 2024-04.12-scarthgap, tag: 2.8.12, origin/2.8, oe/2.8,
github/2.8, github.oe/2.8, 2.8)
Author: Richard Purdie <richard.purdie@linuxfoundation.org>
Date:   Tue Jul 29 14:43:09 2025 -0400

    utils: Optimise signal/sigmask performance

Regards,

On Wed, Sep 10, 2025 at 5:55 PM Steve Sakoman via
lists.openembedded.org <steve=sakoman.com@lists.openembedded.org>
wrote:
>
> From: Martin Jansa <martin.jansa@gmail.com>
>
> To indicate compatibility with python 3.14
>
> [YOCTO #15858]
>
> Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
> Signed-off-by: Steve Sakoman <steve@sakoman.com>
> ---
>  bin/bitbake        | 2 +-
>  lib/bb/__init__.py | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/bin/bitbake b/bin/bitbake
> index 09cbb54e8..05b6ba742 100755
> --- a/bin/bitbake
> +++ b/bin/bitbake
> @@ -27,7 +27,7 @@ from bb.main import bitbake_main, BitBakeConfigParameters, BBMainException
>
>  bb.utils.check_system_locale()
>
> -__version__ = "2.12.0"
> +__version__ = "2.12.1"
>
>  if __name__ == "__main__":
>      if __version__ != bb.__version__:
> diff --git a/lib/bb/__init__.py b/lib/bb/__init__.py
> index 605355e1a..eba7b8fdd 100644
> --- a/lib/bb/__init__.py
> +++ b/lib/bb/__init__.py
> @@ -9,7 +9,7 @@
>  # SPDX-License-Identifier: GPL-2.0-only
>  #
>
> -__version__ = "2.12.0"
> +__version__ = "2.12.1"
>
>  import sys
>  if sys.version_info < (3, 9, 0):
> --
> 2.43.0
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#17999): https://lists.openembedded.org/g/bitbake-devel/message/17999
> Mute This Topic: https://lists.openembedded.org/mt/115172226/3617156
> Group Owner: bitbake-devel+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [martin.jansa@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>
Steve Sakoman Sept. 17, 2025, 1:57 p.m. UTC | #2 
On Wed, Sep 17, 2025 at 12:27 AM Martin Jansa <martin.jansa@gmail.com> wrote:
>
> Hello Steve,
>
> I've noticed today that 1.12.3 tag was pushed for current 1.12 branch:
>
> commit 710f98844ae30416bdf6a01b655df398b49574ec (tag: yocto-5.2.3,
> tag: 2025-04.3-walnascar, tag: 2.12.3, origin/2.12, oe/2.12,
> github/2.12, github.oe/2.12, 2.12)
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date:   Tue Jul 29 16:42:25 2025 -0400
>
>     utils: Optimise signal/sigmask performance
>
> Should I redo this as 2.12.4 and adjust the related change for oe-core
> to bump the minimal version to 2.12.4 as well?
>
> Similarly for scarthgap and 2.8 bitbake, which has 2.8.12 tag already,
> so instead of 2.8.1 I would bump it to 2.8.13.

Adding Richard since he is the bitbake maintainer.

I'm not sure what has been done historically.  We haven't been bumping
the version with each minor release, but it seems to make sense to me
to do the bump to 2.12.4 rather than 2.12.1

Steve

> commit 982645110a19ebb94d519926a4e14c8a2a205cfd (tag: yocto-5.0.12,
> tag: 2024-04.12-scarthgap, tag: 2.8.12, origin/2.8, oe/2.8,
> github/2.8, github.oe/2.8, 2.8)
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date:   Tue Jul 29 14:43:09 2025 -0400
>
>     utils: Optimise signal/sigmask performance
>
> Regards,
>
> On Wed, Sep 10, 2025 at 5:55 PM Steve Sakoman via
> lists.openembedded.org <steve=sakoman.com@lists.openembedded.org>
> wrote:
> >
> > From: Martin Jansa <martin.jansa@gmail.com>
> >
> > To indicate compatibility with python 3.14
> >
> > [YOCTO #15858]
> >
> > Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
> > Signed-off-by: Steve Sakoman <steve@sakoman.com>
> > ---
> >  bin/bitbake        | 2 +-
> >  lib/bb/__init__.py | 2 +-
> >  2 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/bin/bitbake b/bin/bitbake
> > index 09cbb54e8..05b6ba742 100755
> > --- a/bin/bitbake
> > +++ b/bin/bitbake
> > @@ -27,7 +27,7 @@ from bb.main import bitbake_main, BitBakeConfigParameters, BBMainException
> >
> >  bb.utils.check_system_locale()
> >
> > -__version__ = "2.12.0"
> > +__version__ = "2.12.1"
> >
> >  if __name__ == "__main__":
> >      if __version__ != bb.__version__:
> > diff --git a/lib/bb/__init__.py b/lib/bb/__init__.py
> > index 605355e1a..eba7b8fdd 100644
> > --- a/lib/bb/__init__.py
> > +++ b/lib/bb/__init__.py
> > @@ -9,7 +9,7 @@
> >  # SPDX-License-Identifier: GPL-2.0-only
> >  #
> >
> > -__version__ = "2.12.0"
> > +__version__ = "2.12.1"
> >
> >  import sys
> >  if sys.version_info < (3, 9, 0):
> > --
> > 2.43.0
> >
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#17999): https://lists.openembedded.org/g/bitbake-devel/message/17999
> > Mute This Topic: https://lists.openembedded.org/mt/115172226/3617156
> > Group Owner: bitbake-devel+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [martin.jansa@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
Martin Jansa Sept. 17, 2025, 2:05 p.m. UTC | #3 
I've sent the v2 of all 4 related changes to use 2.12.4 and 2.8.13.

I've also noticed that the sanity check for bitbake version is
executed too late after the utils.py is already failing with:
ERROR: Unable to parse oe-core/meta/lib/oe/utils.py
Traceback (most recent call last):
  File "oe-core/meta/lib/oe/utils.py", line 11, in <module>
    from bb import multiprocessing
ImportError: cannot import name 'multiprocessing' from 'bb'
(bitbake/lib/bb/__init__.py)

To avoid this issue I recommend to leave "lib/oe/utils: use
multiprocessing from bb" commit in oe-core scarthgap and walnascar for
some future batch and now merge just the bitbake version bump in
bitbake and the requirement for newer bitbake in oe-core, that way
people will hopefully update both before it gets really mandatory.

Cheers,

On Wed, Sep 17, 2025 at 3:57 PM Steve Sakoman <steve@sakoman.com> wrote:
>
> On Wed, Sep 17, 2025 at 12:27 AM Martin Jansa <martin.jansa@gmail.com> wrote:
> >
> > Hello Steve,
> >
> > I've noticed today that 1.12.3 tag was pushed for current 1.12 branch:
> >
> > commit 710f98844ae30416bdf6a01b655df398b49574ec (tag: yocto-5.2.3,
> > tag: 2025-04.3-walnascar, tag: 2.12.3, origin/2.12, oe/2.12,
> > github/2.12, github.oe/2.12, 2.12)
> > Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> > Date:   Tue Jul 29 16:42:25 2025 -0400
> >
> >     utils: Optimise signal/sigmask performance
> >
> > Should I redo this as 2.12.4 and adjust the related change for oe-core
> > to bump the minimal version to 2.12.4 as well?
> >
> > Similarly for scarthgap and 2.8 bitbake, which has 2.8.12 tag already,
> > so instead of 2.8.1 I would bump it to 2.8.13.
>
> Adding Richard since he is the bitbake maintainer.
>
> I'm not sure what has been done historically.  We haven't been bumping
> the version with each minor release, but it seems to make sense to me
> to do the bump to 2.12.4 rather than 2.12.1
>
> Steve
>
> > commit 982645110a19ebb94d519926a4e14c8a2a205cfd (tag: yocto-5.0.12,
> > tag: 2024-04.12-scarthgap, tag: 2.8.12, origin/2.8, oe/2.8,
> > github/2.8, github.oe/2.8, 2.8)
> > Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> > Date:   Tue Jul 29 14:43:09 2025 -0400
> >
> >     utils: Optimise signal/sigmask performance
> >
> > Regards,
> >
> > On Wed, Sep 10, 2025 at 5:55 PM Steve Sakoman via
> > lists.openembedded.org <steve=sakoman.com@lists.openembedded.org>
> > wrote:
> > >
> > > From: Martin Jansa <martin.jansa@gmail.com>
> > >
> > > To indicate compatibility with python 3.14
> > >
> > > [YOCTO #15858]
> > >
> > > Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
> > > Signed-off-by: Steve Sakoman <steve@sakoman.com>
> > > ---
> > >  bin/bitbake        | 2 +-
> > >  lib/bb/__init__.py | 2 +-
> > >  2 files changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/bin/bitbake b/bin/bitbake
> > > index 09cbb54e8..05b6ba742 100755
> > > --- a/bin/bitbake
> > > +++ b/bin/bitbake
> > > @@ -27,7 +27,7 @@ from bb.main import bitbake_main, BitBakeConfigParameters, BBMainException
> > >
> > >  bb.utils.check_system_locale()
> > >
> > > -__version__ = "2.12.0"
> > > +__version__ = "2.12.1"
> > >
> > >  if __name__ == "__main__":
> > >      if __version__ != bb.__version__:
> > > diff --git a/lib/bb/__init__.py b/lib/bb/__init__.py
> > > index 605355e1a..eba7b8fdd 100644
> > > --- a/lib/bb/__init__.py
> > > +++ b/lib/bb/__init__.py
> > > @@ -9,7 +9,7 @@
> > >  # SPDX-License-Identifier: GPL-2.0-only
> > >  #
> > >
> > > -__version__ = "2.12.0"
> > > +__version__ = "2.12.1"
> > >
> > >  import sys
> > >  if sys.version_info < (3, 9, 0):
> > > --
> > > 2.43.0
> > >
> > >
> > > -=-=-=-=-=-=-=-=-=-=-=-
> > > Links: You receive all messages sent to this group.
> > > View/Reply Online (#17999): https://lists.openembedded.org/g/bitbake-devel/message/17999
> > > Mute This Topic: https://lists.openembedded.org/mt/115172226/3617156
> > > Group Owner: bitbake-devel+owner@lists.openembedded.org
> > > Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [martin.jansa@gmail.com]
> > > -=-=-=-=-=-=-=-=-=-=-=-
> > >
Steve Sakoman Sept. 17, 2025, 4:25 p.m. UTC | #4 
On Wed, Sep 17, 2025 at 7:05 AM Martin Jansa <martin.jansa@gmail.com> wrote:
>
> I've sent the v2 of all 4 related changes to use 2.12.4 and 2.8.13.
>
> I've also noticed that the sanity check for bitbake version is
> executed too late after the utils.py is already failing with:
> ERROR: Unable to parse oe-core/meta/lib/oe/utils.py
> Traceback (most recent call last):
>   File "oe-core/meta/lib/oe/utils.py", line 11, in <module>
>     from bb import multiprocessing
> ImportError: cannot import name 'multiprocessing' from 'bb'
> (bitbake/lib/bb/__init__.py)
>
> To avoid this issue I recommend to leave "lib/oe/utils: use
> multiprocessing from bb" commit in oe-core scarthgap and walnascar for
> some future batch and now merge just the bitbake version bump in
> bitbake and the requirement for newer bitbake in oe-core, that way
> people will hopefully update both before it gets really mandatory.

I'll be doing the final walnascar build at the end of next week, so we
either need to have this sorted by early next week, or just decide to
leave things as they are with walnascar since it is going end of life.

I'll pull the patches from scarthgap till we sort the proper version
numbering and we can then stage them as you suggest.

Steve

> On Wed, Sep 17, 2025 at 3:57 PM Steve Sakoman <steve@sakoman.com> wrote:
> >
> > On Wed, Sep 17, 2025 at 12:27 AM Martin Jansa <martin.jansa@gmail.com> wrote:
> > >
> > > Hello Steve,
> > >
> > > I've noticed today that 1.12.3 tag was pushed for current 1.12 branch:
> > >
> > > commit 710f98844ae30416bdf6a01b655df398b49574ec (tag: yocto-5.2.3,
> > > tag: 2025-04.3-walnascar, tag: 2.12.3, origin/2.12, oe/2.12,
> > > github/2.12, github.oe/2.12, 2.12)
> > > Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > Date:   Tue Jul 29 16:42:25 2025 -0400
> > >
> > >     utils: Optimise signal/sigmask performance
> > >
> > > Should I redo this as 2.12.4 and adjust the related change for oe-core
> > > to bump the minimal version to 2.12.4 as well?
> > >
> > > Similarly for scarthgap and 2.8 bitbake, which has 2.8.12 tag already,
> > > so instead of 2.8.1 I would bump it to 2.8.13.
> >
> > Adding Richard since he is the bitbake maintainer.
> >
> > I'm not sure what has been done historically.  We haven't been bumping
> > the version with each minor release, but it seems to make sense to me
> > to do the bump to 2.12.4 rather than 2.12.1
> >
> > Steve
> >
> > > commit 982645110a19ebb94d519926a4e14c8a2a205cfd (tag: yocto-5.0.12,
> > > tag: 2024-04.12-scarthgap, tag: 2.8.12, origin/2.8, oe/2.8,
> > > github/2.8, github.oe/2.8, 2.8)
> > > Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> > > Date:   Tue Jul 29 14:43:09 2025 -0400
> > >
> > >     utils: Optimise signal/sigmask performance
> > >
> > > Regards,
> > >
> > > On Wed, Sep 10, 2025 at 5:55 PM Steve Sakoman via
> > > lists.openembedded.org <steve=sakoman.com@lists.openembedded.org>
> > > wrote:
> > > >
> > > > From: Martin Jansa <martin.jansa@gmail.com>
> > > >
> > > > To indicate compatibility with python 3.14
> > > >
> > > > [YOCTO #15858]
> > > >
> > > > Signed-off-by: Martin Jansa <martin.jansa@gmail.com>
> > > > Signed-off-by: Steve Sakoman <steve@sakoman.com>
> > > > ---
> > > >  bin/bitbake        | 2 +-
> > > >  lib/bb/__init__.py | 2 +-
> > > >  2 files changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/bin/bitbake b/bin/bitbake
> > > > index 09cbb54e8..05b6ba742 100755
> > > > --- a/bin/bitbake
> > > > +++ b/bin/bitbake
> > > > @@ -27,7 +27,7 @@ from bb.main import bitbake_main, BitBakeConfigParameters, BBMainException
> > > >
> > > >  bb.utils.check_system_locale()
> > > >
> > > > -__version__ = "2.12.0"
> > > > +__version__ = "2.12.1"
> > > >
> > > >  if __name__ == "__main__":
> > > >      if __version__ != bb.__version__:
> > > > diff --git a/lib/bb/__init__.py b/lib/bb/__init__.py
> > > > index 605355e1a..eba7b8fdd 100644
> > > > --- a/lib/bb/__init__.py
> > > > +++ b/lib/bb/__init__.py
> > > > @@ -9,7 +9,7 @@
> > > >  # SPDX-License-Identifier: GPL-2.0-only
> > > >  #
> > > >
> > > > -__version__ = "2.12.0"
> > > > +__version__ = "2.12.1"
> > > >
> > > >  import sys
> > > >  if sys.version_info < (3, 9, 0):
> > > > --
> > > > 2.43.0
> > > >
> > > >
> > > > -=-=-=-=-=-=-=-=-=-=-=-
> > > > Links: You receive all messages sent to this group.
> > > > View/Reply Online (#17999): https://lists.openembedded.org/g/bitbake-devel/message/17999
> > > > Mute This Topic: https://lists.openembedded.org/mt/115172226/3617156
> > > > Group Owner: bitbake-devel+owner@lists.openembedded.org
> > > > Unsubscribe: https://lists.openembedded.org/g/bitbake-devel/unsub [martin.jansa@gmail.com]
> > > > -=-=-=-=-=-=-=-=-=-=-=-
> > > >
Richard Purdie Sept. 17, 2025, 10:24 p.m. UTC | #5 
On Wed, 2025-09-17 at 09:27 +0200, Martin Jansa via lists.openembedded.org wrote:
> Hello Steve,
> 
> I've noticed today that 1.12.3 tag was pushed for current 1.12
> branch:
> 
> commit 710f98844ae30416bdf6a01b655df398b49574ec (tag: yocto-5.2.3,
> tag: 2025-04.3-walnascar, tag: 2.12.3, origin/2.12, oe/2.12,
> github/2.12, github.oe/2.12, 2.12)
> Author: Richard Purdie <richard.purdie@linuxfoundation.org>
> Date:   Tue Jul 29 16:42:25 2025 -0400
> 
>     utils: Optimise signal/sigmask performance
> 
> Should I redo this as 2.12.4 and adjust the related change for oe-
> core
> to bump the minimal version to 2.12.4 as well?
> 
> Similarly for scarthgap and 2.8 bitbake, which has 2.8.12 tag
> already,
> so instead of 2.8.1 I would bump it to 2.8.13.

Sorry about the delay.

Your patches are right and the tags are messed up. They're getting
cleaned up and I've merged the patches in the meantime.

Cheers,

Richard
Richard Purdie Sept. 17, 2025, 10:34 p.m. UTC | #6 
On Wed, 2025-09-17 at 09:25 -0700, Steve Sakoman wrote:
> On Wed, Sep 17, 2025 at 7:05 AM Martin Jansa <martin.jansa@gmail.com> wrote:
> > 
> > I've sent the v2 of all 4 related changes to use 2.12.4 and 2.8.13.
> > 
> > I've also noticed that the sanity check for bitbake version is
> > executed too late after the utils.py is already failing with:
> > ERROR: Unable to parse oe-core/meta/lib/oe/utils.py
> > Traceback (most recent call last):
> >   File "oe-core/meta/lib/oe/utils.py", line 11, in <module>
> >     from bb import multiprocessing
> > ImportError: cannot import name 'multiprocessing' from 'bb'
> > (bitbake/lib/bb/__init__.py)
> > 
> > To avoid this issue I recommend to leave "lib/oe/utils: use
> > multiprocessing from bb" commit in oe-core scarthgap and walnascar for
> > some future batch and now merge just the bitbake version bump in
> > bitbake and the requirement for newer bitbake in oe-core, that way
> > people will hopefully update both before it gets really mandatory.
> 
> I'll be doing the final walnascar build at the end of next week, so we
> either need to have this sorted by early next week, or just decide to
> leave things as they are with walnascar since it is going end of life.
> 
> I'll pull the patches from scarthgap till we sort the proper version
> numbering and we can then stage them as you suggest.

I've pushed what I think makes sense, hopefully that gets things unblocked.

Cheers,

Richard
Steve Sakoman Sept. 17, 2025, 10:35 p.m. UTC | #7 
On Wed, Sep 17, 2025 at 3:34 PM Richard Purdie
<richard.purdie@linuxfoundation.org> wrote:
>
> On Wed, 2025-09-17 at 09:25 -0700, Steve Sakoman wrote:
> > On Wed, Sep 17, 2025 at 7:05 AM Martin Jansa <martin.jansa@gmail.com> wrote:
> > >
> > > I've sent the v2 of all 4 related changes to use 2.12.4 and 2.8.13.
> > >
> > > I've also noticed that the sanity check for bitbake version is
> > > executed too late after the utils.py is already failing with:
> > > ERROR: Unable to parse oe-core/meta/lib/oe/utils.py
> > > Traceback (most recent call last):
> > >   File "oe-core/meta/lib/oe/utils.py", line 11, in <module>
> > >     from bb import multiprocessing
> > > ImportError: cannot import name 'multiprocessing' from 'bb'
> > > (bitbake/lib/bb/__init__.py)
> > >
> > > To avoid this issue I recommend to leave "lib/oe/utils: use
> > > multiprocessing from bb" commit in oe-core scarthgap and walnascar for
> > > some future batch and now merge just the bitbake version bump in
> > > bitbake and the requirement for newer bitbake in oe-core, that way
> > > people will hopefully update both before it gets really mandatory.
> >
> > I'll be doing the final walnascar build at the end of next week, so we
> > either need to have this sorted by early next week, or just decide to
> > leave things as they are with walnascar since it is going end of life.
> >
> > I'll pull the patches from scarthgap till we sort the proper version
> > numbering and we can then stage them as you suggest.
>
> I've pushed what I think makes sense, hopefully that gets things unblocked.

It does.  Thanks!

Steve

>
> Cheers,
>
> Richard
diff mbox series

Patch

diff --git a/bin/bitbake b/bin/bitbake
index 09cbb54e8..05b6ba742 100755
--- a/bin/bitbake
+++ b/bin/bitbake
@@ -27,7 +27,7 @@  from bb.main import bitbake_main, BitBakeConfigParameters, BBMainException
 
 bb.utils.check_system_locale()
 
-__version__ = "2.12.0"
+__version__ = "2.12.1"
 
 if __name__ == "__main__":
     if __version__ != bb.__version__:
diff --git a/lib/bb/__init__.py b/lib/bb/__init__.py
index 605355e1a..eba7b8fdd 100644
--- a/lib/bb/__init__.py
+++ b/lib/bb/__init__.py
@@ -9,7 +9,7 @@ 
 # SPDX-License-Identifier: GPL-2.0-only
 #
 
-__version__ = "2.12.0"
+__version__ = "2.12.1"
 
 import sys
 if sys.version_info < (3, 9, 0):