mbox

[scarthgap,2.8,0/1] Pull request (cover letter only)

Message ID cover.1792191269.git.yoann.congal@smile.fr
State Not Applicable, archived
Headers show

Pull-request

https://git.openembedded.org/bitbake-contrib stable/2.8-next

Message

Yoann Congal Oct. 16, 2026, 10:55 p.m. UTC
This is the patch from the last patch review:
https://lore.kernel.org/all/cover.1792020468.git.yoann.congal@smile.fr/

Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/valkyrie/?#/builders/29/builds/4934
* reproducible failed with #15898 – New sstate.yp.org CDN revealed partial sstate reproducibility tests false-positive error
  But the test warns about a missing sstate object from the reproducibleB
  build that is supposed to rebuild everything anyway, then, rebuilds the
  recipe. So, there is no issue with the series.


The following changes since commit d3b32587c2314febf96897f97e0172790b4fc1cf:

  toastergui/views: Replace os.system call with improved parameter handling (2026-09-28 22:25:53 +0100)

are available in the Git repository at:

  https://git.openembedded.org/bitbake-contrib stable/2.8-next
  https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.8-next

for you to fetch changes up to 6b443060ee96a62efb94723c97f22b51c9b20507:

  prserv: commit new revisions when a request succeeds (2026-10-11 23:40:57 +0200)

----------------------------------------------------------------

Wadim Mueller (1):
  prserv: commit new revisions when a request succeeds

 lib/prserv/serv.py | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Comments

Richard Purdie Oct. 17, 2026, 3:18 p.m. UTC | #1
On Sat, 2026-10-17 at 00:55 +0200, Yoann Congal wrote:
> This is the patch from the last patch review:
> https://lore.kernel.org/all/cover.1792020468.git.yoann.congal@smile.fr/
> 
> Passed a-full on autobuilder:
> https://autobuilder.yoctoproject.org/valkyrie/?#/builders/29/builds/4934
> * reproducible failed with #15898 – New sstate.yp.org CDN revealed partial sstate reproducibility tests false-positive error
>   But the test warns about a missing sstate object from the reproducibleB
>   build that is supposed to rebuild everything anyway, then, rebuilds the
>   recipe. So, there is no issue with the series.
> 
> 
> The following changes since commit d3b32587c2314febf96897f97e0172790b4fc1cf:
> 
>   toastergui/views: Replace os.system call with improved parameter handling (2026-09-28 22:25:53 +0100)
> 
> are available in the Git repository at:
> 
>   https://git.openembedded.org/bitbake-contrib stable/2.8-next
>   https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.8-next
> 
> for you to fetch changes up to 6b443060ee96a62efb94723c97f22b51c9b20507:
> 
>   prserv: commit new revisions when a request succeeds (2026-10-11 23:40:57 +0200)

Do other branches need that patch?

Cheers,

Richard
Yoann Congal Oct. 17, 2026, 3:50 p.m. UTC | #2
Yoann Congal
Smile ECS

Le sam. 17 oct. 2026, 17:18, Richard Purdie <
richard.purdie@linuxfoundation.org> a écrit :

> On Sat, 2026-10-17 at 00:55 +0200, Yoann Congal wrote:
> > This is the patch from the last patch review:
> > https://lore.kernel.org/all/cover.1792020468.git.yoann.congal@smile.fr/
> >
> > Passed a-full on autobuilder:
> > https://autobuilder.yoctoproject.org/valkyrie/?#/builders/29/builds/4934
> > * reproducible failed with #15898 – New sstate.yp.org CDN revealed
> partial sstate reproducibility tests false-positive error
> >   But the test warns about a missing sstate object from the reproducibleB
> >   build that is supposed to rebuild everything anyway, then, rebuilds the
> >   recipe. So, there is no issue with the series.
> >
> >
> > The following changes since commit
> d3b32587c2314febf96897f97e0172790b4fc1cf:
> >
> >   toastergui/views: Replace os.system call with improved parameter
> handling (2026-09-28 22:25:53 +0100)
> >
> > are available in the Git repository at:
> >
> >   https://git.openembedded.org/bitbake-contrib stable/2.8-next
> >   https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.8-next
> >
> > for you to fetch changes up to 6b443060ee96a62efb94723c97f22b51c9b20507:
> >
> >   prserv: commit new revisions when a request succeeds (2026-10-11
> 23:40:57 +0200)
>
> Do other branches need that patch?
>

I think not.

The patch says:
This is specific to the 2.8 branch. The server was reworked for master and
2.10 ("prserv: enable database sharing" and the commits around it), which
commits where values are stored and uses WAL, so master does not have this
problem and the commit cannot be backported as it is.

Other supported branches are 2.18, 2.20 (all above 2.10 and the referenced
patch)

I checked the 2.10 commit and it looked like it matched so I took the patch.


Cheers,
>
> Richard
>
Richard Purdie Oct. 17, 2026, 4:09 p.m. UTC | #3
On Sat, 2026-10-17 at 17:50 +0200, Yoann Congal wrote:
> Le sam. 17 oct. 2026, 17:18, Richard Purdie <richard.purdie@linuxfoundation.org> a écrit :
> > On Sat, 2026-10-17 at 00:55 +0200, Yoann Congal wrote:
> > > 
> > > The following changes since commit d3b32587c2314febf96897f97e0172790b4fc1cf:
> > > 
> > >   toastergui/views: Replace os.system call with improved parameter handling (2026-09-28 22:25:53 +0100)
> > > 
> > > are available in the Git repository at:
> > > 
> > >   https://git.openembedded.org/bitbake-contrib stable/2.8-next
> > >   https://git.openembedded.org/bitbake-contrib/log/?h=stable/2.8-next
> > > 
> > > for you to fetch changes up to 6b443060ee96a62efb94723c97f22b51c9b20507:
> > > 
> > >   prserv: commit new revisions when a request succeeds (2026-10-11 23:40:57 +0200)
> > 
> > Do other branches need that patch?
> 
> I think not.
> 
> The patch says:
> This is specific to the 2.8 branch. The server was reworked for master and
> 2.10 ("prserv: enable database sharing" and the commits around it), which
> commits where values are stored and uses WAL, so master does not have this
> problem and the commit cannot be backported as it is.
>  
> Other supported branches are 2.18, 2.20 (all above 2.10 and the referenced patch)
> 
> I checked the 2.10 commit and it looked like it matched so I took the patch.

Agreed, sorry, I think I misread something somewhere when comparing to
the current code. This does seem to make sense and I've merged.

Thanks,

Richard