On Thu, Mar 29, 2012 at 11:58:17AM +0200, Sebastian Pipping wrote:
| With that bug fixed by now is there still need for a news entry?
I don't think I make that call, but if the current plastering-over would
generally keep existing setups from breaking, I'm happier.
On 03/30/2012 10:56 AM, Amadeusz Żołnowski wrote:
Excerpts from Samuli Suominen's message of 2012-03-29 19:59:17 +0200:
I've been told dracut is able to handle this. Unverified.
Dracut doesn't need anything built static.
Thanks for verifying. Expected nothing less. I've reopened the bug[1]
Excerpts from Samuli Suominen's message of 2012-03-29 19:59:17 +0200:
> I've been told dracut is able to handle this. Unverified.
Dracut doesn't need anything built static.
--
Amadeusz Żołnowski
signature.asc
Description: PGP signature
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.or
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 f
On Thu, Mar 22, 2012 at 15:48, wrote:
> Please - if you're going to significantly change functionality that
> (whether correct or not) people have come to depend on, have the decency
> to at least publish a news article on it.
Previous stable cryptsetup had an "if use dynamic" warning in
pkg_set
On Thu, 2012-03-22 at 07:48 -0600, sch...@subverted.org wrote:
> Normally I don't take to the skies with this sort of thing, but this was
> ridiculous. In what I am sure was a well-intentioned change, cryptsetup
> recently silently lost its default USE=static status. For one of the
> many people
Normally I don't take to the skies with this sort of thing, but this was
ridiculous. In what I am sure was a well-intentioned change, cryptsetup
recently silently lost its default USE=static status. For one of the
many people actually using cryptsetup in an initrd, this came as a
lovely surprise
