Le mercredi 22 avril 2015 à 22:10 -0400, Mike Miller a écrit : > > I am however a bit surprised by the fact that the SOVERSION of liboctave > > has not been bumped upstream. It looks like it should have been, given > > the breakage that you describe. > > Agree, this probably should be done. Several deprecated functions and > the deprecated Octave_map class have been dropped from the library in > version 4.0. Ok thanks. I consider this issue as a blocker for the upload to experimental, because it determines the name of the liboctave package. If upstream decides to bump the SOVERSION (which it should), the package will be named liboctave3. If it doesn't, we have to patch octave to change the SONAME, and we'll probably use something like liboctave2a (using suffix letters seems to be standard practice in Debian for bumping SONAMES when upstream forgets to do so). How should we deal with this issue upstream? Do you want me to open a bug report? Or can you act directly? -- .''`. Sébastien Villemot : :' : Debian Developer `. `' http://sebastien.villemot.name `- GPG Key: 4096R/381A7594
Attachment:
signature.asc
Description: This is a digitally signed message part