From nobody Tue Jun 8 20:37:43 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 E35E75D5620 for ; Tue, 8 Jun 2021 20:37:49 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from gromit.dlib.vt.edu (gromit.dlib.vt.edu [128.173.49.70]) (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 "gromit.dlib.vt.edu", Issuer "Chumby Certificate Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4G029n66J1z4kTb; Tue, 8 Jun 2021 20:37:49 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from smtpclient.apple (unknown [73.99.214.146]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gromit.dlib.vt.edu (Postfix) with ESMTPSA id A68681B5; Tue, 8 Jun 2021 16:37:43 -0400 (EDT) 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: Paul Mather In-Reply-To: <3134b379-2729-05d8-df91-0cbcadc540dc@m5p.com> Date: Tue, 8 Jun 2021 16:37:43 -0400 Cc: freebsd-arm@freebsd.org, "eduardo@freebsd.org" Content-Transfer-Encoding: quoted-printable Message-Id: <21617CC8-7FC4-432F-BBDF-EF821DA4670B@gromit.dlib.vt.edu> References: <12319609-40E7-429A-B290-9C01B0A8ACDC@FreeBSD.org> <20210608193805.GA24803@www.zefox.net> <3134b379-2729-05d8-df91-0cbcadc540dc@m5p.com> To: George Mitchell X-Mailer: Apple Mail (2.3654.100.0.2.22) X-Rspamd-Queue-Id: 4G029n66J1z4kTb X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; TAGGED_RCPT(0.00)[freebsd]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On Jun 8, 2021, at 4:14 PM, George Mitchell = wrote: > On 6/8/21 3:42 PM, Juraj Lutter wrote: >>> 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 > How would this affect net/gitup users? (I'm guessing gitup would = force > the local repo into conformance with the remote repo by default.) This is what I got when I tried updating one of my -CURRENT systems = right now: =3D=3D=3D=3D=3D # gitup current # Scanning local repository... # Host: git.freebsd.org # Port: 443 # Repository Path: /src.git # Target Directory: /usr/src # Have: b5d37e5a20ab1b189499e2824dc269d998c31989 # Want: f20893853e8e6909d422f6646b706b4b6e299682 # Branch: main # Action: pull zsh: segmentation fault (core dumped) gitup current =3D=3D=3D=3D=3D Even deleting everything under /usr/src and doing "rm = /var/db/gitup/current" and re-running "gitup current" to re-clone = everything afresh results in this: =3D=3D=3D=3D=3D # gitup current # Scanning local repository... # Host: git.freebsd.org # Port: 443 # Repository Path: /src.git # Target Directory: /usr/src # Want: f20893853e8e6909d422f6646b706b4b6e299682 # Branch: main # Action: clone gitup: load_object: local file for object = 3331601f6dc50ef2c9779c1656218701b48b276c -- = /usr/src/sys/contrib/openzfs/scripts/zfs-images not found: No such file = or directory =3D=3D=3D=3D=3D So I guess "gitup" needs to be taught how to resolve this kind of = change. :-\ Cheers, Paul.=