Confusing error message when repository_dir has changed.

[anonymous]

The error one gets says:

TracError: The 'repository_dir' has changed, a 'trac-admin resync' operation is needed.

However one need to do trac-admin <trac-env> resync.

[Christian Boos]

Probably even better would be a link to the relevant documentation.

[Christian Boos]

Let's not change that on 0.11 and check how this behaves on multirepos.

[Christian Boos]

Unless I'm mistaken, there's no support for tracking repository moves in MultiRepos.

Several options:

• expand repository add <repos> <dir> so that it supports changing <dir> if <repos> already exists
  • if the uuid is the same, that was simply a move, nothing else changes
  • otherwise, there's a resync
• add a new repository set <repos> <key> <value>, in order to set metadata values
  • this can be reused for other things in the future, like setting the url (#1781), description, …
  • depending on the <key>, different side-effects would be triggered. For repository_dir, this would be the resync if the uuid changed

We could have similar features in the WebAdmin, but most important is to get them first in trac-admin.

[Remy Blank]

Replying to cboos:

Unless I'm mistaken, there's no support for tracking repository moves in MultiRepos.

The repository path is editable in the admin panel, and when it changes, the notice suggests running trac-admin $ENV repository resync.

And changing the path without resyncing seems to work at first (when the repository has only moved), but it will actually fail at the next sync attempt, as repository_dir keeps track of the old name. So changing the directory currently requires a resync. We could remove that check, or replace it with a check on a repository ID.

add a new repository set <repos> <key> <value>, in order to set metadata values

I have done that in [8467], but currently the command doesn't have any side-effects, it only gives the same warnings as the admin panel.

• depending on the <key>, different side-effects would be triggered. For repository_dir, this would be the resync if the uuid changed

The thing is, we currently don't have a backend-neutral way of checking if two repositories are the same. svn_fs has a UUID, cache doesn't have it, and neither does hg. So how would you know that a change in dir is a relocation as opposed to a repository change?

Oh wait, we do have get_base(), which in Subversion's case contains the UUID. But scoped repositories will have the same base as unscoped ones.

[Remy Blank]

Oh, and concerning the original request, [8468] fixes the error message.

[Remy Blank]

I still haven't found a good way of finding out wheter two repositories are the same or not. So in the current state, we require a resync after a repository move. The original issue has been fixed, and both the admin panel and trac-admin allow changing repository metadata, so I'm closing this as fixed.