Defect #11631

Repository links uncorreclty kept after changing repository

Added by Cassiano Monteiro almost 10 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:SCM
Target version:-
Resolution: Affected version:1.4.4

Description

This may be an unusual thing, but happened like this:

  • I had started one repository (SVN) for a project, in order to store legacy code and keep its maintenance.
  • Developers had solved some issues and committed code to that repository, linking the code to the issues (it was revision 6).

Issue linked revisions

  • For some reason, they messed up the code, so they decided to start a new repository from scratch (it would be easier than revert changes and so on).
  • So I deleted the old repository and created a new one, where they committed the last changes on the code (making it revision 2 to 4).

Repository status after restarting it

  • After that, the links of the issues were kept to the revision 6. Clicking on the revision 6 would still show the changes from the revision 6 of the old repository, even if the repository wasn't there anymore. But clicking on files or on the "diff revision" would show the error 404 "The entry or revision was not found in the repository.".

Revision 6 description after restarting the repository

After that, I tried to remove the repository settings from that project, and add it again, but I still had the same behavior.

I don't know exactly how Redmine keeps the repository information, but it seems to be storing old information on its database... Perhaps this may be solved by reloading the repository information once it's reconfigured on the project settings.

Issue_revisions.png - Issue linked revisions (8.75 KB) Cassiano Monteiro, 2012-08-14 14:01

Repository.png - Repository status after restarting it (13 KB) Cassiano Monteiro, 2012-08-14 14:01

Revision6.png - Revision 6 description after restarting the repository (12.2 KB) Cassiano Monteiro, 2012-08-14 14:01

Also available in: Atom PDF