From: "Denys Dmytriyenko" <denis@denix.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe] [meta-python][PATCH 0/2] remove pycryptodome(x) and pyelftools
Date: Mon, 18 May 2020 13:23:03 -0400 [thread overview]
Message-ID: <20200518172303.GL11927@denix.org> (raw)
In-Reply-To: <160F481530632D33.6323@lists.openembedded.org>
On Fri, May 15, 2020 at 02:47:26PM -0400, Denys Dmytriyenko wrote:
> On Fri, May 15, 2020 at 11:42:13AM -0700, Khem Raj wrote:
> >
> >
> > On 5/15/20 11:41 AM, Denys Dmytriyenko wrote:
> > >Joshua,
> > >
> > >FYI
> > >
> > >
> > >On Fri, May 15, 2020 at 02:39:38PM -0400, Denys Dmytriyenko wrote:
> > >>From: Denys Dmytriyenko <denys@ti.com>
> > >>
> > >>python3-pycryptodome(x) and python3-pyelftools have been moved to OE-Core.
> > >>Remove from meta-python now.
> > >>
> > >>OE-Core changes are still in master-next, so may need to wait until merged
> > >>to master.
> > >>
> >
> > thanks, if you are watching this please send a note once its in master.
>
> Sure, will do.
So, OE-Core master-next got merged to master earlier today, but I see you
already have these 2 in your master-next, so should be good. Thanks.
> > >>Denys Dmytriyenko (2):
> > >> python3-pycryptodome(x): moved to OE-Core, remove from meta-python
> > >> python3-pyelftools: moved to OE-Core, remove from meta-python
> > >>
> > >> .../python/python-pycryptodome.inc | 29 ----------------------
> > >> .../python/python3-pycryptodome_3.9.4.bb | 2 --
> > >> .../python/python3-pycryptodomex_3.9.4.bb | 10 --------
> > >> .../python/python3-pyelftools_0.25.bb | 14 -----------
> > >> 4 files changed, 55 deletions(-)
> > >> delete mode 100644 meta-python/recipes-devtools/python/python-pycryptodome.inc
> > >> delete mode 100644 meta-python/recipes-devtools/python/python3-pycryptodome_3.9.4.bb
> > >> delete mode 100644 meta-python/recipes-devtools/python/python3-pycryptodomex_3.9.4.bb
> > >> delete mode 100644 meta-python/recipes-devtools/python/python3-pyelftools_0.25.bb
> > >>
> > >>--
> > >>2.7.4
> > >>
> > >
> > >>
> > >
> > >
> > >
> > >
>
> >
>
>
next prev parent reply other threads:[~2020-05-18 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <160F47A92CF7AFC2.6323@lists.openembedded.org>
2020-05-15 18:41 ` [oe] [meta-python][PATCH 0/2] remove pycryptodome(x) and pyelftools Denys Dmytriyenko
2020-05-15 18:42 ` Khem Raj
2020-05-15 18:47 ` Denys Dmytriyenko
[not found] ` <160F481530632D33.6323@lists.openembedded.org>
2020-05-18 17:23 ` Denys Dmytriyenko [this message]
2020-05-18 17:47 ` Khem Raj
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=20200518172303.GL11927@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox