Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#47828 - [sagemath] Some arguments of the executable are broken
Attached to Project:
Community Packages
Opened by alcinos (alcinos) - Wednesday, 20 January 2016, 09:12 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 20 January 2016, 10:37 GMT
Opened by alcinos (alcinos) - Wednesday, 20 January 2016, 09:12 GMT
Last edited by Antonio Rojas (arojas) - Wednesday, 20 January 2016, 10:37 GMT
|
DetailsDescription:
The sagemath flag to build new modules is "sage -i modulename". However, this triggers an error in the bash script: /usr/bin/sage: line 297: ./sage: No such file or directory It is probably linked to the fact that the packaging sets a weird $SAGE_ROOT variable ($SAGE_ROOT=/usr) Additional info: * package version(s) : sagemath 6.10-2 Steps to reproduce: sage -i jmol |
This task depends upon
Closed by Antonio Rojas (arojas)
Wednesday, 20 January 2016, 10:37 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#44433
Wednesday, 20 January 2016, 10:37 GMT
Reason for closing: Duplicate
Additional comments about closing:
Comment by Antonio Rojas (arojas) -
Wednesday, 20 January 2016, 10:37 GMT
This is intentional. Either you install sage system-wide with pacman, and then you have to install optional packages also with pacman (pacman -S jmol) or you do a local install from the upstream package and then you can manage optional packages locally.