Confusing error

[Noah Spurrier <no...@noah.org>]

I had just finished tweaking my ~/.subversion/config file to add more MIME
types. For no good reason I set the MIME type for CPP files to text/x-c++
(Oops). The I tried adding directory tree of code.

     svn add *

I quickly get the following message after which svn stops with error code 1:

     A         BMP.CPP
     svn: MIME type 'text/x-c++' ends with non-alphanumeric character

The problem is that when I checked the .svn/entries file I saw that the
offending file was actually scheduled for addition. Furthermore if I then run
"svn add *" again it would continue where it stopped and add the rest of the
files in the directory tree (oddly most were C files, not C++).

It was a confusing error at first because Subversion seemed to imply that
there is something wrong with the file rather than the ~/.subversion/config.
I realized the error was referring to a problem with the MIME type in
~/.subversion/config and not the file being added. But it seems wrong that
Subversion would stop and return an error code, yet still successfully
schedule the file for addition. Would this behavior qualify as a bug? 

I fixed the config file and had no more problems.

Yours,
Noah

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Confusing error

[Ryan Schmidt <su...@ryandesign.com>]

On Aug 5, 2007, at 17:40, Noah Spurrier wrote:

> I had just finished tweaking my ~/.subversion/config file to add  
> more MIME
> types. For no good reason I set the MIME type for CPP files to text/ 
> x-c++
> (Oops). The I tried adding directory tree of code.
>
>     svn add *
>
> I quickly get the following message after which svn stops with  
> error code 1:
>
>     A         BMP.CPP
>     svn: MIME type 'text/x-c++' ends with non-alphanumeric character
>
> The problem is that when I checked the .svn/entries file I saw that  
> the
> offending file was actually scheduled for addition. Furthermore if  
> I then run
> "svn add *" again it would continue where it stopped and add the  
> rest of the
> files in the directory tree (oddly most were C files, not C++).
>
> It was a confusing error at first because Subversion seemed to  
> imply that
> there is something wrong with the file rather than the  
> ~/.subversion/config.
> I realized the error was referring to a problem with the MIME type in
> ~/.subversion/config and not the file being added. But it seems  
> wrong that
> Subversion would stop and return an error code, yet still successfully
> schedule the file for addition. Would this behavior qualify as a bug?
> I fixed the config file and had no more problems.

Subversion was successful in scheduling the file for addition, but  
was unsuccessful in setting its MIME type. I would find it clearer if  
Subversion would not schedule the file for addition in this case. I  
think this is another instance of this bug:

http://subversion.tigris.org/issues/show_bug.cgi?id=2713

You may wish to add a note to that bug (with a link to this mailing  
list discussion) since your case is slightly different, and would  
help show that the problem is more general than the one reported in  
the existing bug.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org