Mail Archives: cygwin/2010/10/26/08:13:53
On 10/26/2010 05:58 AM, J.C. Wren wrote:
> OK, I did several things. First, I downgraded subversion to 1.6.12
> and everything worked. Then I re-ran the installer and re-installed
> the base cygwin package, which should have upgraded the DLL. It did
> not, It was still at 1.7.5. I'm using setup 2.721,
> http://mirrors.kernel.org for the site, the installer says the package
> installed is 1.7.7-1. I then manually deleted the cygwin1.dll and ran
> setup.exe again. THIS time it upgraded the DLL. The DLL's don't have
> any weird permission, so I don't know why it didn't upgrade. I did
> have sshd running, and setup threw a warning that I'd need to reboot.
> Maybe something related to that?
>
> Anyway, at this point, I now appear to be able to use subversion
> without filename mangling. I'm just curious why multiple installs of
> the cygwin base didn't update the cygwin1.dll.
>
> Very weird!
Setup.exe warned you that a file was in use and then told you to reboot
in order to complete your installation, and yet you think it's weird
that your installation is incomplete without a reboot. Hmmm....
Anyway, this is a well known problem with Windows. Files that are in
use, such as cygwin1.dll when sshd is running, cannot be immediately
replaced. If you want to replace them, you must either ensure they are
not in use (by stopping sshd and any other Cygwin process in this case)
or schedule them to be replaced upon reboot (which is precisely what
setup.exe does for you) and then actually reboot. :-)
-Jeremy
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
- Raw text -