Subversion commit rendered environment useless via python frontend

[passport@…]

In directory 'trunk' i created a folder in subversion via my client (TortoiseSVN) named 'something_something'. I then deleted the newly created folder to import a complete directory named 'something_something' into 'trunk'.

When i did this, the entire trac environment threw up with the attached Python Traceback.

[passport@…]

Just error occured on 0.10.3 i then upgraded to 0.10.4 the problem persisted. I then ran trac-admin resync and now environment seems fine again.

[eblot]

What do you mean by deleted: you've removed a directory in your working copy of the trunk, then commit this change to the repository? Can you describe the actual steps:

1. check out a fresh working copy of the trunk
2. create something_something in /trunk
3. svn-add something_something
4. svn-commit the change to the repository
5. svn-delete something_something
6. svn-commit this change (?)
7. create something_something in the same directory as the previous something_something dir
8. add files and subdirectories in something_something
9. svn-add something_something
10. svn-commit the changes to the repository
11. browse the repository w/ Trac

Is that it?

[passport@…]

I will try to be more precise. It's kind of hard to know exactly which commands where executed since i used the gui tool TortoiseSVN.

I did not do a checkout since TortoiseSVN got something called "Repository Browser" in the browser, one can create/delete and import directories and or files.

In the repo browser i did:

'Create Folder' named 'something' in 'trunk' 'Delete Folder' named 'something' in 'trunk' 'Import Folder' named 'something' to 'trunk/something'

TortoiseSVN does this without a checkout, so I do not know precisely which svn commands where executed. I tried to repoduce the error after the upgrade but I can't seem to reproduce it.

[cboos]

Replying to passport@safl.dk:

... I tried to repoduce the error after the upgrade but I can't seem to reproduce it.

Yes, I think this was simply a duplicate of #4586, fixed in 0.10.4.