Re: [viewvc-users] viewvc svn revealing fullpaths

Adam Richards wrote:
>> Is there any chance that the versioned directory structure inside the
>> repository actually reflects this tree?  If you run 'svn ls
>> file:///usr/home/svn/repository' on your machine, do you get a listing that
>> contains 'Module_1', 'Module_2', etc., or you do you see instead 'usr'?
> 
> Contains "usr":
> 
>   $ svn ls file:///usr/home/svn/repository
>   usr/
> 
> Hum... interesting.  Did I create the repository incorrectly?  I
> certainly would expect a Module listing.

Technically, you created the repository just fine.  (It's hard to mess that
step up.)  I think you may have just populated it in a way that doesn't
reflect what you wanted.  Just to be sure, run

  $ svn log -vq file:///usr/home/svn/repository

If you see "changed path" records that begin with "/usr/..." then you've
managed to actually created versioned directories in the repository above
the modules which you probably intended to live in the root of the
repository.  It's not world-ending stuff.  You can fix the problem with
regular Subversion commands:

  $ export REPOS_URL=file:///usr/home/svn/repository
  $ svn move $REPOS_URL/usr/home/svn/repository/Module_1 \
             $REPOS_URL/Module_1 \
             -m "Move Module_1 to the root of the repository"
  $ svn move $REPOS_URL/usr/home/svn/repository/Module_2 \
             $REPOS_URL/Module_2 \
             -m "Move Module_2 to the root of the repository"
  [...]

Or you can try to rebuild the history of the repository as if it was always
the way you wanted it using 'svnadmin dump' (to dump the repository
history), 'svndumpfilter include' (to filter that dumpfile by the paths you
want to keep), some 'sed' magic to fixup the paths in the filtered dumpfile,
and then 'svnadmin load' into a new repository of the filtered data.

That conversation is more appropriate to the [email protected]
list, though.

> Ah, right.  I suppose when I want multiple repos I'll use the
> root_parents directive and *not* svn_roots, right?

You can if you wish, or you can explicitly list each root.  And to be clear,
you can use root_parents right now if you want, just set the value to point
to the parent directory of the repository, not the repository itself.
ViewVC won't be bothered that there's only one repository in the root parent
directory, and you won't have to remember to change that value later when
create additional repositories.

-- 
C. Michael Pilato <[email protected]>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

------------------------------------------------------
http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4255&dsMessageId=2431597

To unsubscribe from this discussion, e-mail: [[email protected]].

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAksr3UIACgkQokEGqRcG/W5ROACdELk7b1yrEzQNLGNYpWIKxYRp
Wm0AnjFqhwBBh/z0r6r1BslXvoz9Rqeo
=ySD7
-----END PGP SIGNATURE-----