[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[Pkg-octave-devel] Bug#799412: marked as done (octave-control: fails to call ss function due to undefined symbols)

Your message dated Sat, 19 Sep 2015 10:56:38 +0200
with message-id <1442652998.3259.58.camel@debian.org>
and subject line Re: [Pkg-octave-devel] Bug#799412: octave-control: fails to call ss function due to undefined symbols
has caused the Debian Bug report #799412,
regarding octave-control: fails to call ss function due to undefined symbols
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
799412: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799412
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: octave-control
Version: 2.8.3-1+b1
Severity: grave
Justification: renders package unusable

Dear Maintainer,
I installed Debian stretch a few days ago, switching from jessie.
On jessie I used octave without any problem. Now I'm having this error:

octave:1> pkg load control
octave:2> ss
error: __ss_dim__:
/usr/lib/x86_64-linux-gnu/octave/packages/control-2.8.3/x86_64-pc-linux-gnu-api-v50+/is_real_matrix.oct:
failed to load:
/usr/lib/x86_64-linux-gnu/octave/packages/control-2.8.3/x86_64-pc-linux-gnu-api-v50+/is_real_matrix.oct:
undefined symbol:
_ZNK5ArrayINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEE17resize_fill_valueEv
error: called from
    __ss_dim__ at line 30 column 3
        ss at line 196 column 10

As it seems to search for a c++11 symbol, I suspect some libraries got
compiled with different ABIs. When trying the upstream control package,
it doesn't compile too and fails upon installing it.

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.1.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages octave-control depends on:
ii  libblas3 [libblas.so.3]            1.2.20110419-10
ii  libc6                              2.19-19
ii  libgcc1                            1:5.2.1-17
ii  libgfortran3                       5.2.1-17
ii  liblapack3 [liblapack.so.3]        3.5.0-4
ii  liboctave3                         4.0.0-3
ii  libopenblas-base [liblapack.so.3]  0.2.14-1
ii  libquadmath0                       5.2.1-17
ii  libslicot0                         5.0+20101122-2
ii  libstdc++6                         5.2.1-17
ii  octave                             4.0.0-3

octave-control recommends no packages.

octave-control suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Version: 2.8.4-1

Le samedi 19 septembre 2015 à 07:31 +0200, Niels Thykier a écrit :
> On Sat, 19 Sep 2015 01:21:44 +0200 Vincenzo Scotti <vinc94@gmail.com> 
> wrote:
> > Package: octave-control
> > Version: 2.8.3-1+b1
> > Severity: grave
> > Justification: renders package unusable
> > 
> > Dear Maintainer,
> > I installed Debian stretch a few days ago, switching from jessie.
> > On jessie I used octave without any problem. Now I'm having this 
> > error:
> > 
> > [...]
> > 
> > As it seems to search for a c++11 symbol, I suspect some libraries 
> > got
> > compiled with different ABIs. When trying the upstream control 
> > package,
> > it doesn't compile too and fails upon installing it.
> > 
> > [...]
> > ii  octave                             4.0.0-3
> > [...]
> 

> The GCC-5 related transition is still ongoing for octave.  I suspect
> it
> would be better in unstable right now.  Unfortunately, unstable is
> struck by #796310, which also affects octave (and might break it with
> similar symptoms).
> 
> In the current situation, the best I can offer you is either to wait
> (with a broken package) or downgrade (though unsupported and you will
> probably have to use snapshots.debian.org).  :-/

I confirm that the version currently in unstable (2.8.4-1) is not
affected by the problem. Closing the bug with appropriate versioning
info.
-- 
 .''`.    Sébastien Villemot
: :' :    Debian Developer
`. `'     http://sebastien.villemot.name
  `-      GPG Key: 4096R/381A7594

Attachment: signature.asc
Description: This is a digitally signed message part


--- End Message ---
Reply to: