Hi, the problem is that some packages try to use the installed versions of their own shared libraries or tools during the build process. In the past I've worked around this by
- linking (ln -s) from the old library file to the new one - 'make replace'ing the package in question to be sure: - delete the symlink - 'make replace' again then: - continue with pkg_rolling-replace I think you can, if pressed on time and this happens a lot for a particular .so, just create the symlink, let pkg_rolling-replace run through, then delete it. Not sure if this whole thing is a bug and if so, where. Best, Matthias
