octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: error when installing io package


From: John W. Eaton
Subject: Re: error when installing io package
Date: Thu, 15 Jan 2015 11:08:32 -0600
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.5.0

On 01/15/2015 08:49 AM, JohnD wrote:


-----Original Message-----
From: JohnD [mailto:address@hidden
Sent: Thursday, January 15, 2015 9:33 AM
To: address@hidden; address@hidden; 'Philip Nienhuis'
Subject: RE: error when installing io package


Message: 1
Date: Wed, 14 Jan 2015 12:22:10 -0600
From: "John W. Eaton" <address@hidden>
To: octave maintainers mailing list <address@hidden>
Subject: error when installing io package
Message-ID: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed

I noticed an error from movefile when installing the io package on
windows saying that there were no files to move.  Can anyone else
confirm this
problem,
or is it just me?  All I did was

    pkg install -noauto -verbose io-2.2.6.tar.gz

and the installation fails with the movefile "no files to move" error.

Should this problem be fixed in pkg by avoiding the call to movefile
if
there are
no files to move, or should movefile simply issue a warning if there
are
no files
to move and return success?

jwe


I see it on my 4.1.0+

pkg install -forge -noauto -verbose io
mkdir (C:\Users\JDONOG~1.ECE\AppData\Local\Temp\oct-lSqsGj)
untar (C:\Octave\Octave-4.1.0+\src\io-2.2.6.tar.gz,
C:\Users\JDONOG~1.ECE\AppData\Local\Temp\oct-lSqsGj)
movefile: no files to move
error: called from 'movefile' in file
C:\Octave\Octave-4.1.0+\share\octave\4.1.0+\m\miscellaneous\movefile.m
near line 92,  column 5


It doesn't do it in 3.8.2

Any idea what changed?  Is it the assumption of what directory the
PKG_??? file will be installed in?  The post_install script uses

files = cstrcat (desc.archprefix, filesep, octave_config_info ("canonical_host_type"), "-", octave_config_info ("api_version"), filesep, "PKG_???");

Is that no longer the valid location of the PKG_??? files?  If we just
want a quick fix for this problem with 4.1.0+, is there a better way
to specify the location of these files?

It also seems to me that using fullfile would be better than concatenating with filesep, but that's a separate issue.

jwe





reply via email to

[Prev in Thread] Current Thread [Next in Thread]