[Pkg-octave-devel] Bug#514035: octave3.0: glpk cannot find the octave runtime libraries

[LUK ShunTim]

Rafael Laboissiere wrote:
> * Thomas Weber <thomas.weber.mail at gmail.com> [2009-02-03 18:27]:
> 
>> Am Dienstag, den 03.02.2009, 18:11 +0100 schrieb Rafael Laboissiere:
>>> and:
>>>
>>>     dpkg -l libglpk0
>> Luk, you have libglpk from experimental (4.35).
> 
> Yes, this is what I suspected.
> 
> It is unfortunate that this bug happens.  In a perfect world that would not
> have been the case.  I mean, since octave3.0_3.0.1-6lenny2 depends on
> libglpk0 >= 4.29, the Octave binding for GLPK must work with libglpk0_4.35-1
> (the version in experimental) but it doesn't.
> 
> The problem arises because since version 4.32 of GLPK, the __glp_lib_*
> symbols are not exported anymore.  As Andrew Makhorin explained in a message
> to bug-glpk [1], those symbols have never been part of the published API.
> He then removed them form the list of exported symbols without bumping the
> SOVERSION of the library.
> 
> [1] http://lists.gnu.org/archive/html/bug-glpk/2008-10/msg00010.html
> 
> Now, both 3.0.4 and 3.1.51 packages in Debian fail with the libglpk0 package
> in experimental.  The problem seems to have been fixed in Mercurial [2] and
> we should backport it to our packages before they migrate into unstable.
> 
> [2] http://hg.savannah.gnu.org/hgweb/octave/diff/aaccb1362347/src/DLD-FUNCTIONS/__glpk__.cc
> 

Thanks for your prompt replies.

Yes, it must be that installing octave3.1 pulls in the newer version.
Downgrading to 4.29 in sid works for both octave3.0 and 3.1.

BTW, what mechanism is used to let the octave runtimes be found by the
oct modules? Just want to learn a bit more.

Thanks again,
ST
--