public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Jose Perez Carranza <jose.perez.carranza@linux.intel.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>,
	"Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v3] runtime/dnf: Add new dnf test cases
Date: Thu, 8 Jun 2017 08:11:21 -0500	[thread overview]
Message-ID: <ffb7b2ad-adad-fa79-b01f-ae48f9f81195@linux.intel.com> (raw)
In-Reply-To: <3e99ba6b-5841-dbe3-b44b-25ffe906f04f@linux.intel.com>



On 06/08/2017 07:49 AM, Alexander Kanavin wrote:
> On 06/08/2017 03:49 PM, Jose Perez Carranza wrote:
>
>> 1. bitbake core-image-sato using shared states (I'm using local sstates)
>
> When you do this, tmp/deploy/rpm should get re-populated with rpm 
> packages, regardless of whether they're taken from sstate, or rebuilt.
All those steps are done on a fresh build directory, so the first time 
that image is built packages are not being populated when rebuilding the 
image packages are get pupulated, but AB only built once the image and 
then execute testimage.
>
> Can you check why this does not happen on your side?
>
> Alex

-- 
Saludos
José



  reply	other threads:[~2017-06-08 13:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 19:38 [PATCH] runtime/dnf: Add new dnf test cases jose.perez.carranza
2017-05-10 19:52 ` Alexander Kanavin
2017-05-11 17:33   ` [PATCH v2] " jose.perez.carranza
2017-05-11 18:56     ` Alexander Kanavin
2017-05-11 19:21       ` Jose Perez Carranza
2017-05-15 13:50       ` [PATCH v3] " jose.perez.carranza
2017-06-07 10:21         ` Burton, Ross
2017-06-07 17:31           ` Jose Perez Carranza
2017-06-08 11:31             ` Alexander Kanavin
2017-06-08 12:49               ` Jose Perez Carranza
2017-06-08 12:49                 ` Alexander Kanavin
2017-06-08 13:11                   ` Jose Perez Carranza [this message]
2017-06-08 16:35             ` Alexander Kanavin
2017-06-09  9:22               ` Alexander Kanavin
2017-06-09 12:54                 ` Jose Perez Carranza
2017-06-13 19:56         ` [PATCH v4] " jose.perez.carranza
2017-06-14 12:00           ` Alexander Kanavin
2017-06-14 12:32             ` Jose Perez Carranza
2017-11-30 16:23               ` [PATCH v5] " jose.perez.carranza

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=ffb7b2ad-adad-fa79-b01f-ae48f9f81195@linux.intel.com \
    --to=jose.perez.carranza@linux.intel.com \
    --cc=alexander.kanavin@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