Den lör 3 sep. 2022 kl 08:31 skrev Barry <ba...@barrys-emacs.org>:
>
>
> > On 2 Sep 2022, at 15:09, Nathan Hartman <hartman.nat...@gmail.com>
> wrote:
> >
> >
> >>
> >> On Mon, Aug 29, 2022 at 5:36 AM Barry Scott <ba...@barrys-emacs.org>
> wrote:
> >> I had a pysvn user report that they cannot detect that a wc is locked.
> >>
> >> What I found is that I get that info and indeed locked == 0.
> >>
> >> This is because there is no code in svn_wc__status2_from_3 to
> >> copy locked value from old_status->locked into *status->locked.
> >
> > Hi Barry,
> >
> > Are you able to check whether the attached one-line patch fixes the
> > issue?
>
> Yep, I build subversion myself, so can add your patch and test.
>
> >
> > Caveat: I intended to implement a regression test and verify the fix
> > with the test suite but haven't gotten around to it yet. For now the
> > fix is on a branch:
> > https://svn.apache.org/repos/asf/subversion/branches/issue-4908
> >
> > Notes: While investigating this, I discovered that we are also not
> > copying file_external. It appears that all other fields are being
> > copied.
>
> How do I force the working copy into the locked state?
> I did it by accident before and did the debug with that,
>
Sorry if I'm just copying from the source, but there is a note in svn_wc.h:
typedef struct svn_wc_status2_t
{
[...]
/** a directory can be 'locked' if a working copy update was interrupted.
*/
svn_boolean_t locked;
[...]
Maybe this helps figuring out how to the the WC "locked" (I didn't try it
myself).
Kind regards,
Daniel
