Bug 243228
| 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: | |
| Severity: | low | Docs Contact: | |
| Priority: | high | ||
| Version: | rawhide | CC: | agk, dwysocha, mbroz, mgarski, opensource, pjones, prockai |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-08-24 10:54:31 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 249814, 249815, 249816 | ||
| Bug Blocks: | 235704 | ||
|
Description
Jeremy Katz
2007-06-08 02:11:47 UTC
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.
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 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. (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 cryptsetup-luks-1_0_5-2_fc8 is built dynamically and puts libcryptsetup into /lib, too. popt-1.12-3 will provide the files /lib/libpopt.so.0 and /lib/libpopt.so.0.0.0 once it reached Rawhide. All "depends on" bugs are closed, so this can be closed, too. |