From: Peter Seiderer <ps.report@gmx.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] package/qt5location: handle plugins being conditionally built
Date: Sat, 29 Jul 2017 00:08:38 +0200 [thread overview]
Message-ID: <20170729000838.487a69cd@gmx.net> (raw)
In-Reply-To: <e4f07131-c47e-f3f6-e0fc-a96a1defb6c6@microchip.com>
Hello Joshua,
On Fri, 28 Jul 2017 14:54:06 -0700, Joshua Henderson <joshua.henderson@microchip.com> wrote:
> Arnout,
>
> On 07/28/2017 02:17 PM, Arnout Vandecappelle wrote:
> >
> >
> > On 28-07-17 18:31, Joshua Henderson wrote:
> >> Thomas, Peter,
> >>
> >> On 07/25/2017 12:52 PM, Thomas Petazzoni wrote:
> > [snip]
> >>> Thanks, but Peter had sent an almost identical patch a few hours
> >>> before, and I've applied his patch.
> >>
> >> It wasn't exactly identical. The applied patch now causes a build failure for 5.6.2:
> >
> > If you noticed that Peter's patch was wrong, you could have mentioned it in the
> > commit message of your patch (below the --- line). Then Thomas might have seen
> > the difference and applied your patch instead.
>
> It was caught last night by a local build server. Didn't notice it previously. I
> have actually been flying right along using his patch, but only with 5.9.1. This
> is only an issue with 5.6.2.
>
Ups, my fault...
> >
> >
> >> qt5location 5.6.2 Patching^[
> >> Applying 0001-Fix-plugins-build-dependency.patch using patch:
> >> patching file src/src.pro
> >> Hunk #1 FAILED at 7.
> >> Hunk #2 succeeded at 14 (offset -4 lines).
> >> 1 out of 2 hunks FAILED -- saving rejects to file src/src.pro.rej
> >
> > Care to send a fix (I guess just moving the patch to the right directory)?
>
> That should do it. Done.
Thanks...
>
> >
> > When you do, please also add a reference to the autobuilder failure:
> >
> > http://autobuild.buildroot.net/results/676abe008c9c4bddfddd7b041d8db9999e9e899d
>
> OK. Is there any way to subscribe to these failures? Even better, for specific packages?
>
The DEVELOPERS file in the buildroot root directory, send a patch adding yourself
for packages you contributed to/interested in...
> >
>
> ...
>
> >>
> >> I also have several other patches to rev (add qt5wayland and license hashes for all of qt5).
Did not find time for testing the qt5wayland patch yet and missed the license hash patch...
Regards,
Peter
> >
> > For the qt5wayland patch, since you wrote yourself "This needs a v3 before
> > applying.", it's been marked as Changes Requested in patchwork so it won't be
> > applied and probably won't be reviewed either.
>
> OK.
>
> Josh
prev parent reply other threads:[~2017-07-28 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 19:50 [Buildroot] [PATCH v3] package/qt5location: handle plugins being conditionally built Joshua Henderson
2017-07-25 19:52 ` Thomas Petazzoni
2017-07-27 7:09 ` Peter Seiderer
2017-07-28 16:31 ` Joshua Henderson
2017-07-28 21:17 ` Arnout Vandecappelle
2017-07-28 21:54 ` Joshua Henderson
2017-07-28 21:59 ` Thomas Petazzoni
2017-07-28 22:08 ` Peter Seiderer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170729000838.487a69cd@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox