Bug #1945
Wrong revision used when scanning components of new SVN branch
Start date:
26.02.2016
Due date:
% Done:
100%
Estimated time:
origin:
Description
Again there is the problem that when copying to a branch the repo will have the right revision, but child modules will be looked up with a peg revision that is from before the copy so that the URL will not resolve.
Test:
- create branch of addon
- scan for contained modules
Related issues
Updated by