Re: [PATCH] wayland-protocols: upgrade to 1.11

[Denys Dmytriyenko <denis@denix.org>]

On Tue, Oct 17, 2017 at 06:53:25PM -0400, Denys Dmytriyenko wrote:
> On Mon, Oct 16, 2017 at 09:56:56PM +0100, Burton, Ross wrote:
> > On 16 October 2017 at 21:54, Denys Dmytriyenko <denis@denix.org> wrote:
> > 
> > > On Mon, Oct 16, 2017 at 09:31:49PM +0100, Burton, Ross wrote:
> > > > On 16 October 2017 at 18:48, Denys Dmytriyenko <denis@denix.org> wrote:
> > > >
> > > > > On Fri, Oct 13, 2017 at 12:28:25PM -0400, Denys Dmytriyenko wrote:
> > > > > > On Fri, Oct 13, 2017 at 12:33:35PM +0100, Burton, Ross wrote:
> > > > > > > On 12 October 2017 at 20:35, Denys Dmytriyenko <denis@denix.org>
> > > > > wrote:
> > > > > > >
> > > > > > > > From: Denys Dmytriyenko <denys@ti.com>
> > > > > > > >
> > > > > > > > Signed-off-by: Denys Dmytriyenko <denys@ti.com>
> > > > > > > >
> > > > > > >
> > > > > > > One day I'll figure out why quilt appears to be non-deterministic
> > > about
> > > > > > > this but:
> > > > > > >
> > > > > > > ERROR: wayland-protocols-1.11-r0 do_patch: Command Error: 'quilt
> > > > > --quiltrc
> > > > > > > /data/poky-tmp/master/build/work/all-poky-linux/wayland-
> > > > > protocols/1.11-r0/recipe-sysroot-native/etc/quiltrc
> > > > > > > push' exited with 0  Output:
> > > > > > > Applying patch usesysrootprefixforpkgdatadirvariable.patch
> > > > > >
> > > > > > I don't see this patch in master. Works fine in distroless and poky
> > > from
> > > > > > master.
> > > > >
> > > > > Ping.
> > > >
> > > > The patch fails here, so I'm waiting for a v2.
> > >
> > > As I said above - there's no usesysrootprefixforpkgdatadirvariable.patch
> > > in
> > > wayland-protocols recipe in master, master-next or rocko branches:
> > >
> > > http://cgit.openembedded.org/openembedded-core/tree/meta/
> > > recipes-graphics/wayland/wayland-protocols_1.10.bb
> > >
> > > Are you sure you don't have something in your local tree?
> > >
> > 
> > Damnit, yes.  There's an earlier series to remove the nasty hacks. I
> > realised this when I saw your first reply to my patch but then forgot
> > again, sorry!
> > 
> > One of them needs to land first, and they won.  Wait for master to re-open,
> > or rebase on top of ross/mut.
> 
> I'm not sure how this is possible, when new revisions of that patch are still 
> coming in - v5 was just submitted yesterday, while ross/mut shows the patch 
> was merged 6 hours ago (unless you rebased your branch, of course)...
> 
> Anyway, looks like the patch that breaks for you is a backport from version 
> 1.11, for which I submitted the update, so it simply needs to be dropped.

v2 has been posted.