-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
lo,
On Thursday 12 January 2006 16:45, Doug Goldstein wrote:
> AFAIK, cryptsetup should be pulled in favor of cryptsetup-luks. I think
> everything uses luks now rather then cryptsetup.
I know that the latest versions of gnome now are using cryptsetu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
lo,
On Thursday 12 January 2006 17:17, Chris Gianelloni wrote:
> On Thu, 2006-01-12 at 11:45 -0500, Doug Goldstein wrote:
> > AFAIK, cryptsetup should be pulled in favor of cryptsetup-luks. I think
> > everything uses luks now rather then cryptsetup.
On Thu, 2006-01-12 at 11:45 -0500, Doug Goldstein wrote:
> AFAIK, cryptsetup should be pulled in favor of cryptsetup-luks. I think
> everything uses luks now rather then cryptsetup.
We're still using cryptsetup on the InstallCD/LiveCD. Should we switch?
What's the differences?
--
Chris Gianello
Henrik Brix Andersen wrote:
> Hi,
>
> As stated in bug #74396, all ebuilds using kernel-mod.eclass must be
> converted to using either linux-mod.eclass and/or linux-info.eclass.
>
> The bug has been open since 2004-12-14, yet there are still ebuilds in
> the tree which inherits kernel-mod.eclass:
Hi,
As stated in bug #74396, all ebuilds using kernel-mod.eclass must be
converted to using either linux-mod.eclass and/or linux-info.eclass.
The bug has been open since 2004-12-14, yet there are still ebuilds in
the tree which inherits kernel-mod.eclass:
$ find . -name "*.ebuild"|xargs grep inh
