[Buildroot] 2016.05-rc1 approaching: what to merge?

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Thomas Petazzoni]

Hello,

We're approaching the end of April, and therefore the beginning of May,
which means that 2016.05-rc1 will be released soon, most likely in
about a week.

As a reminder, once -rc1 is released, we don't merge new packages or
version bumps, but only build fixes, security fixes, documentation
updates, etc. Of course, anything that doesn't get merged before -rc1
can be merged for the next release, 2016.08.

So the question is: we have ~230 patches pending patchwork. Do you see
anything that we should really merge before 2016.05-rc1 is released?

Thanks for your feedback,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Yegor Yefremov]

On Thu, Apr 28, 2016 at 4:00 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> We're approaching the end of April, and therefore the beginning of May,
> which means that 2016.05-rc1 will be released soon, most likely in
> about a week.
>
> As a reminder, once -rc1 is released, we don't merge new packages or
> version bumps, but only build fixes, security fixes, documentation
> updates, etc. Of course, anything that doesn't get merged before -rc1
> can be merged for the next release, 2016.08.
>
> So the question is: we have ~230 patches pending patchwork. Do you see
> anything that we should really merge before 2016.05-rc1 is released?
>
> Thanks for your feedback,

I would like to see Barebox double config feature merged.

Perhaps Python 3.5 and pyc related stuff.

Yegor

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Thomas Petazzoni]

Hello,

On Thu, 28 Apr 2016 16:06:40 +0200, Yegor Yefremov wrote:

> I would like to see Barebox double config feature merged.

On that one, I was waiting for the final review from Arnout. With the
latest changes done by Pieter, I'm happy as it is. I'll merge it over
the WE, hopefully after Arnout gave his Reviewed-by.

> Perhaps Python 3.5 and pyc related stuff.

So Python 3.5 is http://patchwork.ozlabs.org/patch/562627/.

For the .pyc stuff, we have http://patchwork.ozlabs.org/patch/546542/
and http://patchwork.ozlabs.org/patch/580512/. Are you talking about
both of them, or more specifically one of the two?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Yegor Yefremov]

On Thu, Apr 28, 2016 at 4:20 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Thu, 28 Apr 2016 16:06:40 +0200, Yegor Yefremov wrote:
>
>> I would like to see Barebox double config feature merged.
>
> On that one, I was waiting for the final review from Arnout. With the
> latest changes done by Pieter, I'm happy as it is. I'll merge it over
> the WE, hopefully after Arnout gave his Reviewed-by.
>
>> Perhaps Python 3.5 and pyc related stuff.
>
> So Python 3.5 is http://patchwork.ozlabs.org/patch/562627/.
>
> For the .pyc stuff, we have http://patchwork.ozlabs.org/patch/546542/
> and http://patchwork.ozlabs.org/patch/580512/. Are you talking about
> both of them, or more specifically one of the two?

First of all this one http://patchwork.ozlabs.org/patch/546542/, the
second one can be reviewed/reworked later on top of the first one.

Yegor

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Thomas Petazzoni]

Hello,

On Thu, 28 Apr 2016 16:06:40 +0200, Yegor Yefremov wrote:

> Perhaps Python 3.5 and pyc related stuff.

I've sent a new version of the Python 3.5 and pyc related stuff, so if
you have some time to give a test and/or review, it would be good.
Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Thomas Petazzoni]

Hello,

On Thu, 28 Apr 2016 16:06:40 +0200, Yegor Yefremov wrote:

> I would like to see Barebox double config feature merged.

Merged. Thanks for reminding me about this feature!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Yegor Yefremov]

On Sun, May 1, 2016 at 2:35 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> On Thu, 28 Apr 2016 16:06:40 +0200, Yegor Yefremov wrote:
>
>> I would like to see Barebox double config feature merged.
>
> Merged. Thanks for reminding me about this feature!

Thanks for merging. Now I can send my follow up patch adding a path to
custom embedded environment.

Yegor

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Thomas Petazzoni]

Hello,

On Sun, 1 May 2016 16:17:19 +0200, Yegor Yefremov wrote:

> Thanks for merging. Now I can send my follow up patch adding a path to
> custom embedded environment.

You mean https://patchwork.ozlabs.org/patch/583971/, but reworked for
the two barebox thing?

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Julien CORJON]

Thomas, All,

Le 28/04/2016 16:00, Thomas Petazzoni a ?crit :
> Hello,
>
> We're approaching the end of April, and therefore the beginning of May,
> which means that 2016.05-rc1 will be released soon, most likely in
> about a week.
>
> As a reminder, once -rc1 is released, we don't merge new packages or
> version bumps, but only build fixes, security fixes, documentation
> updates, etc. Of course, anything that doesn't get merged before -rc1
> can be merged for the next release, 2016.08.
>
> So the question is: we have ~230 patches pending patchwork. Do you see
> anything that we should really merge before 2016.05-rc1 is released?

I would really appreciate to see android-tools[1] in 2016.05 as I use it 
for target production which will start in about 2 month.

>
> Thanks for your feedback,
>
> Thomas
>

Regards,

Julien

[1] https://patchwork.ozlabs.org/patch/547683/

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Thomas Petazzoni]

Hello,

On Thu, 28 Apr 2016 14:15:05 +0000, Julien CORJON wrote:

> > So the question is: we have ~230 patches pending patchwork. Do you see
> > anything that we should really merge before 2016.05-rc1 is released?  
> 
> I would really appreciate to see android-tools[1] in 2016.05 as I use it 
> for target production which will start in about 2 month.

Thanks for the reminder, I've applied the android-tools patch.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Gustavo Zacarias]

On 28/04/16 11:00, Thomas Petazzoni wrote:

> So the question is: we have ~230 patches pending patchwork. Do you see
> anything that we should really merge before 2016.05-rc1 is released?
>
> Thanks for your feedback,
>
> Thomas

Hi.
webkitgtk/midori bumps?
Now that the bulk of the hard patches (gtk3/epoxy/wayland) have landed 
these would be a nice addition.
I'm also interested in the enlightenment bump to have a more meaningful 
desktop to test and play with wayland (needs extra support, but the bump 
is a prereq) so i'll likely look into it.
Regards.

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Thomas Petazzoni]

Hello,

On Thu, 28 Apr 2016 11:40:57 -0300, Gustavo Zacarias wrote:

> webkitgtk/midori bumps?

I've applied.

> Now that the bulk of the hard patches (gtk3/epoxy/wayland) have landed 
> these would be a nice addition.
> I'm also interested in the enlightenment bump to have a more meaningful 
> desktop to test and play with wayland (needs extra support, but the bump 
> is a prereq) so i'll likely look into it.

I see you tested the EFL bump, and found some issues, so I'm not going
to take this for the moment. Thanks for the testing!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Bernd Kuhls]

[posted and mailed]

Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote
in news:20160428160000.5db9d1cb at free-electrons.com: 

> So the question is: we have ~230 patches pending patchwork. Do you see
> anything that we should really merge before 2016.05-rc1 is released?

Hi Thomas,

despite the fact that vlc 3.0, which contains support for ffmpeg 3.x, is
not released yet I would still like to see the bump to ffmpeg 3.0 in
2016.05. Currently I am preparing a new iteration of the patchset with the
latest ffmpeg 3.0.2 bump.

Regards, Bernd

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Thomas De Schampheleire]

Hi Thomas,

On Thu, Apr 28, 2016 at 4:00 PM, Thomas Petazzoni
<thomas.petazzoni@free-electrons.com> wrote:
> Hello,
>
> We're approaching the end of April, and therefore the beginning of May,
> which means that 2016.05-rc1 will be released soon, most likely in
> about a week.
>
> As a reminder, once -rc1 is released, we don't merge new packages or
> version bumps, but only build fixes, security fixes, documentation
> updates, etc. Of course, anything that doesn't get merged before -rc1
> can be merged for the next release, 2016.08.
>
> So the question is: we have ~230 patches pending patchwork. Do you see
> anything that we should really merge before 2016.05-rc1 is released?

I just submitted three patches:
- opkg: this is a build fix, I think it would best go in 2016.05
- ccache: this is also a build fix, but only triggered if you manually
run 'make host-ccache' as opposed to a standard build. I think it is a
trivial fix, but not mandatory for 2016.05. For you to decide how to
handle it.
- gdb wrapper: this was submitted first at the developer days in
February. I kind of forgot about it until now :) I made one minor fix
and resubmitted as v2. It is not crucial for the release but it would
be great to have it included of course. Also for you to decide how to
handle it.

Best regards,
Thomas

[Buildroot] 2016.05-rc1 approaching: what to merge?

[Carlos Santos]

> From: "Thomas Petazzoni" <thomas.petazzoni@free-electrons.com>
> To: buildroot at uclibc.org
> Sent: Thursday, April 28, 2016 11:00:00 AM
> Subject: [Buildroot] 2016.05-rc1 approaching: what to merge?

> Hello,
> 
> We're approaching the end of April, and therefore the beginning of May,
> which means that 2016.05-rc1 will be released soon, most likely in
> about a week.
> 
> As a reminder, once -rc1 is released, we don't merge new packages or
> version bumps, but only build fixes, security fixes, documentation
> updates, etc. Of course, anything that doesn't get merged before -rc1
> can be merged for the next release, 2016.08.
> 
> So the question is: we have ~230 patches pending patchwork. Do you see
> anything that we should really merge before 2016.05-rc1 is released?

I would like to have the fix for GTest/GMock applied before I start working on a new "googletest" package that would replace them:

    http://patchwork.ozlabs.org/patch/586130/

Carlos Santos (Casantos)
DATACOM, P&D