Comment 1 for bug 1013203

Thank you for taking the time to report this bug and helping to make Ubuntu better.

The Unix standard is for applications to always link to libraries with a name that includes the major version number, so that multiple versions (ie. ABIs) of the same library can co-exist. rampart appears to be doing this correctly.

Symlinks without a major version number (such as /usr/lib/libmod_rampart.so) are only used for development and build, so that there is a default ABI to link against. On Debian and Ubuntu, the standard is to provide these through the -dev package that corresponds to the library. Here, this is the librampart-dev package, and again this appears to be correct.

If the Eucalyptus requires libmod_rampart.so at runtime, then this is a bug in Eucalyptus, not in rampart. Eucalyptus should be using librampart.so.0, etc. at runtime, so that a future librampart.so.1 can co-exist without breaking it.

To fix the problem, please can you tell us what Eucalyptus is doing, what it needs, and if this is a bug in packaging or if it can be fixed upstream?

I'm marking the bug in rampart as Invalid in rampart as its library symlinks are correct (verified in Quantal). I'm marking the bug in eucalyptus as Incomplete, pending further information on what Eucalyptus needs or what it is doing. Once you provide further information, please change the bug status for the eucalyptus task back to New.