From: Zac Medico <zmedico@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Replace sys-apps/sysvinit with sys-apps/systemd[sysv-utils] in installcd-stage1.spec or installcd-stage2-minimal.spec
Date: Mon, 2 Jan 2017 13:09:42 -0800 [thread overview]
Message-ID: <100de3f7-831e-ab84-7cac-9f2f4f841852@gentoo.org> (raw)
In-Reply-To: <2859498.MH6ModozN9@99d44166af322fc16a4774097a5f271d>
On 12/18/2016 03:42 PM, anonymous0@openmailbox.org wrote:
> Good day, monks!
>
> I try to build installcd with systemd. So, I want to replace sys-apps/sysvinit with sys-apps/systemd[sysv-utils].
>
> Well, I tried my .spec file (derived from releng/releases/weekly/specs/amd64/installcd-stage1.spec). http://pastebin.com/zRzpYDAS
>
> Diff here http://pastebin.com/YenF9ypQ
>
> And I got error: http://pastebin.com/XgZNXFar
>
> How I can force installation of sys-apps/systemd[sysv-utils]?
In order to do that, you're going to have to eliminate openrc from the
dependency graph, since openrc pulls in sys-apps/sysvinit
unconditionally on linux. If you can repeat the emerge command with the
--tree option, then it should should reveal how openrc got pulled into
the dependency graph.
Troubleshooting dependency problems is off-topic for this list, maybe
forums.gentoo.org or the gentoo-user list would be better. Anyway, maybe
someone here can suggest a good way to add --tree to the emerge options
used by catalyst. I think adding this line to /etc/catalyst/catalystrc
might do it:
EMERGE_DEFAULT_OPTS="--tree"
--
Thanks,
Zac
next prev parent reply other threads:[~2017-01-02 21:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-18 23:42 [gentoo-catalyst] Replace sys-apps/sysvinit with sys-apps/systemd[sysv-utils] in installcd-stage1.spec or installcd-stage2-minimal.spec anonymous0
2017-01-02 13:14 ` anonymous0
2017-01-02 21:09 ` Zac Medico [this message]
2017-01-02 21:12 ` Zac Medico
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=100de3f7-831e-ab84-7cac-9f2f4f841852@gentoo.org \
--to=zmedico@gentoo.org \
--cc=gentoo-catalyst@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