Red Hat Bugzilla – Full Text Bug Listing
|Summary:||binary in /sbin links with libs in /usr/lib|
|Product:||[Fedora] Fedora||Reporter:||Jeremy Katz <katzj>|
|Component:||cryptsetup-luks||Assignee:||Till Maas <opensource>|
|Status:||CLOSED RAWHIDE||QA Contact:|
|Version:||rawhide||CC:||agk, dwysocha, mbroz, mgarski, opensource, pjones, prockai|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2007-08-24 06:54:31 EDT||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Bug Depends On:||249814, 249815, 249816|
Description Jeremy Katz 2007-06-07 22:11:47 EDT
This will break things using /etc/crypttab and a separate /usr
Comment 1 Till Maas 2007-07-26 13:46:44 EDT
Cryptsetup-luks in Fedora 7 and before were build statically, this changed with 1.0.3-5 in rawhide. I do not know why this changed, but I guess we should either put the following libraries into /lib libpopt.so.0 => /usr/lib/libpopt.so.0 (0x0012e000) libcryptsetup.so.0 => /usr/lib/libcryptsetup.so.0 (0x00136000) libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0x001b5000) libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x47d8f000) or go back to building it statically. This not only breaks existing installations, but also blocks Bug #124789 (encrypted root support). There was also a bug report for cryptsetup to build it statically: #129926, which was closed a long time ago.
Comment 2 Till Maas 2007-07-26 18:55:36 EDT
I commited the necessary changes to cvs to build it statically again, there is a scratch build available: http://koji.fedoraproject.org/koji/taskinfo?taskID=78776
Comment 3 Jeremy Katz 2007-07-26 19:42:32 EDT
Static linking isn't the right answer, though, and is explicitly disallowed per the packaging guidelines. The fact that it's needed in early boot isn't a reason to link it statically; instead, it's a reason to get libraries moved to /lib.
Comment 4 Till Maas 2007-07-27 04:52:21 EDT
(In reply to comment #3) > Static linking isn't the right answer, though, and is explicitly disallowed per > the packaging guidelines. The fact that it's needed in early boot isn't a > reason to link it statically; instead, it's a reason to get libraries moved to > /lib. I have commited to cvs a change that moves the cryptsetup libraries to /lib. Here is a list of the packages that need to move their libraries to /lib: /usr/lib/libgcrypt.so.11 -> libgcrypt /usr/lib/libpopt.so.0 -> popt (rpm) /usr/lib/libgpg-error.so.0 -> libgpg-error
Comment 5 Till Maas 2007-07-27 10:23:37 EDT
cryptsetup-luks-1_0_5-2_fc8 is built dynamically and puts libcryptsetup into /lib, too.
Comment 6 Robert Scheck 2007-08-23 19:12:54 EDT
popt-1.12-3 will provide the files /lib/libpopt.so.0 and /lib/libpopt.so.0.0.0 once it reached Rawhide.
Comment 7 Till Maas 2007-08-24 06:54:31 EDT
All "depends on" bugs are closed, so this can be closed, too.