All of lore.kernel.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 07:49:02 -0500	[thread overview]
Message-ID: <f602be74-9ed6-ceed-0a94-e1486f956add@linux.intel.com> (raw)
In-Reply-To: <1fc0defa-748a-bff4-2f72-7bc0d0f160d9@linux.intel.com>



On 06/08/2017 06:31 AM, Alexander Kanavin wrote:
> On 06/07/2017 08:31 PM, Jose Perez Carranza wrote:
>> When I tried this test image was built without using states hence
>> "busybox*.rpm" and "curl*.rpm"where present under
>> "tmp/deploy/rpm/core2_64" hence the repo i taking tha packages form
>> there to add them to repo and used on the image, but when using sstates
>> those packages are not being built so are not present on local build
>> directory. is there any way to force those packages to be built to have
>> them available on tmp/deploy/rpm/core2_64?
>
> I can try to help if you provide steps to reproduce: if I merely do
>
> rm -rf build/tmp
> bitbake core-image-sato
>
> then the build/tmp/deploy/rpm directory gets fully re-populated.
>
Sure I'm using this branch [1]

The steps that Iḿ following are :

1. bitbake core-image-sato using shared states (I'm using local sstates)
2. Add to the local.conf
         INHERIT += "testimage"
         TEST_SUITES += " ping ssh dnf"
3. bitbake core-image-sato -c testimage

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=jperez/dnf-updates
>
> Alex
>

-- 
Saludos
José



  reply	other threads:[~2017-06-08 12:46 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 [this message]
2017-06-08 12:49                 ` Alexander Kanavin
2017-06-08 13:11                   ` Jose Perez Carranza
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=f602be74-9ed6-ceed-0a94-e1486f956add@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 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.