List Info

Thread: auto-props problems




auto-props problems
country flaguser name
United States
2008-04-14 06:31:15
Hi, all.

My migration is running without errors!  Woo hoo! 
However...

When I compare the export of VSS to SVN, I found that all my
files (or 
all the ones I've checked so far) have properties
"svn:eol-style=native" 
and "svn:mime-type=text/plain".  That's kind of a
problem for MSI and 
EXE files (and several other types, but these are enough to
prove the 
problem).

At what point in the process is this property being
attached?  I'm using 
Subversion 1.4.6, and running the migration on XP with a
batch file, 
then exporting using TortoiseSVN 1.4.8.  My vss2svn is rev
339.

My command line for the migration is:

%build%vss2svn --ssphys %build%ssphys.exe --vssdir %VSS% 
--revtimerange %revtimerange% --timing --verbose
--auto_props 
"C:Documents and SettingsusernameApplication
DataSubversionconfig" 
 > migration.log


(build, vss and revtimerange are all valid values defined
earlier in my 
batch file)

I can include my config if that will help, but I can say for
sure that 
MSI and EXE are not contained in the file, and I do not have
any other 
filename pattern which would match these files.

Anybody?  I'm so close, I just need to correct this one
problem and I 
can be done with VSS for good.

_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.
pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/lis
tinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-c
ontrol.subversion.vss2svn.user


Re: auto-props problems
country flaguser name
United States
2008-04-14 22:46:45
Bruce Wilson wrote:
> Hi, all.
>
> My migration is running without errors!  Woo hoo! 
However...
>
> When I compare the export of VSS to SVN, I found that
all my files (or 
> all the ones I've checked so far) have properties 
> "svn:eol-style=native" and
"svn:mime-type=text/plain".  That's kind of 
> a problem for MSI and EXE files (and several other
types, but these 
> are enough to prove the problem).
>
> At what point in the process is this property being
attached?  I'm 
> using Subversion 1.4.6, and running the migration on XP
with a batch 
> file, then exporting using TortoiseSVN 1.4.8.  My
vss2svn is rev 339.
>
> My command line for the migration is:
>
> %build%vss2svn --ssphys %build%ssphys.exe --vssdir
%VSS% 
> --revtimerange %revtimerange% --timing --verbose
--auto_props 
> "C:Documents and SettingsusernameApplication 
> DataSubversionconfig" > migration.log
>
>
> (build, vss and revtimerange are all valid values
defined earlier in 
> my batch file)
>
> I can include my config if that will help, but I can
say for sure that 
> MSI and EXE are not contained in the file, and I do not
have any other 
> filename pattern which would match these files.
>
> Anybody?  I'm so close, I just need to correct this one
problem and I 
> can be done with VSS for good.

Hello Bruce,

I'm unfortunately not too familiar with the auto-props
feature but I 
would suggest disabling it if rerunning without it is
feasible. You 
should also check VSS itself to ensure that these files are
not marked 
as text files there.

You should also note that in general, Subversion best
practices 
recommend against keeping build artifacts such as .exe and
.msi in the 
repository, so you may just want to remove them instead of
fixing them 
unless your build/deployment process depends on them being
there.

toby

_______________________________________________
vss2svn-users mailing list
Project homepage:
http://www.
pumacode.org/projects/vss2svn/
Subscribe/Unsubscribe/Admin:
http://lists.pumacode.org/mailman/lis
tinfo/vss2svn-users-lists.pumacode.org
Mailing list web interface (with searchable archives):
http://dir.gmane.org/gmane.comp.version-c
ontrol.subversion.vss2svn.user


[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )