Thu 31 Mar 2016 11:49:36 AM UTC, comment #2:
<title adapted after more investigation>
Turns out this also failed in 3.8.2. So this bug is really old.
(The examples were cooked a bit. But I am sure of the bug/regression as I hit it when trying the spreadsheet test scripts on a drive with spaces in the name.
Rather than impose installing io I figured I'd make up a simple example. But with the io package it is easier for me to show what fails)
If you have the OF io package installed you can do:
more off
pkg load io
io_ods_testscript ("oct") ## .ods file, invokes zip
- or -
io_ods_testscript ("oct", "test.gnumeric") ## invokes gzip
Run these commands from inside a subdir with, and a subdir without spaces in the name.
That example gives for a subdir w/o spaces in name (empty lines removed) (NOTE: all with octave-4.0.1 but 4.1.0+ behaves identical):
and for a subdir with spaces:
Running a level higher up (in d:\tmp):
..but...
runs fine.
I just tried with 3.8.2, 4.0.1 and a 4.1.0+ from Mar 29 and all show the same bug.
Is it a concealed manifestation of the "do not install Octave in a path with spaces" issue? That would be a very creepy gotcha.
Or is it that gzip / zip / bzip2 just get handed a path to the zip file that is in a format they don't expect? (or w/o double quotes)
(regression -> incorrect result)
|