Re: aspell upgrade woes
Thomas Bushnell BSG <email@example.com> writes:
> So aspell changed the library name to libaspell15c2, which breaks all
> the existing packages that use libaspell.
> Was this really an ABI change in libaspell? If not, there was no
> reason to make the change as I understand it. Were high-severity bugs
> filed on all the packages that depend on the library, requesting
> My understanding was that this upgrade would *not* normally change
> library package names, so I'm wondering why this one did. The aspell
> changelog doesn't contain anything illuminating.
aspell (0.60.3-2) unstable; urgency=low
* debian/control: renamed libaspell15 to libaspell15c2 for the GCC 4.0
ABI change transition
Society is never going to make any progress until we all learn to
pretend to like each other.