All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/1] bblayers sanity: bblayers.conf.sample specific update code
Date: Tue, 13 Jun 2017 09:41:44 +0200	[thread overview]
Message-ID: <1497339704.30163.334.camel@intel.com> (raw)
In-Reply-To: <cover.6a3be6133a9172fdd3e435528c8d98c4be1d9dd1.1496069310.git-series.patrick.ohly@intel.com>

Ping?

On Mon, 2017-05-29 at 16:49 +0200, Patrick Ohly wrote:
> In an experimental branch of refkit I bumped LCONF_VERSION from 4 to 5
> and ran into the problem mentioned in the commit message: instead of
> raising an error as before, the code (incorrectly) claimed to have
> updated the bblayers.conf file.
> 
> Perhaps refkit should have started with LCONF_VERSION as in the
> current OE-core bblayers.conf.sample file to avoid being affected by
> this - too late for that now, though.
> 
> As an ugly workaround I'm currently jumping from 4 to 8 directly,
> which produces some extra (and wrong) output about "automatically
> updated" before finally raising the expected error (twice, for some
> reasons).
> 
> I'm not sure how this code was meant to work for different distros
> based on OE-core. Depending on when a distro forked from OE-core and
> how it continued with numbering its bblayers.conf.sample file, there
> must have been such conflicts already before.
> 
> Note that I have only checked that the code gets called when placed in
> the expected location, and the code itself was copied verbatim. As it
> refers to ancient changes, I've not actually tried to set up a build
> dir where that upgrade path is necessary. Perhaps the code could even
> be removed entirely?
> 
> Patrick Ohly (1):
>   bblayers sanity: bblayers.conf.sample specific update code
> 
>  meta/classes/sanity.bbclass               | 121 ++++-------------------
>  meta/conf/lib/bblayers_update/__init__.py | 104 ++++++++++++++++++++-
>  2 files changed, 130 insertions(+), 95 deletions(-)
>  create mode 100644 meta/conf/lib/bblayers_update/__init__.py
> 
> base-commit: ccf630e78aad488da7b80f2981037d3d0559cfad




      parent reply	other threads:[~2017-06-13  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-29 14:49 [PATCH 0/1] bblayers sanity: bblayers.conf.sample specific update code Patrick Ohly
2017-05-29 14:49 ` [PATCH 1/1] " Patrick Ohly
2017-06-13  7:41 ` Patrick Ohly [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=1497339704.30163.334.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=openembedded-core@lists.openembedded.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.