All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Richard Purdie" <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	Taras Kondratiuk <takondra@cisco.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	 "xe-linux-external(mailer list)" <xe-linux-external@cisco.com>,
	Martin Jansa <Martin.Jansa@gmail.com>
Subject: Re: [OE-core] [RFC PATCH] devtool: remove _PYTHON_SYSCONFIGDATA_NAME to fix do_unpack
Date: Fri, 10 Jul 2020 22:16:36 +0100	[thread overview]
Message-ID: <231f7c8e83cea1ef2d99bc6c40fb7b089192180b.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj9sJAaPdPQ2yPkN5iPBiUA9jNQ4qLSvbhxGGXja2oTR-A@mail.gmail.com>

On Fri, 2020-07-10 at 22:41 +0200, Alexander Kanavin wrote:
> I am able to do 'devtool modify gpgme' without any errors. In what
> setting does it fail for you?
> 
> The purpose of _sysconfigdata is to substitute configuration values
> that are specific for target python when running native python in
> cross builds with requests from target component build systems to
> supply those values. For that to work, the recipe also needs to have
> target python3 in its DEPENDS. It 
> 
> I feel the patch is fixing the symptom rather than the issue somehow?

We've had other patches like this and were playing "whack-a-mole" since
as soon as one merged, an issue appeared somewhere else. In the end I
stopped taking them and asked the issue be debugged and fixed properly.
There should be more info in the archives about what I suggested/asked
for to move forward with this...

Cheers,

Richard


  reply	other threads:[~2020-07-10 21:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-10 19:08 [RFC PATCH] devtool: remove _PYTHON_SYSCONFIGDATA_NAME to fix do_unpack Taras Kondratiuk
2020-07-10 20:41 ` Alexander Kanavin
2020-07-10 21:16   ` Richard Purdie [this message]
2020-07-11  1:31     ` [OE-core] " Taras Kondratiuk
2020-07-10 22:02   ` Taras Kondratiuk
2020-07-10 22:41     ` Alexander Kanavin
2020-07-11  0:58       ` Taras Kondratiuk
2020-07-11  7:42         ` Alexander Kanavin
2020-07-14  1:47           ` Taras Kondratiuk
2020-07-14  8:35             ` Alexander Kanavin
2020-07-15 19:07               ` Taras Kondratiuk

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=231f7c8e83cea1ef2d99bc6c40fb7b089192180b.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=Martin.Jansa@gmail.com \
    --cc=alex.kanavin@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=takondra@cisco.com \
    --cc=xe-linux-external@cisco.com \
    /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.