On Thu, Oct 1, 2009 at 11:17, Hyrum K. Wright <hyrum_at_hyrumwright.org> wrote:
>...
> +++ trunk/subversion/libsvn_wc/lock.c  Thu Oct  1 08:17:49 2009     (r39740)
>...
> @@ -277,8 +249,7 @@ adm_access_alloc(svn_wc_adm_access_t **a
> Â if (err)
> Â Â return svn_error_compose_create(
> Â Â Â Â Â Â Â Â err,
> - Â Â Â Â Â Â Â Â svn_wc__remove_adm_file(lock->abspath, SVN_WC__ADM_LOCK,
> - Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â scratch_pool));
> + Â Â Â Â Â Â Â Â svn_wc__db_lock_remove(db, lock->abspath, scratch_pool));
Heh. I'm guessing you want svn_wc__db_wclock_remove() here.
>...
> +++ trunk/subversion/libsvn_wc/upgrade.c     Thu Oct  1 08:17:49 2009     (r39740)
>...
> @@ -336,6 +359,18 @@ upgrade_to_wcng(svn_wc__db_t *db,
> Â SVN_ERR(svn_wc__db_upgrade_begin(&sdb, dir_abspath,
> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â this_dir->repos, this_dir->uuid,
> Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â scratch_pool, scratch_pool));
> + Â {
> + Â Â /* Unfortunately, we can't call the svn_wc__db_wclock_set() API just yet,
> + Â Â Â since the sdb isn't yet the right format. Â So we've got to do the lock
> + Â Â Â insertion manually. */
You could if this happens right after the reset_format() call a few lines below.
>...
Cheers,
-g
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=2402729
Received on 2009-10-02 03:13:57 CEST