In this case you would download the package and run the command: pkg install symbolic-win-py-bundle-2.4.0.zipĪnother more tedious option would be for you to compile your own copy from development sources, as the fix has supposedly been pushed to the mxe-octave repository. If you don't already have this on your Windows machine, the package maintainer has a separate self-contained package for Windows that can be obtained from the author's github repository. NOTE: symbolic currently requires Python and Sympy installed. Then within octave, issue the following from the command line: pkg install symbolic-2.4.0.tar.gz You are still able to go to the Octave Forge package site, manually download a package file, and then as described in the Octave manual and help for pkg run the install command.Į.g., you could download symbolic-2.4.0.tar.gz and save it to your current working directory. It only prevents you from using the program to go fetch packages to be installed. This, however, does not prevent you from installing packages. It should be fixed in the next Octave release. Recent news Package releases RSS stk-2.7.0 released sockets-1.3.0 released dicom-0.4.1 released mapping-1.4. That bug report and the original help list discussion summarize the certificate issue and problem verification. To install a package, use the pkg command from the Octave prompt by typing: pkg install -forge packagename, where packagename is the name of the package you want to install. Yes, there appears to be a known issue logged on the bug tracker with the current release version of Octave (4.2.0) on windows being unable to connect to https due to the curl issue you identified in the linked discussions/questions. EDIT: this bug is no longer present in Octave v4.2.1, and the issue described in the Question should no longer occur.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |