trac-admin resync failure

[tjb@…]

Ran trac-admin resync for a trac installation scoped to part of our subversion repository.

trac-admin reported:

Resyncing repository history... 
Command failed: No changeset 17437 in the repository

I collected a trac.log at the DEBUG log level, a subversion log around the affected revisions, and the full output of trac-admin.

We are running trac-0.11.5-stable, subversion 1.5.6, apache 2.2 on a Ubuntu 8.04 server.

[tjb@…]

trac-admin output

[tjb@…]

trac log, DEBUG level

[tjb@…]

Subversion log of affected path

[tjb@…]

Our trac instance is scoped to /projects/PAR. Looking at the svn.log, I would think it was significant that the path was created(rev 17435), then deleted(rev 17436), then recreated again(rev 17551).

At some point in the past, this must have worked, as we had trac history on this project until I ran the resync today.

I have to admit that this is a pathological case, but unfortunately we (in our repository) are stuck with it.

[Christian Boos]

Can you try reverting [8184], to see if it makes a difference?

[tjb@…]

Our server is not connected to the internet, so I install updates by periodically updating to an internet connected machine, and transferring to the server. I do keep a history of previous installations, the most recent I have prior to r8195 was r8177.

I reverted to r8177, and the resync works fine now. I can checkout the last stable prior to 8184 if you like, and be more specific.

[Remy Blank]

This is very likely a side-effect of the fix from #5640. I'll revert [8184] on 0.11-stable for now and propose a better fix, now that I know when it's failing.

[Remy Blank]

I have reverted [8184] in [8198], which should fix this issue. Would it be possible for you to test the following items:

• Update to [8198] and ensure that this issue is actually fixed.

• Apply 5640-hide-forbidden-changesets-r8198.2.patch​ on top of [8198], and check that everything still works as expected.

[anonymous]

Replying to rblank:

I have reverted [8184] in [8198], which should fix this issue. Would it be possible for you to test the following items:

• Update to [8198] and ensure that this issue is actually fixed.

• Apply 5640-hide-forbidden-changesets-r8198.2.patch​ on top of [8198], and check that everything still works as expected.

I updated to [8198], and the resync works OK. I applied the patch attachment, and the resync still works OK.

I checked the Timeline and looked in the trac log for anything unusual, all seems OK. Thanks.

[Remy Blank]

Ok, thanks for testing. So [8198] closes this issue, and the discussion continues in #5640. I would suggest you re-update to a clean copy of [8198], without the patch, as we may not keep it.

And sorry for the trouble that [8184] has caused!