Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCHv2] dnf: move the entire dnf/rpm4 stack to Python 3
Date: Mon, 27 Mar 2017 14:41:32 +0100	[thread overview]
Message-ID: <1490622092.13980.266.camel@linuxfoundation.org> (raw)
In-Reply-To: <5eab5be9-580f-d869-f7c0-b32d3e30daf3@linux.intel.com>

On Mon, 2017-03-27 at 15:19 +0300, Alexander Kanavin wrote:
> On 03/25/2017 07:56 PM, Richard Purdie wrote:
> > 
> > > 
> > > [YOCTO #11180]
> > So close but:
> > 
> > https://autobuilder.yocto.io/builders/nightly-multilib/builds/226
> > https://autobuilder.yocto.io/builders/nightly-x32/builds/206
> This is actually a bug in our target Python 3 installation. No idea
> how 
> it went unnoticed - does no one use Python 3 on target with multilib
> or 
> x32 at all?
> 
> 
> Python 3.5.2 (default, Mar 27 2017, 11:43:41)
> [GCC 6.3.0] on linux
> Type "help", "copyright", "credits" or "license" for more
> information.
>  >>> import site
>  >>> site.getsitepackages()
> ['/usr/lib/python3.5/site-packages']
>         ^^^ !!!

Highlights we need better testing, thanks for fixing it!

Cheers,

Richard


      reply	other threads:[~2017-03-27 13:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 21:08 [PATCHv2] dnf: move the entire dnf/rpm4 stack to Python 3 Alexander Kanavin
2017-03-25 17:56 ` Richard Purdie
2017-03-27 12:19   ` Alexander Kanavin
2017-03-27 13:41     ` 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=1490622092.13980.266.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alexander.kanavin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox