Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] python-nose: Fixes python-unittest-native RPROVIDES error after upgrade
Date: Wed, 20 Jan 2016 10:48:07 -0600	[thread overview]
Message-ID: <569FBA47.4050907@linux.intel.com> (raw)
In-Reply-To: <CAJTo0LZE-_XMvYjANPYDJBoJ9-wNgxap7-k9EbzXrjxXTSZB3g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 636 bytes --]



On 01/20/2016 10:43 AM, Burton, Ross wrote:
>
> On 20 January 2016 at 16:33, Alejandro Hernandez 
> <alejandro.hernandez@linux.intel.com 
> <mailto:alejandro.hernandez@linux.intel.com>> wrote:
>
>     The python-nose upgrade to 1.3.7 required a new unittest runtime
>     dependency
>     after this, bitbake cant find a runtime provider for it when
>     trying to build
>     python-nose-native, this patch makes python-native RPROVIDES
>     python-unittest-native
>     to fix the issue.
>
>

I agree

> A more accurate shortlog would be "python-native also RPROVIDE 
> python-unittest-native".
>
> Ross


[-- Attachment #2: Type: text/html, Size: 2047 bytes --]

      reply	other threads:[~2016-01-20 16:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1453307585.git.alejandro.hernandez@linux.intel.com>
2016-01-20 16:33 ` [PATCH 1/1] python-nose: Fixes python-unittest-native RPROVIDES error after upgrade Alejandro Hernandez
2016-01-20 16:43   ` Burton, Ross
2016-01-20 16:48     ` 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=569FBA47.4050907@linux.intel.com \
    --to=alejandro.hernandez@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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