On Sat, Jan 26, 2013 at 9:52 AM, Jérémy Lal wrote:
>> On 24 October 2012 08:17, Mike Miller wrote:
>>> The octave package provides the directories, and liboctinterp.so.1 has
>>> a compiled-in set of paths with its version number that it attempts to
>>> load.
>>
>> Ah, this is probably not the grea
> On 24 October 2012 08:17, Mike Miller wrote:
>> The octave package provides the directories, and liboctinterp.so.1 has
>> a compiled-in set of paths with its version number that it attempts to
>> load.
>
> Ah, this is probably not the greatest idea ever. I'm not sure how to
> fix it. Provide a
On 24 October 2012 08:17, Mike Miller wrote:
> The octave package provides the directories, and liboctinterp.so.1 has
> a compiled-in set of paths with its version number that it attempts to
> load.
Ah, this is probably not the greatest idea ever. I'm not sure how to
fix it. Provide a build-time
On Wed, Oct 24, 2012 at 4:32 AM, Sébastien Villemot wrote:
> It appears that octave 3.6.2 does not work with liboctave1 3.6.3, and
> conversely octave 3.6.3 does not work with liboctave1 3.6.2.
I took a look at this and the problem is simply that the load path
contains Octave's version number. No
Control: severity -1 serious
Control: tags -1 + confirmed
sacrifial-spam-addr...@horizon.com writes:
> Package: octave
> Version: 3.6.3-2
> Architecture: i386
>
> Upgrading from 3.6.2-5 is failing:
>
> # dpkg --configure octave
> Setting up octave (3.6.3-2) ...
> error: feval: function `unimpleme
Package: octave
Version: 3.6.3-2
Architecture: i386
Upgrading from 3.6.2-5 is failing:
# dpkg --configure octave
Setting up octave (3.6.3-2) ...
error: feval: function `unimplemented' not found
dpkg: error processing octave (--configure):
subprocess installed post-installation script returned e
6 matches
Mail list logo
