severity 307481 normal thanks On Tue, May 03, 2005 at 09:43:09AM -0400, James Aspnes wrote: > Upgrading to the most recent version of aspell-bin fixed the problem. > So there may be a missing dependency issue but otherwise this doesn't > seem to be a bug.
Ugh. The soname of libaspell15 did not change from 0.50 -> 0.60, but maybe it should have. Although the external API/ABI did not change, the 'aspell' binary uses internal library symbols that did change. The only thing I could do at this time is make the current libaspell15 conflict with aspell-bin (<< 0.60), but that's pretty clumsy. Fortunately, it's not a release crtical bug since it does not affect woody -> sarge partial upgrades (woody doesn't have libaspell15). A better solution for the future is probably to make aspell-bin depend on the exact same version of libaspell15, instead of relying on shlibs to do a >= dependency. -- Society is never going to make any progress until we all learn to pretend to like each other. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
