Re: Bug: Incorrect tree structure on nested repository access

altern wrote:
> I have really confusing bug in Tortoise 1.5.5 - it treats with
> subrepositories in a strange way. Subfolders of subrepository are displayed
> on a wrong nesting level. If PROJECT has folders trunk, tags and branches,
> they are displayed on the same level as the PROJECT folder item while they
> should be nested into PROJECT folder. Attachment included:
> http://www.nabble.com/file/p20837256/TortoiseSVN-bug.jpg TortoiseSVN-bug.jpg
>
> Under subrepository I mean repository located in folder (on hard disk) with
> the same name as the folder (at the repository), for instance, at the top of
> repository structure. Give you an example:
> C:/repository/ (hard disk structure)
> conf\
> db\
> hooks\
> locks\
> format
> README.txt
> PROJECT\
> conf\
> db\
> hooks\
> locks\
> format
> README.txt

This setup is not allowed. I've explained this in length before on this
list (even though the one who was doing it refused to accept any
explanation):
The repository folder is private, you must not ever mess around inside
that folder yourself.

For example, in your setup above: what would have happened if Subversion
would require a folder named "PROJECT" itself one day for storing
additional data?

Also: you won't be able to create repositories inside an existing
repository anymore with Subversion 1.6 - the devs added an explicit
check for that so it won't work anymore.

> It may seem useless to use such framework, so you could ask me for the
> reason why exactly I create such subrepositories. It is the matter of
> independent revisions flow and convenient multiproject environment
> organization which allows users to see all the projects that are hosted on
> subversion server directly from subversion client. I completely disagree
> with people who think that this feature should be deprecated. This bug is
> critical for me because I have several multiple-project environments
> configured with such structure (which of course I and repo-users get used
> to) and after update to subversion 1.5 and TortoiseSVN 1.5 they are
> completely mixed up. My repositories cannot be accessed directly from
> TortoiseSVN.

This is not a bug but by design: you must never rely on 'features' that
you introduced yourself by messing with internals of an application.

And no: even if you think it's a bug and must be fixed, that's never
gonna happen.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=979716
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].