Re: 14-CURRENT/aarch64 build problem

From: George Mitchell <george+freebsd_at_m5p.com>
Date: Tue, 8 Jun 2021 16:14:07 -0400
On 6/8/21 3:42 PM, Juraj Lutter wrote:
> 
> 
>> On 8 Jun 2021, at 21:38, bob prohaska <fbsd_at_www.zefox.net> wrote:
>>
>> FWIW, same problem seen here. In an added twist, git pull (hoping for
>> a fix) fails also:
>>
>> root_at_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
> otis_at_FreeBSD.org
> 
> 
How would this affect net/gitup users?  (I'm guessing gitup would force
the local repo into conformance with the remote repo by default.)
-- George


Received on Tue Jun 08 2021 - 20:14:07 UTC

Original text of this message