Re: EOL problems in cvs2svn converted repository
On Sun, 11 Feb 2018 17:49:32 +0100, Bo Berglund wrote: >Any advice? Thanks for all advice and links. Most helpful. I have now mastered the way the svn_apply_autoprops.py can be used and have completed the EOL configuration of the repository for contractors with all items therein. Had to do as follows: - Used a virtual machine running Ubuntu Server 16.04-3LTS (the py file would not run on Windows) - Installed subversion via apt-get, resulted in version 1.9.7 - Edited the ~/.subversion/config file and added all of the file types that should have native EOL to the autoprops section - Connected the machine to the remote network using OpenVPN - Checked out all of the projects in the repository - Ran the svn_apply_autoprops.py program in the projects - Committed the changes - Went back to Windows and updated my working copies and now I have CRLF line endings. In the process I have used the svn revert command several times when the result pointed to a flaw in the config files, very handy! So I guess I am done now (with this issue)! -- Bo Berglund Developer in Sweden
Re: Reverting accidental permanent acceptance of SSL certificate?
Bo Berglund wrote on Sun, 11 Feb 2018 21:00 +0100: > I found the certificate acceptance in this file: > > ~/.subversion/auth/svn.ssl.server/52e60f46d8c02303aea5256b18eb7aac > > It looks perfectly safe, does not contain anything especially useful. That file records the certificate itself (in standard encoding) and the list of failures the certificate had when you permanently accepted it (such as having expired, being self-signed, etc). If when the certificate is next seen it has only those failures that it had last time, it won't be prompted for again.
File not accepted as valid addition to svn
Today I found that there is a problem with some files in regards to the svn add command (on Windows 7): svn add Fasadändring&Attefalltillbyggnad.pdf svn: warning: W155010: 'D:\Bosse\Fasadändring' not found svn: E29: Could not add all targets because some targets don't exist svn: E29: Illegal target for the requested operation 'Attefalltillbyggnad.pdf' is not recognized as an internal or external command, operable program or batch file. Why does this happen? The & character is a fully legal part of a file name at least on Windows... I tried to find a list of characters that Subversion does not like, but apparently there is none. So is it in fact not possible to use & inside a file name in Svn (1.9.7)? Is there a workaround? (I replaced the & with a hyphen just to be able to continue, but got curious... While googling I found that trying to create a seemingly innocent file by name aux.txt also fails! It was mentioned as one of the (undocumented) "features" of Windows. I tried and sure enough there was an error. -- Bo Berglund Developer in Sweden
Re: File not accepted as valid addition to svn
Bo Berglund writes: > svn add Fasadändring&Attefalltillbyggnad.pdf > svn: warning: W155010: 'D:\Bosse\Fasadändring' not found '&' has special meaning to the shell and needs to be quoted or escaped. -- Philip
Re: File not accepted as valid addition to svn
On Mon, 12 Feb 2018 15:54:00 +, Philip Martin wrote: >Bo Berglund writes: > >> svn add Fasadändring&Attefalltillbyggnad.pdf >> svn: warning: W155010: 'D:\Bosse\Fasadändring' not found > >'&' has special meaning to the shell and needs to be quoted or escaped. I always thought that this was the case only for Linux, since & is a perfectly valid part of a file name on Windows... But I will refrain from such characters in paths in the future. -- Bo Berglund Developer in Sweden
Re: File not accepted as valid addition to svn
On 12.02.2018 18:41, Bo Berglund wrote: > On Mon, 12 Feb 2018 15:54:00 +, Philip Martin > wrote: > >> Bo Berglund writes: >> >>> svn add Fasadändring&Attefalltillbyggnad.pdf >>> svn: warning: W155010: 'D:\Bosse\Fasadändring' not found >> '&' has special meaning to the shell and needs to be quoted or escaped. > I always thought that this was the case only for Linux, since & is a > perfectly valid part of a file name on Windows... > But I will refrain from such characters in paths in the future. The Windows shell has special characters, too. As far as file names are concerned, Unix filesystems typically allow _more_ characters than Windows filesystems. -- Brane
Re: File not accepted as valid addition to svn
On Feb 12, 2018, at 5:13 PM, Branko Čibej wrote: > >> On 12.02.2018 18:41, Bo Berglund wrote: >> On Mon, 12 Feb 2018 15:54:00 +, Philip Martin >> wrote: >> >>> Bo Berglund writes: >>> svn add Fasadändring&Attefalltillbyggnad.pdf svn: warning: W155010: 'D:\Bosse\Fasadändring' not found >>> '&' has special meaning to the shell and needs to be quoted or escaped. >> I always thought that this was the case only for Linux, since & is a >> perfectly valid part of a file name on Windows... >> But I will refrain from such characters in paths in the future. > > The Windows shell has special characters, too. As far as file names are > concerned, Unix filesystems typically allow _more_ characters than > Windows filesystems. Nevertheless I try to avoid filenames that create difficulties under either system because we have a mix Windows, Mac, and *nix. Each comes with its idiosyncrasies. Oh, and sometimes build systems don't escape everything correctly. Just my 2 cents.
