From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Where can I find "recent" qemu out-of-tree ebuild
Date: Thu, 26 Oct 2017 12:18:41 -0400 [thread overview]
Message-ID: <20171026161841.GA30841@waltdnes.org> (raw)
In-Reply-To: <CAGfcS_n=uinhqV9QxK94-RTqHBQQ4fFsa-mWCpAvKGUQOD+jMQ@mail.gmail.com>
On Thu, Oct 26, 2017 at 06:55:45AM -0700, Rich Freeman wrote
> This should work:
> git clone git://anongit.gentoo.org/repo/gentoo.git .
> git checkout 4716c9ae8666e4cfc6eff46960f7bff8f4f3d708.
That worked, thanks. Now on to the next problem. I ran repoman, and
got a whole slew of errors. I stripped down the KEYWORDS line to
"amd64" in both ebuilds, but repoman is still getting errors. I am
*NOT* running "hardened" or "selinux"...
========================================================================
RepoMan scours the neighborhood...
>>> Creating Manifest for /usr/local/portage/app-emulation/qemu
dependency.bad [fatal] 8
app-emulation/qemu/qemu-2.9.0-r2.ebuild: RDEPEND: amd64(hardened/linux/amd64/no-multilib/selinux)
['sec-policy/selinux-qemu']
app-emulation/qemu/qemu-2.9.0-r2.ebuild: RDEPEND: amd64(hardened/linux/amd64/no-multilib/selinux)
['sec-policy/selinux-qemu']
app-emulation/qemu/qemu-2.9.0-r2.ebuild: RDEPEND: amd64(hardened/linux/amd64/selinux)
['sec-policy/selinux-qemu']
app-emulation/qemu/qemu-2.9.0-r2.ebuild: RDEPEND: amd64(hardened/linux/amd64/selinux)
['sec-policy/selinux-qemu']
app-emulation/qemu/qemu-2.9.0-r55.ebuild: RDEPEND: amd64(hardened/linux/amd64/no-multilib/selinux)
['sec-policy/selinux-qemu']
app-emulation/qemu/qemu-2.9.0-r55.ebuild: RDEPEND: amd64(hardened/linux/amd64/no-multilib/selinux)
['sec-policy/selinux-qemu']
app-emulation/qemu/qemu-2.9.0-r55.ebuild: RDEPEND: amd64(hardened/linux/amd64/selinux)
['sec-policy/selinux-qemu']
app-emulation/qemu/qemu-2.9.0-r55.ebuild: RDEPEND: amd64(hardened/linux/amd64/selinux)
['sec-policy/selinux-qemu']
ebuild.minorsyn 1
app-emulation/qemu/qemu-2.9.0-r55.ebuild: Useless blank line on line: 210
Note: use --include-dev (-d) to check dependencies for 'dev' profiles
Please fix these important QA issues first.
RepoMan sez: "Make your QA payment on time and you'll never see the likes of me."
========================================================================
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
next prev parent reply other threads:[~2017-10-26 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 1:24 [gentoo-user] Where can I find "recent" qemu out-of-tree ebuild Walter Dnes
2017-10-26 1:51 ` Michael Orlitzky
2017-10-26 3:15 ` Walter Dnes
2017-10-26 4:54 ` Walter Dnes
2017-10-26 11:40 ` Rich Freeman
2017-10-26 13:28 ` Walter Dnes
2017-10-26 13:55 ` Rich Freeman
2017-10-26 16:18 ` Walter Dnes [this message]
2017-10-26 16:35 ` Rich Freeman
2017-10-26 22:29 ` [gentoo-user] [SOLVED] " Walter Dnes
2017-10-26 1:58 ` [gentoo-user] " Lucas Ramage
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=20171026161841.GA30841@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox