Poul-Henning Kamp is working with me on some GBDE fixes. Which means he sends me patches and says “Here, try this,” along with very valuable exposition on how GBDE works and the threat model it applies to. This means I’m updating frequently.
My usual update process is:
# cd /usr/src
# make update && make -j8 buildworld && make -j8 kernel && reboot
Half a second after typing this, I realized I’d forgotten to apply PHK’s latest patch. I hit CTRL-C during the make update before building an unsuitable userland. I need to do the source update, apply the patch, and then build everything.
# make update
--------------------------------------------------------------
>>> Updating /usr/src using Subversion
--------------------------------------------------------------
svn: E155004: Run 'svn cleanup' to remove locks (type 'svn help cleanup' for det
ails)
svn: E155004: Working copy '/usr/src' locked.
svn: E155004: '/usr/src' is already locked.
*** Error code 1
Stop.
make[1]: stopped in /usr/src
*** Error code 1
Fine. svn cleanup it is. But wait–I don’t have svn installed!
As a matter of principle, I don’t want to install svn on this test box. svnlite is what FreeBSD offers to users, so it should be able to handle everything.
The good news is, svnlite also have a cleanup feature.
# svnlite cleanup
# make update
And the update proceeds as I would hope.
Is this worth a PR to get the error message changed? Dunno. What do you think?
Now all I must do is master all the GBDE wisdom PHK dumped in my brain…