All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: Philip Balister <philip@balister.org>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: ✗ patchtest: failure for Avoid build failures due to setscene errors
Date: Wed, 30 Aug 2017 07:41:47 +0000	[thread overview]
Message-ID: <906d179400764587a86b0b120ce99951@XBOX02.axis.com> (raw)
In-Reply-To: <c752c36a-0b4c-7ab0-5ce1-b98bf8998585@balister.org>

> -----Original Message-----
> From: openembedded-core-bounces@lists.openembedded.org
> [mailto:openembedded-core-bounces@lists.openembedded.org] On Behalf Of
> Philip Balister
> Sent: den 30 augusti 2017 00:36
> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>; openembedded-
> core@lists.openembedded.org
> Subject: Re: [OE-core] ✗ patchtest: failure for Avoid build failures
> due to setscene errors
> 
> On 08/29/2017 04:25 PM, Peter Kjellerstedt wrote:
> >> -----Original Message-----
> >> From: Patchwork [mailto:patchwork@patchwork.openembedded.org]
> >> Sent: den 29 augusti 2017 22:05
> >> To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
> >> Cc: openembedded-core@lists.openembedded.org
> >> Subject: ✗ patchtest: failure for Avoid build failures due to
> setscene
> >> errors
> >>
> >> == Series Details ==
> >>
> >> Series: Avoid build failures due to setscene errors
> >> Revision: 1
> >> URL   : https://patchwork.openembedded.org/series/8575/
> >> State : failure
> >>
> >> == Summary ==
> >>
> >>
> >> Thank you for submitting this patch series to OpenEmbedded Core.
> This is
> >> an automated response. Several tests have been executed on the
> proposed
> >> series by patchtest resulting in the following failures:
> >>
> >>
> >>
> >> * Issue             Series does not apply on top of target branch
> [test_series_merge_on_head]
> >>   Suggested fix    Rebase your series on top of targeted branch
> >>   Targeted branch  master (currently at 2454019844)

Actually, would it be possible to get a better error message that 
indicates that one has mixed in patches for other projects that are 
part of Poky? When working with Poky as the basis, differentiating 
between, e.g., bitbake and OE-Core is not something that comes 
natural. I actually had to think both once and twice before I 
realized that one of my patches was actually for bitbake (and just 
barely stopped me in time from sending an irritated mail about why 
patchtest wasn't accepting my changes).

> > Argh, why can't this handle combined bitbake and OE-Core changes,
> > i.e., changes for Poky. Oh well, separate patches coming up...
> 
> Because poky isn't the upstream project.
> 
> Philip

Well, I know that. However, I doubt we are the only ones who use Poky 
as the base for our distribution. Thus Poky is our de facto upstream. 
So when working on a change that affects both BitBake, OE-Core and 
maybe even the OE documentation (none of which is uncommon), having 
to split the changes in multiple stacks and keeping track of them 
together over multiple projects is not very encouraging, especially 
when Poky is distributed as a unit.

I am not asking for this to change, but it would have been nice to be 
able to treat Poky as an upstream and to deliver changes that span the 
individual projects as one set of changes against Poky.

//Peter


  reply	other threads:[~2017-08-30  7:41 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-29 20:00 [PATCH 0/2] Avoid build failures due to setscene errors Peter Kjellerstedt
2017-08-29 20:00 ` [PATCH 1/2] bitbake: fetch2: Allow Fetch.download() to warn instead of error Peter Kjellerstedt
2017-08-29 20:00 ` [PATCH 2/2] sstate.bbclass: Do not cause build failures due to setscene errors Peter Kjellerstedt
2017-08-29 20:04 ` ✗ patchtest: failure for Avoid " Patchwork
2017-08-29 20:25   ` Peter Kjellerstedt
2017-08-29 22:35     ` Philip Balister
2017-08-30  7:41       ` Peter Kjellerstedt [this message]
2017-08-29 20:38 ` [PATCH 0/2] " Andre McCurdy
2017-08-29 20:59   ` Peter Kjellerstedt
2017-08-29 21:49     ` Richard Purdie
2017-08-30  6:44       ` Peter Kjellerstedt
2017-08-30  7:54         ` Martin Jansa
2019-11-29 16:48           ` Martin Jansa
2020-01-09 12:26             ` Ricardo Ribalda Delgado
2017-08-30  8:02         ` Richard Purdie
2017-08-30  9:52           ` Peter Kjellerstedt
2017-08-29 22:03     ` Andre McCurdy
2017-08-30  9:55       ` Peter Kjellerstedt

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=906d179400764587a86b0b120ce99951@XBOX02.axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=philip@balister.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.