From nobody Tue Jun 08 19:42:02 2021 X-Original-To: freebsd-arm@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 10E8B5D15DF; Tue, 8 Jun 2021 19:42:16 +0000 (UTC) (envelope-from SRS0=emw9=LC=FreeBSD.org=otis@ns2.wilbury.net) Received: from ns2.wilbury.net (ns2.wilbury.net [92.60.51.55]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "svc.wilbury.net", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4G00xg6Rp0z4dLL; Tue, 8 Jun 2021 19:42:15 +0000 (UTC) (envelope-from SRS0=emw9=LC=FreeBSD.org=otis@ns2.wilbury.net) Received: from smtpclient.apple (gw-upc.owhome.net [188.167.168.254]) (Authenticated sender: juraj@lutter.sk) by svc.wilbury.net (Postfix) with ESMTPSA id 697BE45CF18; Tue, 8 Jun 2021 21:42:03 +0200 (CEST) Content-Type: text/plain; charset=utf-8 List-Id: Porting FreeBSD to ARM processors List-Archive: https://lists.freebsd.org/archives/freebsd-arm List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arm@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\)) Subject: Re: 14-CURRENT/aarch64 build problem From: Juraj Lutter In-Reply-To: <20210608193805.GA24803@www.zefox.net> Date: Tue, 8 Jun 2021 21:42:02 +0200 Cc: freebsd-arm@freebsd.org, freebsd-current Content-Transfer-Encoding: quoted-printable Message-Id: References: <12319609-40E7-429A-B290-9C01B0A8ACDC@FreeBSD.org> <20210608193805.GA24803@www.zefox.net> To: bob prohaska X-Mailer: Apple Mail (2.3654.100.0.2.22) X-Spam-Status: No, score=-0.7 required=5.0 tests=BAYES_00,KHOP_HELO_FCRDNS, SPF_HELO_NONE,SPF_SOFTFAIL,TW_NZ,TW_ZF autolearn=no autolearn_force=no version=3.4.5 X-Spam-Checker-Version: SpamAssassin 3.4.5 (2021-03-20) on ns2.wilbury.net X-Rspamd-Queue-Id: 4G00xg6Rp0z4dLL X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N > On 8 Jun 2021, at 21:38, bob prohaska wrote: >=20 > FWIW, same problem seen here. In an added twist, git pull (hoping for > a fix) fails also: >=20 > 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' > =46rom 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) >=20 > 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 =E2=80=94 Juraj Lutter otis@FreeBSD.org