Wednesday, 15 September 2010

version control - What can be a reason for getting empty svn repository after loading dump file? -



version control - What can be a reason for getting empty svn repository after loading dump file? -

i trying split existing svn repository since has multiple projects in it. want have separate repositories each. lastly step of splitting loading filtered dump file new repository have problem loaded somehow not see them. thought why happens?

thanks beforehand

i see transactions getting committed. how accessing new repository? starting svnserve on directory? using file:///?

do have svnlook on system? can utilize query particular directory. since we're in directory, it's pretty simple:

$ svnlook youngest .

this should print out lastly revision of repository. should agree svnadmin load.

$ svnlook tree .

this should print out entire directory tree of repository.

if doesn't work. seek these:

$ svnlook log .

that print out lastly log message.

$ svnlook changed

prints out changed.

if svnlook tree . doesn't print out anything, it's possible dump filled empty revisions. true if used svndumpfilter filter out transactions didn't like.

if repo have transactions according svnlook, utilize svnserve run local re-create of repo:

$ svnserve -r .

then open window, , seek this:

$ svn log -v svn://localhost

and see if prints out log of transactions.

addendum

i see have, , can see dropped tags, branches, , trunk.

it looks problem didn't specify thought. when specify include a, you're specifying files @ root of repo.

you have:

$ svndumpfilter include < repo.dump > a.dump

what want this:

$ svndumpfilter include trunk/a tags/a branches/a < repos.dump > a.dump

note how have give full path name of directory tree want include. might able this:

$ svndumpfilter include --pattern "*/a" < repo.dump > a.dump

your dump shows of directories excluded svndumpfilter. can utilize verify you're keeping think keeping.

svn version-control split repository tortoisesvn

No comments:

Post a Comment