All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Gherzan <andrei@gherzan.ro>
To: Herve Jourdain <herve.jourdain@neuf.fr>
Cc: yocto@yoctoproject.org, 'Gary Thomas' <gary@mlbassoc.com>
Subject: Re: ***SPAM*** Re: [meta-raspberrypi] Current master broken
Date: Tue, 6 Dec 2016 18:11:10 +0000	[thread overview]
Message-ID: <20161206181110.GG1636@carbonA> (raw)
In-Reply-To: <009401d24feb$33bc8f30$9b35ad90$@neuf.fr>

[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

On Tue, Dec 06, 2016 at 07:04:31PM +0100, Herve Jourdain wrote:
> Hi Andrei,
>
> But I believe that the core of the problem is not necessarily the patch in
> oe-core to detect the kernel version itself, but like Khem mentioned the
> fact that a "well known" SRCREV is only valid for a brief period of time
> under the RPI tree "constant" rebasing we've been experiencing lately.
> So basically, the SRCREV that is used is not corresponding to what it used
> to be, if it's still there in the tree, and the oe-core detects that - the
> SRCREV thought it was one version of the kernel, and it just happened that
> it corresponds to a different codebase with a different linux version.
> Killing the error reporting by a patch will probably not prevent the
> mismatch happening behind the scene.
> So like Khem mentioned, either we find a way to "prevent" the rebasing at
> the source, or we need to track down every version we want to support, and
> update SRCREV and corresponding kernel version for those.

Got it now. What do you mean by "track down every version we want"?
--
Andrei Gherzan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 817 bytes --]

  reply	other threads:[~2016-12-06 18:11 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-03  7:33 [meta-raspberrypi] Current master broken Gary Thomas
2016-12-03 14:16 ` Paul Barker
2016-12-05  0:54   ` Andrei Gherzan
2016-12-05  6:03     ` Gary Thomas
2016-12-05 16:50       ` Khem Raj
2016-12-06 15:29         ` Andrei Gherzan
2016-12-06 18:04           ` ***SPAM*** " Herve Jourdain
2016-12-06 18:11             ` Andrei Gherzan [this message]
2016-12-06 21:21               ` Herve Jourdain
2016-12-06 23:00                 ` Paul Barker
2016-12-07  2:17                   ` Trevor Woerner
2016-12-07  7:25                     ` Paul Barker
2016-12-07  7:42                       ` Paul Barker
2016-12-07 10:54                         ` Andreas Müller
2016-12-06 22:50           ` Paul Barker
2016-12-07 15:19           ` Andrea Galbusera
2016-12-07 15:23             ` Andrei Gherzan
2016-12-03 20:18 ` Herve Jourdain
2016-12-06 21:32 ` Trevor Woerner

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=20161206181110.GG1636@carbonA \
    --to=andrei@gherzan.ro \
    --cc=gary@mlbassoc.com \
    --cc=herve.jourdain@neuf.fr \
    --cc=yocto@yoctoproject.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.