reopen 621169 quit On Tue, 26 Apr 2011 19:52:28 +0200 Patrick Matthäi <pmatth...@debian.org> wrote:
> Hi I am closing this bug. > The gluster libs are just for internal usage. Nevertheless, libglusterfs-dev_3.1.3-1_amd64.deb contains libgfxdr.la which is installed into /usr/lib/ and which contains values in dependency_libs: # Libraries that this one depends upon. dependency_libs=' /usr/lib/libgfrpc.la /usr/lib/libglusterfs.la -lfl -ldl -lpthread' That line needs to be cleared out (exactly as per the MBF) and this action does not affect "internal usage" of the library. There may well be others in the binary packages build from this source, but this one, alone, is sufficient to reopen this bug. "internal usage" is not a valid reason to close this bug. > > In most cases, the .la file(s) can simply be removed as the process > > behind this MBF has already identified that there are no further > > dependencies using the .la file. In the unusual case that your > > package uses libltdl directly, it is still necessary to empty the > > dependency_libs part of all .la files remaining in the package. Once > > glusterfs is fixed, the process will repeat and other packages which > > you maintain may need to be fixed in turn. It is important that > > packages are fixed in sequence to avoid FTBFS bugs. If you have plugins which use the .la file(s) then those will still work because you can retain the .la file - just without the dependency_libs value which is only used for re-linking, not at runtime. Feel free to discuss this further if you have queries but closing this bug without changes in the package is not sufficient. -- Neil Williams ============= http://www.linux.codehelp.co.uk/
pgpVw2qT9alSP.pgp
Description: PGP signature
