Re: Subversion mangling names in .svn/entries metadata file
On Sat, Oct 23, 2010 at 12:34 AM, Andy Koppe andy.ko...@gmail.com wrote: On 22 October 2010 18:51, J.C. Wren wrote: I updated my Cygwin install a couple days ago, and have ran into a problem with Subversion mangling the .svn/entries file. Before the problem occurred, I had done a 'svn status' with no issues. I committed a file, ran 'svn status' again, and received the following error message: svn: Error at entry 1 in entries file for '.': svn: Invalid escape sequence Looking in the .svn/entries file, the first file name should read http://amzatlanta.com/svn_amzatlanta/sx_gfm/trunk http://amzatlanta.com/svn_amzatlanta/sx_gfm but is actually encoded as h\x74\x74p://\x61mz\x61\x74l\x61n\x74\x61.\x63\x6f\x6d/\x73\x76n_\x61mz\x61\x74l\x61n\x74\x61/\x73\x78_g\x66\x6d/\x74\x72\x75nk h\x74\x74p://\x61mz\x61\x74l\x61n\x74\x61.\x63\x6f\x6d/\x73\x76n_\x61mz\x61\x74l\x61n\x74\x61/\x73\x78_g\x66\x6d Attempting to check out the repository into a new directory gives the same error. On another machine with a slightly older install of Cygwin had no issues. I was also able to check it out on a Linux box (I did this to make sure the repository hadn't gotten corrupted somehow). One person in #cygwin speculated it might be a locale issue. Seems unlikely, as the filenames are entirely within the ASCII range. I've got no idea though why selected lowercase characters should have been replaced with their hex escape equivalents. The cygcheck output doesn't look healthy though: Cygwin DLL version info: DLL version: 1.7.5 cygwin 1.7.7-1 Also, any chance that TortoiseSVN\bin in the path might interfere? Try 'which svn' and 'svn --version' to make sure you're really getting the Cygwin version. $ svn --version svn, version 1.6.13 (r1002816) compiled Oct 4 2010, 09:08:12 Andy -- 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 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! --jc -- 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
Re: Subversion mangling names in .svn/entries metadata file
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
Re: Subversion mangling names in .svn/entries metadata file
Do you *really* think I didn't reboot it? C'mon now, be serious. I've been using Cygwin for at least 5 years, I think I can follow some instructions when setup tells me I'll need to. I think I ended up rebooting 12 times, or at least that what it seemed like. Maybe I didn't explicitly say that I did reboot the system, but that's not a reason to merely assume that I didn't. In any case, it made no difference. There were half a dozen files ending in .new in /usr/bin and /usr/sbin, so *something* wasn't running that was supposed to move them after a reboot. --jc Eagles may soar, but weasels don't get sucked into jet engines. On Tue, Oct 26, 2010 at 8:12 AM, Jeremy Bopp jer...@bopp.net wrote: 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 -- 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
Re: Subversion mangling names in .svn/entries metadata file
On 10/26/2010 8:11 AM, J.C. Wren wrote: Do you *really* think I didn't reboot it? C'mon now, be serious. I've been using Cygwin for at least 5 years, I think I can follow some instructions when setup tells me I'll need to. Sorry, but yes, that's what I thought. It's a common enough problem for people in a rush to get things running to skip a reboot. Perhaps you did skip a reboot at one point and things got a little wedged when you ran later instances of setup.exe. I'm not intimately familiar with the guts of setup.exe to know for sure whether or not that is possible though. Maybe I didn't explicitly say that I did reboot the system, but that's not a reason to merely assume that I didn't. On the contrary, I think it's a great reason to assume you didn't reboot given your description of how cygwin1.dll eventually got updated and the following quote: On 10/26/2010 05:58 AM, J.C. Wren wrote: I did have sshd running, and setup threw a warning that I'd need to reboot. Maybe something related to that? -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
Re: Subversion mangling names in .svn/entries metadata file
On 10/26/2010 8:11 AM, J.C. Wren wrote: [snip] There were half a dozen files ending in .new in /usr/bin and /usr/sbin, so *something* wasn't running that was supposed to move them after a reboot. Same thing happened to me some time ago, I reported it on this list, no replies. I just moved the really *new* files over the old ones, some where older than the ones installed so I just deleted those. -- René Berber -- 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
Re: Subversion mangling names in .svn/entries metadata file
Hello, * On Tue, Oct 26, 2010 at 09:35:47AM -0500 Jeremy Bopp wrote: On 10/26/2010 8:11 AM, J.C. Wren wrote: Maybe I didn't explicitly say that I did reboot the system, but that's not a reason to merely assume that I didn't. On the contrary, I think it's a great reason to assume you didn't reboot given your description of how cygwin1.dll eventually got updated and the following quote: My experience on user support (both from the side of giving support, as well as from the side of receiving it) on other forums tells me that it is never wrong to state the (expectedly) obvious. It happens every now and then, even to the experienced users, that they forget something like that. Thus, it is better to ask the obvious instead of trying to debug the problem for hours, only to find out that the obvious was the problem in the first place. Best regards, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/ -- 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
RE: Subversion mangling names in .svn/entries metadata file
Maybe I didn't explicitly say that I did reboot the system, but that's not a reason to merely assume that I didn't. On the contrary, I think it's a great reason to assume you didn't reboot given your description of how cygwin1.dll eventually got updated and the following quote: This reminds me of a story: Support person (on phone): Right-click on your desktop Customer: Nothing's happening Support person: Didn't you right-click on your desktop? Customer: Yes, I wrote 'click' on my desktop.. Bill -- 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
Re: Subversion mangling names in .svn/entries metadata file
On 10/22/2010 10:51 AM, J.C. Wren wrote: I updated my Cygwin install a couple days ago, and have ran into a problem with Subversion mangling the .svn/entries file. Looks like you updated to Cygwin 1.7.5. You might want to try 1.7.7. Looking in the .svn/entries file, the first file name should read http://amzatlanta.com/svn_amzatlanta/sx_gfm/trunk http://amzatlanta.com/svn_amzatlanta/sx_gfm but is actually encoded as h\x74\x74p://\x61mz\x61\x74l\x61n\x74\x61.\x63\x6f\x6d/\x73\x76n_\x61mz\x61\x74l\x61n\x74\x61/\x73\x78_g\x66\x6d/\x74\x72\x75nk h\x74\x74p://\x61mz\x61\x74l\x61n\x74\x61.\x63\x6f\x6d/\x73\x76n_\x61mz\x61\x74l\x61n\x74\x61/\x73\x78_g\x66\x6d One person in #cygwin speculated it might be a locale issue. This is indeed odd. I use subversion every day and don't have this problem, but I also have LANG=C.UTF-8 defined in my environment. You might want to try that. Otherwise, I'd have to reproduce this locally to investigate further, and I don't think I have access to that repository. -- David Rothenberger daver...@acm.org Volunteer Cygwin Subversion maintainer. -- 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
Re: Subversion mangling names in .svn/entries metadata file
On 22 October 2010 18:51, J.C. Wren wrote: I updated my Cygwin install a couple days ago, and have ran into a problem with Subversion mangling the .svn/entries file. Before the problem occurred, I had done a 'svn status' with no issues. I committed a file, ran 'svn status' again, and received the following error message: svn: Error at entry 1 in entries file for '.': svn: Invalid escape sequence Looking in the .svn/entries file, the first file name should read http://amzatlanta.com/svn_amzatlanta/sx_gfm/trunk http://amzatlanta.com/svn_amzatlanta/sx_gfm but is actually encoded as h\x74\x74p://\x61mz\x61\x74l\x61n\x74\x61.\x63\x6f\x6d/\x73\x76n_\x61mz\x61\x74l\x61n\x74\x61/\x73\x78_g\x66\x6d/\x74\x72\x75nk h\x74\x74p://\x61mz\x61\x74l\x61n\x74\x61.\x63\x6f\x6d/\x73\x76n_\x61mz\x61\x74l\x61n\x74\x61/\x73\x78_g\x66\x6d Attempting to check out the repository into a new directory gives the same error. On another machine with a slightly older install of Cygwin had no issues. I was also able to check it out on a Linux box (I did this to make sure the repository hadn't gotten corrupted somehow). One person in #cygwin speculated it might be a locale issue. Seems unlikely, as the filenames are entirely within the ASCII range. I've got no idea though why selected lowercase characters should have been replaced with their hex escape equivalents. The cygcheck output doesn't look healthy though: Cygwin DLL version info: DLL version: 1.7.5 cygwin 1.7.7-1 Also, any chance that TortoiseSVN\bin in the path might interfere? Try 'which svn' and 'svn --version' to make sure you're really getting the Cygwin version. $ svn --version svn, version 1.6.13 (r1002816) compiled Oct 4 2010, 09:08:12 Andy -- 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
