From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Jose Perez Carranza <jose.perez.carranza@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: Fri, 9 Jun 2017 12:22:03 +0300 [thread overview]
Message-ID: <77fb98df-ff8a-c3d7-c995-7c8de3c4cf3d@linux.intel.com> (raw)
In-Reply-To: <f3d6469c-b0a8-6f75-7c02-e8afd0cf04bd@linux.intel.com>
On 06/08/2017 07:35 PM, Alexander Kanavin wrote:
> I haven't been able to reproduce the installroot failure, works fine here.
The installroot issue is most likely due to dnf architectures not being
properly configured (which causes breakage when the architecture is not
one of the standard ones that the upstream has hardcoded). Yes, the
error message is unhelpful and leads one to think the repo is somehow
broken or is missing packages :)
Copy the contents of /etc/rpm and /etc/dnf into installroot dir before
running dnf, and you should be good to go. Test on x32, for example.
Alex
next prev parent reply other threads:[~2017-06-09 9:22 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
2017-06-08 16:35 ` Alexander Kanavin
2017-06-09 9:22 ` Alexander Kanavin [this message]
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=77fb98df-ff8a-c3d7-c995-7c8de3c4cf3d@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=jose.perez.carranza@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