From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/3] Restructure python2 and python3 packaging system
Date: Wed, 23 Aug 2017 14:46:21 +0100 [thread overview]
Message-ID: <1503495981.32591.159.camel@linuxfoundation.org> (raw)
In-Reply-To: <cover.1502989095.git.alejandro.hernandez@linux.intel.com>
On Thu, 2017-08-17 at 10:11 -0700, Alejandro Hernandez wrote:
> Alejandro Hernandez (3):
> python: Restructure python packaging and replace it with
> autopackaging
> python3: fix RDEPENDS on several recipes, due to non-existent
> python3
> packages
> python3: Restructure python3 packaging and replace it with
> autopackaging
There was an issue exposed on the autobuilder from this patchset which
then highlighted problems with the incorrect PACKAGES_DYNAMIC use and
issues with the lack of a native manifest.
With M3 being now and this change potentially causing issues for other
layers, I've deferred this patch series for now as I don't think its
ready yet and I don't think it will be ready in a timeframe that can
make it into M3.
Cheers,
Richard
prev parent reply other threads:[~2017-08-23 13:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 17:11 [PATCH 0/3] Restructure python2 and python3 packaging system Alejandro Hernandez
2017-08-17 17:11 ` [PATCH 1/3] python: Restructure python packaging and replace it with autopackaging Alejandro Hernandez
2017-08-17 17:11 ` [PATCH 2/3] python3: fix RDEPENDS on several recipes, due to non-existent python3 packages Alejandro Hernandez
2017-08-17 17:11 ` [PATCH 3/3] python3: Restructure python3 packaging and replace it with autopackaging Alejandro Hernandez
2017-08-17 17:35 ` ✗ patchtest: failure for Restructure python2 and python3 packaging system Patchwork
2017-08-17 19:15 ` Alejandro Hernandez
2017-08-18 9:35 ` [PATCH 0/3] " Alexander Kanavin
2017-08-18 10:23 ` Richard Purdie
2017-08-18 11:33 ` Richard Purdie
2017-08-18 11:37 ` Richard Purdie
2017-08-23 13:46 ` Richard Purdie [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=1503495981.32591.159.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alejandro.hernandez@linux.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.