[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [lmi] Cannot 'mv' read-only files on cygwin?
From: |
Greg Chicares |
Subject: |
Re: [lmi] Cannot 'mv' read-only files on cygwin? |
Date: |
Tue, 10 Apr 2018 21:48:21 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 |
On 2018-03-05 23:37, Greg Chicares wrote:
[...]
> Kim's trying to upgrade [...] running 'install_msw.sh' yielded:
>
> mv scratch/mingw32 /MinGW_
> mv: cannot move 'scratch/mingw32' to '/MinGW_': Permission denied
> make: *** [install_mingw.make:104: all] Error 1
Something similar happened today:
+ cd /opt/lmi/src
# Preserve any preexisting source directory, moving it aside so that
# 'git clone' will install a pristine working copy.
mv lmi lmi-moved-"$stamp0"
+ mv lmi lmi-moved-2018-04-10T12:43:45Z
mv: cannot move 'lmi' to 'lmi-moved-2018-04-10T12:43:45Z': Permission denied
I was hoping that upgrading cygwin might give us GNU/Linux 'mv'
behavior, but this cygwin installation is pretty recent:
Cygwin DLL version info:
DLL version: 2.9.0
which moved out of test only last September:
https://sourceware.org/ml/cygwin-announce/2017-09/msg00036.html
and I don't think they've changed anything pertinent since then.
I think the best we can do here is:
cp --archive lmi lmi-moved-"$stamp0"
rm -rf /opt/lmi/src/lmi
Then 'cp' will almost certainly succeed (which is why we used it to
replace 'mv' in the 2018-03-05 situation), so we'll have our backup;
and, if 'rm' fails, it doesn't matter much.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [lmi] Cannot 'mv' read-only files on cygwin?,
Greg Chicares <=