libhunspell-1.1-0 1.1.5-6: Incompatible ABI change

[Bryan Donlan]

Binary package hint: libhunspell-1.1-0

After upgrading libhunspell-1.1-0 from 1.1.4-7 to 1.1.5-6, firefox began crashing whenever I began entering text. On the console, this was emitted:
/usr/lib/firefox/firefox-bin: symbol lookup error: /usr/lib/firefox/components/libmyspell.so: undefined symbol: _ZN8Hunspell5spellEPKc

It seems that there was an incompatible ABI change, and thus the soname of the library must be changed (or the package name itself if that hasn't occured upstream).

[Emmet Hikory (persia)]

firefox rebuild is being processed as bug #107340.

openoffice.org doesn't appear to have an active bug, but needs a rebuild (and perhaps porting).

[Bryan Donlan (bdonlan)]

Shouldn't the name of the binary package be changed, and set to conflicts/replace the original, so as to prevent someone from unwittingly installing a bad combination of packages, and to help catch any packages which were missed in the transition?

[Emmet Hikory (persia)]

In general, yes. This early in the development cycle for gutsy, and with only two packages affected, I'm not sure if that step will be taken.

[Bryan Donlan (bdonlan)]

This package was in feisty, however, so it's not the same as if you had a new package introduced early in gutsy, then the ABI changed; or am I mistaken?

[Emmet Hikory (persia)]

The goal is to ensure that all released and supported pacakges can never reach an unstable state. When a large number of packages is affected, the name change and conflicts may be used (or a false soname bump) to ensure that there is no problem, and that no packages are missed. When a small number of packages is involved, sometimes the migration is handled without such changes. When upgrading to 7.10 from 7.04, updated libhunspell, firefox, and openoffice.org-core packages will all be delivered simultaneously, so that a user of either release should never encounter this situation.

I'm not sure you're mistaken, just that practice is sometimes different than theory. The final solution may well include a change to package names.

[Giedrius (giedrbac)]

OOo has same bug as firefox. OOo bug #112901. It is sort of duplicate, but I am not sure if it should be marked as such or not.

[Giedrius (giedrbac)]

Bug #112372 is also the same OOo bug. Sorry for the spam, forgot this one when adding last comment.

[Emmet Hikory (persia)]

This bug is for hunspell, which managed the transition differently than is preferred. Even if the transition was handled in an ideal manner, there would be bugs against firefox and OOo to be updated to link against the new library. This bug may be closed when any of the following conditions is met:

1) Both packages that depend on libhunspell have been build against linhunspell 1.1.5-6 or later
2) libhunspell is updated such that the old interface is used (and perhaps again updated with new binary names)
3) libhunspell is packaged to conflict with versions of dependent packages compiled against the old interface

[Emmet Hikory (persia)]

firefox 2.0.0.3+3-0ubuntu1 includes all necessary changes

[Christian Reis (kiko)]

Updating based on status of bug 107340. I added the tasks to this bug because this is the "right" way to monitor work that needs to happen across multiple packages to solve a single bug. I'm going to file a bug about making the adding of package tasks for a distro easier.

[Someone (s4910321931-deactivatedaccount)]

This very issue plaugud me with Thunderbird 2. I am running feisty and wanted a thunderbird 2.0 on my system. I added gutsy repos into the sources.lsit, added a default release into apt.conf and happily installed thunderbird 2.0. It upgraded libhunspell as a dependecy. And now oo crashes. So thunderbird is a third on the list of "small number of packages involved". Changing package names and/or handling a parrallel installation of this lib with two different versions for different application versions would help to track only a part of development release of Ubuntu.
Sorry, I cannot track the whole one, I am working on this system.
Thanks.

[John Vivirito (gnomefreak)]

Dennis using gutsy repos with feisty or any repo that is unofficial for your version of ubuntu is not supported nor is it ever recommended due to the very problem you are having. thunderbird 2 was not built and added into feisty for a few reasons, I cant say yet if it will ever make it into feisty in the backports repo as there has not been a date set when mozilla will stop support for the 1.5 branch. When they set a date we will talk about it.

[John Vivirito (gnomefreak)]

Why is this bug filed against libhunspell? the version of libhunspell is the correct version that will be in gutsy. The only thing that this bug is about is anything that depends on hunspell 1.1.5-6 needs to be respun/merged using build-depend on gutsys version of hunspell and that will happen during the devel process.

[John Vivirito (gnomefreak)]

thunderbird has been built using correct hunspell.

[Emilio Pozuelo Monfort (pochu)]

Closing hunspell task, since it's not a bug in it.

[Emilio Pozuelo Monfort (pochu)]

11:20 < persia> pochu: Why are you rejecting hunspell in bug 111940? The maintainer should have bumped the soname for the ABI change, no?

Looks like there _is_ a bug in hunspell too :)

[John Vivirito (gnomefreak)]

Yeah sorry about that i heard about this last week its the soname issue and afaik it hasnt been worked out yet.

[Alexander Sack (asac)]

debian hunspell soname is now in sync with upstream and i doubt that we want to change that for ubuntu alone. If we really want a soname bump we should probably ask hunspell upstream instead of debian and explain the situation to them.

 - Alexander

[Emmet Hikory (persia)]

Given the small size of this transition, working with upstream to generate a soname bump is not likely required: more important is coordination between affected packages to ensure that a stable system is released. This remains a bug in hunspell, as a changed ABI was released without a change to either the soname or the binary package name, but at this point the least painful solution is to wait for the next revison of openoffice.org, rather than adjusting hunspell (as otherwise, other libhunspell clients must again be rebuilt).

[Emilio Pozuelo Monfort (pochu)]

By the way, there is an OOo 2.2.1 RC1. Maybe it's worth to upload it, fixing this bug and testing that release candidate.

http://development.openoffice.org/releases/2.2.1rc1.html

[Wolf Halton (saphil)]

I have tried RC1 on my own box, and it says it can't run swriter bexause openoffice is not installed.

[Francesc Vicent (fransex)]

I guess that we will wait until 2.2.1, now it is in release candidate 2: http://development.openoffice.org/releases/2.2.1rc2.html

If you need OOo in gutsy, just install libhunspell 1.1.4 from feisty: http://launchpadlibrarian.net/5769050/libhunspell-1.1-0_1.1.4-7_i386.deb

[Francesc Vicent (fransex)]

(but in case you install libhunspell for feisty, you will not be able to use current firefox and thunderbird in gutsy)

[Anderson (amg1127)]

"(but in case you install libhunspell for feisty, you will not be able to use current firefox and thunderbird in gutsy)"

You are right.

A possible workaround is:

# wget http://launchpadlibrarian.net/5769050/libhunspell-1.1-0_1.1.4-7_i386.deb
# dpkg --extract libhunspell-1.1-0_1.1.4-7_i386.deb .
# cp usr/lib/libhunspell* /usr/lib/openoffice/program/

So only OpenOffice.org uses the old libhunspell.

[Emilio Pozuelo Monfort (pochu)]

Matthias has already merged OOo with Debian (OOo 2.2.1~rc3).

[Martin Pitt (pitti)]

we will rebuild things against the new hunspell and leave this as it is.

[Matthias Klose (doko)]

fixed in openoffice.org 2.2.1~rc3-1ubuntu3

[Anderson (amg1127)]

A warning for those people that made my workaround....
Now, you must remove old libhunspell from the system.

# rm /usr/lib/openoffice/program/libhunspell*