Ticket #6624 (closed defect: duplicate)
Opened 4 years ago
Last modified 4 years ago
Revision applies to directories not involved
| Reported by: | sylvain@… | Owned by: | cboos |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | version control/browser | Version: | 0.10.3 |
| Severity: | normal | Keywords: | |
| Cc: | |||
| Release Notes: | |||
| API Changes: | |||
Description
I don't know why but when I commit a file or a folder on my repository Trac browser says that another higher particular folder tree ('aFiles' at the root of the browser) is involved in the last revision but he is not.
Exemple :
http://aforge.abstraction.fr/browser
Trac says "aFiles" is involved in revision 92, but he is not and it's confirmed here :
http://aforge.abstraction.fr/changeset/92
In fact trac browser says that the aFiles folder is always part of the last revision.
I tried to resync trac environement but didn't work.
Regards.
Attachments
Change History
comment:1 Changed 4 years ago by eblot
comment:2 follow-up: ↓ 3 Changed 4 years ago by nkantrowitz
This is a feature, the rev/log on a folder will show the last change anywhere below that folder.
comment:3 in reply to: ↑ 2 ; follow-up: ↓ 8 Changed 4 years ago by eblot
Replying to nkantrowitz:
This is a feature, the rev/log on a folder will show the last change anywhere below that folder.
AFAICT, that's the point:
[92] shows that /dimdim/trunk/asw has been removed so
- /dimdim/trunk/asw,
- /dimdim/trunk,
- /dimdim,
- / folders
should be tagged (SVN bubble up). No other directory should be tagged with [92]
However, the browser pointed at / shows that /aFiles (and everything below it) is also tagged with [92]
So either there's a weird project setting, or this is definitely a bug.
comment:4 follow-up: ↓ 5 Changed 4 years ago by sylvain@…
I don't know if it helps but the trac browser points to a scope into the repository.
Repository : /var/svn
Scope : /var/svn/public/aForge
comment:5 in reply to: ↑ 4 Changed 4 years ago by eblot
Replying to sylvain@abstraction.fr:
I don't know if it helps but the trac browser points to a scope into the repository.
Repository : /var/svn
Scope : /var/svn/public/aForge
Could you dump the complete changeset log report with the svn tool ?
svn log -v -r 92 repos_url
comment:6 follow-up: ↓ 7 Changed 4 years ago by sylvain
wellington:/var/svn# svn log -v -r 92 svn://svn.abstraction.fr/public/aForge ------------------------------------------------------------------------ r92 | Absynthe | 2008-01-09 23:01:00 +0100 (mer, 09 jan 2008) | 1 line Chemins modifiés : D /public/aForge/dimdim/trunk/asw Removed file/folder ------------------------------------------------------------------------
comment:7 in reply to: ↑ 6 Changed 4 years ago by eblot
Replying to sylvain:
r92 | Absynthe | 2008-01-09 23:01:00 +0100 (mer, 09 jan 2008) | 1 line
D /public/aForge/dimdim/trunk/asw
I see no reason why /public/aForge/aFiles would have been tagged. Try to upgrade…
comment:8 in reply to: ↑ 3 Changed 4 years ago by anonymous
Replying to eblot:
Replying to nkantrowitz:
This is a feature, the rev/log on a folder will show the last change anywhere below that folder.
AFAICT, that's the point:
Whoops, ignore me then. Scoped repos were one of the things worked on during 0.10, so your original assessment is probably the best starting place. /me hangs head.
comment:9 Changed 4 years ago by cboos
- Resolution set to duplicate
- Status changed from new to closed
Duplicate of #3470.



Upgrade to release 0.10.4.
0.10.3 is known to have some flaws with version control management.