Package Details: octave-general 2.1.3-1

Git Clone URL: (read-only, click to copy)
Package Base: octave-general
Description: General tools for Octave.
Upstream URL:
Licenses: custom
Groups: octave-forge
Submitter: drizzd
Maintainer: pingplug
Last Packager: pingplug
Votes: 51
Popularity: 0.000205
First Submitted: 2012-03-12 21:56 (UTC)
Last Updated: 2023-11-04 17:17 (UTC)

Latest Comments

petronny commented on 2018-05-13 17:15 (UTC)

Hi 2.1.0 is out And here is the patch to PKGBUILD

diff --git a/octave-general/PKGBUILD b/octave-general/PKGBUILD
index 29c3a9f..473ce14 100644
--- a/octave-general/PKGBUILD
+++ b/octave-general/PKGBUILD
@@ -8,23 +8,23 @@

 pkgdesc="General tools for Octave."

 _octave_run() {
        octave --no-history --no-init-file --no-window-system -q -f --eval "$*"
@@ -45,7 +45,7 @@ build() {
        _octave_run "$(cat <<-EOF
                pkg local_list octave_packages;
                pkg prefix $_prefix $_archprefix;
-               pkg install -verbose -nodeps $_archive;
+               pkg install -verbose -nodeps $pkgname-$;

drizzd commented on 2015-06-10 08:44 (UTC)

Upgrading fails with conflicts How to fix: Uninstall the package and packages which depend on it with pacman -Rc <package>, then re-install the new version and packages which depend on it. See also

zsrkmyn commented on 2014-11-04 11:18 (UTC)

Thank you for your reply! I tested the .install script in my machine and several other environments, including building and installing in a clean chroot enviroment using 'devtools'. I am glad that the fault is not caused by the script, and I am really sorry to wrongly report the bug. I find it that when install `octave' and `octave-general` separately (just using this `` pacman -S octave ; pacman -S octave-general``), it works fine. But when install them together (using `` pacman -S octave octave-general ``), it can be wrong as I metioned before. Adding '_' to the variable or not makes no difference.

drizzd commented on 2014-11-03 20:21 (UTC)

Thank you for noticing this bug. This will be fixed in future updates of the packages. However, I do not see how this has any effect, since the configured $prefix $libdir is the default anyways.

zsrkmyn commented on 2014-11-03 13:27 (UTC)

the command in .install script should be: `` octave -q -f --eval "pkg prefix $_prefix $_libdir; pkg install -verbose -global /usr/share/octave/$_pack.tar.gz" `` but not: `` octave -q -f --eval "pkg prefix $prefix $libdir; pkg install -verbose -global /usr/share/octave/$_pack.tar.gz" `` otherwise, it can be wrong during the installaltion: /usr/bin/octave-cli-3.8.2: error while loading shared libraries: cannot open shared object file: No such file or directory /usr/bin/octave-cli-3.8.2: error while loading shared libraries: cannot open shared object file: No such file or directory error: command failed to execute correctly Almost all the "octave-*" packages have this problem.

drizzd commented on 2014-02-06 19:38 (UTC)

I have reported your issue upstream: But if you upgrade your octave package -- it's version 3.8.0-2 now -- that probably solves your issue.

noplomplom commented on 2014-02-06 06:08 (UTC)

Build error: