Re: svn unlock all files locked by a specific user

[Sean McBride]

Thanks to you both.

I ended up doing this on the server:

```
svnadmin lslocks /usr/local/repositories/reponame/ | grep -B3 "Owner: 
alice" | grep "Path: " | sed 's/^Path: \//svn unlock --force "/' | sed 
's/$/"/' > ~/svnunlock.sh

```

then running that result on my own computer against my local working 
copy.


Sean

Re: ./configure --with-berkeley-db gives incomplete message

[Michael Osipov]

On 2025/03/18 23:27:58 Yasuhito FUTATSUKI wrote:
> Hello,
> 
> On 2025/03/19 3:21, Michael Osipov wrote:
> > On 2025/03/18 16:41:07 Nathan Hartman wrote:
> >> On Tue, Mar 18, 2025 at 10:09 AM Michael Osipov  
> >> wrote:
> >>
> >>> Folks,
> >>>
> >>> the configure script for 1.14.5 gives me:
> >>>   --with-berkeley-db[=HEADER:INCLUDES:LIB_SEARCH_DIRS:LIBS]
> >>>   The Subversion Berkeley DB based filesystem
> >>> library
> >>>   requires Berkeley DB $db_version or
> >>> $db_alt_version.
> >>>   If you specify `--without-berkeley-db', that
> >>> library
> >>>   will not be built. If you omit the argument of
> >>> this
> >>>   option completely, the configure script will use
> >>>   Berkeley DB used by APR-UTIL.
> >>>
> >>> $db_alt_version is defined with "5.x", but not rendered. $db_version is
> >>> set dynamically with a case and is valid as well.
> >>>
> >>> Maybe someone wants to check why they are not interpolated for help 
> >>> output.
> >>>
> >>> Michael
> >>>
> >>
> >> Hi Michael,
> >>
> >> Did this same invocation work as expected with an earlier SVN release? If
> >> so, which release was that? That will help immensely...
> > 
> > I dare to say that it has never worked. Tried 1.10.x and 1.11.x, both have 
> > the same issue.
> 
> As far as I saw subversion-1.6.0.tar.bz2, it uses autoconf 2.63 and
> help string was expanded to "cat <<\_ACEOF ..." so the shell variables
> cannot be replaced.

2.72 isn't any better here and https://stackoverflow.com/a/27466219/696632 
doesn't work either.

Docs say 
(https://www.gnu.org/software/autoconf/manual/autoconf-2.68/html_node/Pretty-Help-Strings.html):
> Macro expansion is performed on the first argument. However, the second
> argument of AS_HELP_STRING is treated as a whitespace separated list of
> text to be reformatted, and is not subject to macro expansion. Since it
> is not expanded, it should not be double quoted. See Autoconf Language,
> for a more detailed explanation. 

So it has never worked. I tried to play around a bit with my humble knowledge, 
but was not successful. My assumption is that the help string is built during 
autoconf time while the variables are only available at configuration time.

M

svn unlock all files locked by a specific user

[Sean McBride]

Hi all,

Is there an easy way to force unlock all files currently locked by a specific 
user?

Consider an employee that leaves, and needing to then unlock anything she still 
had locked.

Thanks,

Sean

Re: svn unlock all files locked by a specific user

[Andreas Stieger]

On 2025-03-19 19:10, Sean McBride wrote:

Is there an easy way to force unlock all files currently locked by a specific 
user?



It's easy enough to get a full list:

https://svnbook.red-bean.com/nightly/en/svn.advanced.locking.html#svn.advanced.locking.break-steal

grep -B3 [...], grep, awk/cut,... should be straightforward.

Andreas