Bug 186964 - "dispatch" from octave-forge seems to conflict with new octave 2.1.73
Summary: "dispatch" from octave-forge seems to conflict with new octave 2.1.73
Alias: None
Product: Fedora
Classification: Fedora
Component: octave
Version: 4
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Quentin Spencer
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: 186966
TreeView+ depends on / blocked
Reported: 2006-03-27 18:51 UTC by Piergiorgio Sartor
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-03-27 21:31:33 UTC

Attachments (Terms of Use)

Description Piergiorgio Sartor 2006-03-27 18:51:10 UTC
Description of problem:
After upgrading from octave-2.1.72-3 to octave-2.1.73-1, the following
error appears when "octave" is launched from terminal:

error: `dispatch' undefined near line 2 column 1
error: near line 2 of file `/usr/share/octave/site/m/octave-forge/fixed//PKG_ADD'
error: source: error sourcing file

This causes, of course, problems with external functions.
Specifically, if something is defined in "~/.octaverc", like
LOADPATH=..., this seems to fail.
I did not check if octave-forge is fully functional.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
Upgrade from previous version (maybe this is important).
Start "octave".
Actual results:
Errors are displayed and, maybe, something is not working.

Expected results:
Clean start.

Additional info:
This seems to be a regression since 2.1.72 was fine.
Maybe octave-forge related, don't know.
Regarding "~/.octaverc", I've an other installation of octave
which has, in the "rc" file:

LOADPATH=[LOADPATH "/home/.../octlibs//"

This was working fine with 2.1.72, but due to the errors with "dispatch",
the LOADPATH is un-modified and the local libraries are not found.

Comment 1 Quentin Spencer 2006-03-27 21:31:33 UTC
Thanks for reporting this. The problem was caused by a change in octave's paths
for executable extensions from /usr/libexec/octave/site/exec/i686-pc-linux-gnu/
to /usr/libexec/octave/site/exec/i686-redhat-linux-gnu/. This was not
intentional, and I still haven't figured out what caused the change, but it is
easily fixed by rebuilding octave-forge for the new version of octave. A new
build has been requested, and the new release should fix the problem.

Note You need to log in before you can comment on or make changes to this bug.