[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #43159] The Signal package (1.3.0) specgram()
[Octave-bug-tracker] [bug #43159] The Signal package (1.3.0) specgram() function is broken in ML when installed from MacPorts or Brew 0.9.5
Sat, 06 Sep 2014 04:02:41 +0000
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_5) AppleWebKit/537.78.1 (KHTML, like Gecko) Version/6.1.6 Safari/537.78.1
Follow-up Comment #1, bug #43159 (project octave):
One thing I noticed that is kind of weird, is that I had been using Octave all
year up until last month. Only since August, have I ever seen this happen.
According to the package description, this was released back in January???
Author: various authors
Maintainer: Mike Miller <address@hidden>
Title: Signal Processing.
Description: Signal processing tools, including filtering, windowing and
Depends: octave (>= 3.8.0), control (>= 2.4.5), general (>= 1.3.2)
License: GPLv3+, public domain
It could be something relating to the brew Repository, which installs Octave
3.8.1. However, if it is a recent repository related problem for a Mac OSX
packaging tool, how come MacPorts is also having the exact same issue?
I can't think of a logical reason both of these package managers install the
problematic Signal package.
Further more, I have tried pulling the Signal package directly from the Octave
package repository from inside of Octave by installing each package using the
pkg command directly like "pkg install <package> -forge". I tried this after
having the packages fail when installed from the MacPorts repository, as well
as after downloading the packages directly (last month).
Did the January release not get pushed when committed or something? I am
really confused here.
Reply to this item at:
Message sent via/by Savannah