All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] python3-native: Fix pip install issue due to unclean build directory
Date: Mon, 20 Apr 2015 11:05:12 -0500	[thread overview]
Message-ID: <553523B8.8010002@linux.intel.com> (raw)
In-Reply-To: <1429429781.6976.217.camel@linuxfoundation.org>



On 19/04/15 02:49, Richard Purdie wrote:
> On Fri, 2015-04-17 at 19:19 -0500, Alejandro Hernandez wrote:
>> On 17/04/15 16:50, Richard Purdie wrote:
>>> On Thu, 2015-04-16 at 09:45 +0000, Alejandro Hernandez wrote:
>>>> When installing python3-native sometimes pips default build
>>>> directory (which is on the host and is user dependant) is left unclean,
>>>> due to this, when python3-core is being installed it tries to use
>>>> the same directory producing an error, this explicitly removes
>>>> what the previous installation might have left behind, fixing the issue.
>>>>
>>>> Signed-off-by: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
>>>> ---
>>>>    .../python/python3-native_3.4.2.bb                 |  1 +
>>>>    .../python3/pip_build_directory_unclean.patch      | 28 ++++++++++++++++++++++
>>>>    2 files changed, 29 insertions(+)
>>>>    create mode 100644 meta/recipes-devtools/python/python3/pip_build_directory_unclean.patch
> I tried it on the autobuilder and it failed again. I think part of the
> problem is that this part of the process runs under pseudo so it thinks
> its root, yet can't clear root's pip directory in /tmp.
>
> I suspect we are going to have to tell pip to use WORKDIR somehow, even
> if we have to patch it to take some kind of prompt from the environment
> for example.
>
> Cheers,
>
> Richard
>

Yes, the problem does happen when it uses pseudo and it thinks its root, 
I thought removing the files inside the same python code would be able 
to do it, ok I will find another workaround.



      reply	other threads:[~2015-04-20 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1429177203.git.alejandro.hernandez@linux.intel.com>
2015-04-16  9:45 ` [PATCH 1/1] python3-native: Fix pip install issue due to unclean build directory Alejandro Hernandez
2015-04-17 21:50   ` Richard Purdie
2015-04-18  0:19     ` Alejandro Hernandez
2015-04-19  7:49       ` Richard Purdie
2015-04-20 16:05         ` Alejandro Hernandez [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=553523B8.8010002@linux.intel.com \
    --to=alejandro.hernandez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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.