[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Bug report

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Wed, 11 Jan 2012 20:55:56 +0100

On 11.01.2012 10:04, Poot, B. (Bas) wrote:
> Hello,
>
> I have 3 bugs related to svn:extnerals and/or branching. I read on your
> site to send my ‘detailed bug report’ to this email address, so here it is:
>
> *Bug1: externals with bigger folder depth do not showing in repo browser*
>
> Normal externals do show prety well with nice folder icon and an arrow
> to distinct them from normal folders.
>
> But when i create an external like this: (old 1.6 style)
>
> http://svn.organisation.com/svn/files/version1 files/version1
> <http://svn.organisation.com/svn/files/version1%20files/version1>
>
> where (as you can see) the local folder is not just 1 folder but a
> subfolder (where the folder ‘files’ doesn’t exist) and i go to the repo
> browser. The folder ‘files’ (that would be created when you checkout the
> entire repo) doesn’t show in the repo browser.

That's because the intermediate folder ('files' in your example) does
not exist, i.e. is not versioned.
If you had a folder http://svn.organisation.com/svn/files/version1/files
which could be completely empty but was versioned, then the repo browser
would show your externals just fine.

Please note that externals the way you use it are not officially
supported by SVN. The devs only discovered that the externals are
sometimes used that way after the externals was introduced. And in 1.7
that 'feature' doesn't work properly anymore. So you really should
change your externals now - they might not work at all in the next release.

> *Bug2: updating revision of externals doesn’t work with the checkboxes
> in the ‘create brache/tag’ dialog*
>
> When i create a branch or tag of my trunk, and my externals point to the
> latest version of some other svn repo (or other location on same repo
> for that matter), I have the ability to ‘check’ the externals that i
> want tortoise to set to an explicit revision number.
>
> After i checked some externals (the ones i wanted) and i clicked ‘ok’,
> svn worked for a while and i had my branch.
>
> Great i thought, but after some checking i noticed that all my external
> references were pointing to a non-specific version. So the entire option
> ‘Set explicit revisions for these externals’ doesn’t work.

Think about it: if that feature wouldn't work at all, don't you think we
would have noticed it by now?
So something must be different on your end than on all of ours that
makes it not work for you. But you haven't mentioned anything about your
setup, what your externals look like, where you created the branch from
(WC, HEAD, revision), ...

> *Bug3: branching a specific revision shows externals from the latest
> version in the ‘Branch/Tag’ dialog.*
>
> Same dialog as above.
>
> When I want to make a brache of , lets say revision 1 of my source, the
> ‘Set explicit revisions for these externals’ part fo the dialog shows
> all externals from the latest version of my source.
>
> I expected it to show the externals i had at the revision i wanted to
> checkout (in my case revision 1 which didn’t contain any externals)

Sorry, but that's not gonna happen: the external revisions are gathered
from the working copy, and even that is an expensive operation. Now
imagine we had to gather those from the repository at your specified
revision! You'd have to wait several minutes, maybe even hours before we
had all the required information.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2908006
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-01-11 20:56:28 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.