From: Samuli Suominen <ssuominen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Arbitrary breakage: sys-fs/cryptsetup
Date: Thu, 29 Mar 2012 20:59:17 +0300 [thread overview]
Message-ID: <4F74A2F5.5010603@gentoo.org> (raw)
In-Reply-To: <4F743239.9010103@gentoo.org>
On 03/29/2012 12:58 PM, Sebastian Pipping wrote:
> On 03/22/2012 03:20 PM, Alexandre Rostovtsev wrote:
>>> [1] For one, genkernel should bomb out if it can't comply with a
>>> command-line arg instead of just putting non-alert text up.
>>
>> There is already a bug open about this issue:
>> https://bugs.gentoo.org/show_bug.cgi?id=409277
>
> With that bug fixed by now is there still need for a news entry?
>
> Best,
>
>
>
> Sebastian
>
It doesn't look fixed to me, only temporarily worked around to force USE
static on cryptsetup.
Should be kept open until genkernel is fixed to generate the initramfs
in a way it doesn't need the static cryptsetup.
I've been told dracut is able to handle this. Unverified.
- Samuli
next prev parent reply other threads:[~2012-03-29 18:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 13:48 [gentoo-dev] Arbitrary breakage: sys-fs/cryptsetup schism
2012-03-22 14:20 ` Maxim Kammerer
2012-03-22 14:20 ` Alexandre Rostovtsev
2012-03-29 9:58 ` Sebastian Pipping
2012-03-29 17:59 ` Samuli Suominen [this message]
2012-03-30 7:56 ` Amadeusz Żołnowski
2012-03-30 8:05 ` Samuli Suominen
2012-04-02 0:49 ` schism
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=4F74A2F5.5010603@gentoo.org \
--to=ssuominen@gentoo.org \
--cc=gentoo-dev@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