[Pkg-octave-devel] Bug#681064: Bug#681064: octave: does not configure properly
package octave
tags 681064 unreproducible moreinfo
severity 681064 normal
thanks
* Santiago Vila <sanvila@unex.es> [2012-07-10 13:23]:
> Package: octave
> Version: 3.6.2-2
> Severity: serious
>
> I had a wheezy system which was updated to wheezy last week.
>
> After "apt-get update; apt-get upgrade; apt-get dist-upgrade" today I decided
> to install octave and octave-info, then purge octave3.2 and octave3.2-info.
>
> Now octave does not configure:
>
> # dpkg --pending --configure
> Setting up octave (3.6.2-2) ...
> warning: X11 DISPLAY environment variable not set
> error: could not find the file or path /usr/share/octave/packages
> error: called from:
> error: /usr/share/octave/3.6.2/m/pkg/pkg.m at line 1234, column 5
> error: /usr/share/octave/3.6.2/m/pkg/pkg.m at line 418, column 16
> error: /usr/share/octave/3.6.2/m/startup/octaverc at line 26, column 1
>
> dpkg: error processing octave (--configure):
> subprocess installed post-installation script returned error exit status 1
> Processing triggers for menu ...
> Errors were encountered while processing:
> octave
I cannot reproduce the problem in my testing system as today. I am
hereby downgrading the severity level of this bug report from "serious"
to "normal".
The following is what I did. First, I put this in /etc/apt/preferences:
##################################
Package: *
Pin: release a=testing
Pin-Priority: 650
Package: *
Pin: release a=stable
Pin-Priority: 550
##################################
I then purged all Octave-related packages from my system and issued the
commands:
aptitude update
aptitude install octave3.2
aptitude install octave
aptitude purge octave3.2
and everything went fine.
I suspect that your system has some file left over from another package
that may be causing the problem. If this is true, then what you are
reporting is a real bug that must be fixed, but it is perhaps not caused
by the octave package.
Unless you provide us with a precise way to reproduce the problem, we
will keep the severity level of this report below the release-critical
threshold.
Best,
Rafael
Reply to: