Re: [yocto] systemd Version Going Backwards on Warrior

2019-10-29 Thread Ross Burton
On 29/10/2019 04:41, Robert Joslyn wrote: On Mon, 2019-10-28 at 19:06 +, Ross Burton wrote: On 28/10/2019 16:25, robert.jos...@redrectangle.org wrote: I'm using buildhistory in one of my builds that creates a package feed, and a recent update to systemd on warrior triggered version- going-b

Re: [yocto] systemd Version Going Backwards on Warrior

2019-10-29 Thread akuster
On 10/29/19 11:50 AM, Ross Burton wrote: > On 29/10/2019 04:41, Robert Joslyn wrote: >> On Mon, 2019-10-28 at 19:06 +, Ross Burton wrote: >>> On 28/10/2019 16:25, robert.jos...@redrectangle.org wrote: I'm using buildhistory in one of my builds that creates a package feed, and a rece

[yocto] Yocto Project Status WW44’19

2019-10-29 Thread Stephen K Jolley
Current Dev Position: YP 3.1 M1 Next Deadline: YP 3.1 M1 build Dec. 2, 2019 SWAT Team Rotation: - SWAT lead is currently: Amanda - SWAT team rotation: Amanda -> Armin on Nov. 1, 2019 - SWAT team rotation: Armin-> Anuj on Nov. 8, 2019 - https://wiki.yoctoproject.org/wi

Re: [yocto] systemd Version Going Backwards on Warrior

2019-10-29 Thread Martin Jansa
PR server never knows which one is really newer (in git). It just returns max(LOCALCOUNT)+1 when it gets query for hash which isn't stored in the database yet. Either the build in question didn't use PRserv at all or PRserv's cache was deleted between builds or the builds were using the same buil

Re: [yocto] [OE-core] Yocto Project Status WW44’19

2019-10-29 Thread akuster808
On 10/29/19 5:12 PM, Stephen K Jolley wrote: > > Current Dev Position: YP 3.1 M1  > > Next Deadline: YP 3.1 M1 build Dec. 2, 2019 > I noticed there is no 3.0.1 schedule.  Can we try for early December? > > SWAT Team Rotation: > > * > > SWAT lead is currently: Amanda > > * > > SWAT tea

Re: [yocto] systemd Version Going Backwards on Warrior

2019-10-29 Thread Robert Joslyn
On Tue, 2019-10-29 at 20:30 +0100, Martin Jansa wrote: > PR server never knows which one is really newer (in git). > > It just returns max(LOCALCOUNT)+1 when it gets query for hash which > isn't stored in the database yet. > > Either the build in question didn't use PRserv at all or PRserv's cach

[yocto] [zeus] icu-native-64.2-r0 do_configure: configure failed

2019-10-29 Thread star
Build of image failed, I got strange and long error messages like: ERROR: icu-native-64.2-r0 do_configure: configure failed ERROR: icu-native-64.2-r0 do_configure: Execution of '/home/.../tmp/work/x86_64-linux/icu-native/64.2-r0/temp/run.do_configure ... | configure: WARNING: unrecognized options