Sorry for not having noticed in the changelogs that the patch was introduced in nautilus 1:2.22.5.1-0ubuntu2
I was already using it with all hardy-updates. However, since I was still seeing that behaviour, I tried to build nautilus from source. This is the relevant output of dpkg-buildpackage:
The 91_svn_change_new_mounts_correctly_displayed.patch file actually patches itself, instead of the file which was supposed to (nautilus-mime-actions.c).
Sorry for not having noticed in the changelogs that the patch was introduced in nautilus 1:2.22.5.1-0ubuntu2
I was already using it with all hardy-updates. However, since I was still seeing that behaviour, I tried to build nautilus from source. This is the relevant output of dpkg-buildpackage:
... svn_dont_ allow_recursive _copies. patch private/ nautilus- file-operations .c
Applying patch 90_from_
patching file libnautilus-
Hunk #1 succeeded at 3352 (offset 131 lines).
Hunk #2 succeeded at 3412 (offset 131 lines).
Hunk #3 succeeded at 3974 (offset 131 lines).
Applying patch 91_svn_ change_ new_mounts_ correctly_ displayed. patch patches/ 91_svn_ change_ new_mounts_ correctly_ displayed. patch
patching file debian/
Applying patch 99_ltmain_ as-needed. patch
patching file ltmain.sh
...
The 91_svn_ change_ new_mounts_ correctly_ displayed. patch file actually patches itself, instead of the file which was supposed to (nautilus- mime-actions. c).