From: daid kahl <daidxor@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Migration to baselayout2 / openrc
Date: Wed, 14 Oct 2009 21:34:08 +0900 [thread overview]
Message-ID: <3ac129340910140534ic5dc918n1e5232a27488dcdd@mail.gmail.com> (raw)
In-Reply-To: <20091010100119.GA5805@solfire>
>
> Hi,
>
> for this weekend I planned to migrate to baselayout 2
> finally.
>
> On gentoo web I found this: 2.
> Migration to OpenRC
> Migration to OpenRC is fairly straightforward; it will be pulled in
> as part of your regular upgrade process by your package manager.
>
> I tried to check this (emerge -pv openrc) and found:
> !!! All ebuilds that could satisfy "sys-apps/openrc" have been masked.
> !!! One of the following masked packages is required to complete your request:
> - sys-apps/openrc-9999 (masked by: missing keyword)
> - sys-apps/openrc-0.5.1 (masked by: ~x86 keyword)
> - sys-apps/openrc-0.4.3-r4 (masked by: ~x86 keyword)
> - sys-apps/openrc-0.4.3-r3 (masked by: ~x86 keyword)
> - sys-apps/openrc-0.4.3-r2 (masked by: ~x86 keyword)
> - sys-apps/openrc-0.4.3-r1 (masked by: ~x86 keyword)
> - sys-apps/openrc-0.4.2 (masked by: ~x86 keyword)
> - sys-apps/openrc-0.4.1-r1 (masked by: ~x86 keyword)
>
> Especially "masked by: missing keyword" let me doubt whether
> or not it is sane to migrate....
>
> How to proceed here ?
>
I had originally migrated an entirely ~x86 system. Then I downgraded
almost all of the system, except for openrc & co because it was enough
work to upgrade, so I didn't want to downgrade to x86 and then
eventually openrc migrate again.
For the most part, the Gentoo Baselayout and OpenRC migration Guide is fine.
You can see my package.keywords for openrc on an otherwise stable
system below. I leave in some garbage comments since it might give
you an idea what I toyed around with.
#Dependencies to keep openrc with otherwise ARCH=x86
#<=sys-apps/openrc-0.4.3-r3 ~x86
<=sys-apps/openrc-0.4.1-r1 ~x86
<=sys-apps/baselayout-2.0.0 ~x86
#<=sys-fs/udev-145 ~x86
<=sys-apps/sysvinit-2.86-r12 ~x86
#<=sys-devel/libtool-2.2.4 ~x86
#<=sys-fs/e2fsprogs-1.41.8 ~x86
#<=sys-libs/e2fsprogs-libs-1.41.8 ~x86
<=sys-apps/sysvinit-2.86 ~x86
<=sys-fs/cryptsetup-1.0.6-r2 ~x86
# udev-145 messes up libvolume_id (see bug 281632)
#<=sys-apps/hal-0.5.13-r2 ~x86
#<=sys-apps/util-linux-2.16-r1 ~x86
Regards,
daid
prev parent reply other threads:[~2009-10-14 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-10 10:01 [gentoo-user] Migration to baselayout2 / openrc meino.cramer
2009-10-10 10:55 ` Mick
2009-10-10 11:43 ` Alan McKinnon
2009-10-10 12:16 ` Mike Kazantsev
2009-10-12 5:33 ` Eray Aslan
2009-10-12 8:14 ` Dale
2009-10-12 12:41 ` Momesso Andrea
2009-10-14 12:34 ` daid kahl [this message]
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=3ac129340910140534ic5dc918n1e5232a27488dcdd@mail.gmail.com \
--to=daidxor@gmail.com \
--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