[arch-dev-public] removing cryptsetup from base group
Hi, this package brings in our clean chroots libgcrypt dependency. Until recently, gnutls had libcrypt as dependency but now it relies on nettle. That means that packages linked to gnutls and relied on libgcrypt dependency from it, will be broken. We have a gnutls 3.0.0 rebuild in progress in staging and because libgcrypt is in our clean chroots, everything is fine, functionality wise but I noticed that we skipped adding ligcrypt to dependency mostly because namcap and us assume that everybody have base group installed. Please check your packages to see if they link to libgcrypt and add it to dependency if they do. -- Ionuț
Am 09.08.2011 14:37, schrieb Ionut Biru:
Hi,
this package brings in our clean chroots libgcrypt dependency.
Until recently, gnutls had libcrypt as dependency but now it relies on nettle. That means that packages linked to gnutls and relied on libgcrypt dependency from it, will be broken.
We have a gnutls 3.0.0 rebuild in progress in staging and because libgcrypt is in our clean chroots, everything is fine, functionality wise but I noticed that we skipped adding ligcrypt to dependency mostly because namcap and us assume that everybody have base group installed.
Please check your packages to see if they link to libgcrypt and add it to dependency if they do.
Hm, -1 for now. AIF needs to become aware of it first, so it can auto-select cryptsetup when encrypted partitions are created.
On Tue, 09 Aug 2011 20:55:01 +0200 Thomas Bächler <thomas@archlinux.org> wrote:
Am 09.08.2011 14:37, schrieb Ionut Biru:
Hi,
this package brings in our clean chroots libgcrypt dependency.
Until recently, gnutls had libcrypt as dependency but now it relies on nettle. That means that packages linked to gnutls and relied on libgcrypt dependency from it, will be broken.
We have a gnutls 3.0.0 rebuild in progress in staging and because libgcrypt is in our clean chroots, everything is fine, functionality wise but I noticed that we skipped adding ligcrypt to dependency mostly because namcap and us assume that everybody have base group installed.
Please check your packages to see if they link to libgcrypt and add it to dependency if they do.
Hm, -1 for now. AIF needs to become aware of it first, so it can auto-select cryptsetup when encrypted partitions are created.
I just checked this, apparently aif already deals with it. (see how filesystem_pkg is used, all those packages are tracked when needed, none of them needs to be in base http://projects.archlinux.org/aif.git/tree/src/core/libs/lib-blockdevices-fi... ) Dieter
participants (3)
-
Dieter Plaetinck
-
Ionut Biru
-
Thomas Bächler