> On 8 Jun 2021, at 21:38, bob prohaska <f...@www.zefox.net> wrote:
>
> FWIW, same problem seen here. In an added twist, git pull (hoping for
> a fix) fails also:
>
> root@www:/usr/src # git pull
> error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/legacy':
> 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create
> 'refs/remotes/freebsd/vendor/openzfs/legacy'
> From https://git.freebsd.org/src
> ! [new branch] vendor/openzfs/legacy ->
> freebsd/vendor/openzfs/legacy (unable to update local ref)
> error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/master':
> 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create
> 'refs/remotes/freebsd/vendor/openzfs/master'
> ! [new branch] vendor/openzfs/master ->
> freebsd/vendor/openzfs/master (unable to update local ref)
> error: cannot lock ref 'refs/remotes/freebsd/vendor/openzfs/zfs-2.1-release':
> 'refs/remotes/freebsd/vendor/openzfs' exists; cannot create
> 'refs/remotes/freebsd/vendor/openzfs/zfs-2.1-release'
> ! [new branch] vendor/openzfs/zfs-2.1-release ->
> freebsd/vendor/openzfs/zfs-2.1-release (unable to update local ref)
>
> Is this a problem at my end, or the server's end?
This already has been documented, as the old openzfs branch has been
renamed/moved.
$ git remote prune freebsd
$ git pull
See: https://lists.freebsd.org/archives/freebsd-git/2021-June/000015.html
otis
—
Juraj Lutter
o...@freebsd.org
