From nobody Tue Oct 01 07:04:47 2024 X-Original-To: git@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 4XHpqB3T4wz5XNpH for ; Tue, 01 Oct 2024 07:05:10 +0000 (UTC) (envelope-from dch@skunkwerks.at) Received: from fout-a8-smtp.messagingengine.com (fout-a8-smtp.messagingengine.com [103.168.172.151]) (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 did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4XHpqB0Y3zz4bBL; Tue, 1 Oct 2024 07:05:10 +0000 (UTC) (envelope-from dch@skunkwerks.at) Authentication-Results: mx1.freebsd.org; none Received: from phl-compute-02.internal (phl-compute-02.phl.internal [10.202.2.42]) by mailfout.phl.internal (Postfix) with ESMTP id E51D61381F46; Tue, 1 Oct 2024 03:05:08 -0400 (EDT) Received: from phl-imap-02 ([10.202.2.81]) by phl-compute-02.internal (MEProxy); Tue, 01 Oct 2024 03:05:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=skunkwerks.at; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:subject:subject:to:to; s=fm3; t=1727766308; x=1727852708; bh=XXxbJQ50KmEr3xNIEVlPymi6MoAV607K +p1dvSAlYEk=; b=nLSYRH4b3Mbf2ukahQ56D9V6TR3yMv5mklYIoTpKnpId0G4+ s/h7LEMqmhCGDLoOQGszIizx5KoIJQzldqUjFo0rAdU4PC1bZY5af/9u+x6OpX7X 4QeZPWexKasR3iBNA39RkZ2M95Ix/tHtTApaMzK0vRg/4nRemD5uSDSjQPAezsdU xQr49dHK7U+2jg0DR9UMTM5dvQC1EYUwknNX06a+/Owrtk5CJ6gLgoqHo0IgNci4 KMEvrF/u7lmTtBWgbgbsadJsTvzO8/uxc+4QbV9lUnEXx5u+2CIblgIOMhqT0zfo To8iU4yVBoeZAcpNfjKkoPmeB/LcSW6StkND1g== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1727766308; x= 1727852708; bh=XXxbJQ50KmEr3xNIEVlPymi6MoAV607K+p1dvSAlYEk=; b=b qtGVfwr0sieknJO7sC3JCEXcNJ3yDkq3OPHWXhkf3FahVGTA3ghtISYqE4WoLwGi jby1SSmA7WpE4+gtw+EDiEgl1dCMwVuWSDEI0s/CZCO6Rc8Tu9DTBZtyy/xqnb5L RvFs8t4P/PbaMnMzeqyQ9InfpN+yOZTOI+hr2zzw6RDkj4GwJbYefLvStuF4sV4f msj0lpROtaN18Je8xmFgt1wCtZgmuGor19KvNr2Bm1nttaFGFw6N+VyOclx1iDL7 osbTJhYxvbYN5ymFAJDKZw+LebHAM7b78pOidubf2Zke232qOwr/lms0RwvIfGUw IUtoAg5YkyzfrlCBZi5OA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeeftddrvdduiedgudduiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdp uffrtefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivg hnthhsucdlqddutddtmdenucfjughrpefoggffhffvvefkjghfufgtgfesthhqredtredt jeenucfhrhhomhepfdffrghvvgcuvehothhtlhgvhhhusggvrhdfuceouggthhesshhkuh hnkhifvghrkhhsrdgrtheqnecuggftrfgrthhtvghrnhepveelieeljeeifedvhfefhffh geevtdejgefgtedugfeuhfdvuddvvdduhfegteeknecuffhomhgrihhnpehfrhgvvggssh gurdhorhhgpdhgihhthhhusgdrtghomhdpghhithdqshgtmhdrtghomhdpfhgvtghhnhgv rhdrnhgvthenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhroh hmpegutghhsehskhhunhhkfigvrhhkshdrrghtpdhnsggprhgtphhtthhopedvpdhmohgu vgepshhmthhpohhuthdprhgtphhtthhopehgihhtsehfrhgvvggsshgurdhorhhgpdhrtg hpthhtohepmhhfvggthhhnvghrsehfrhgvvggsshgurdhorhhg X-ME-Proxy: Feedback-ID: ic0e84090:Fastmail Received: by mailuser.phl.internal (Postfix, from userid 501) id 2330BB00068; Tue, 1 Oct 2024 03:05:08 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface List-Id: Discussion of git use in the FreeBSD project List-Archive: https://lists.freebsd.org/archives/freebsd-git List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-git@FreeBSD.org MIME-Version: 1.0 Date: Tue, 01 Oct 2024 07:04:47 +0000 From: "Dave Cottlehuber" To: "Matthias Fechner" Cc: git@freebsd.org Message-Id: In-Reply-To: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> References: <483fb132-0d1c-443a-9b44-b7f2f087fb3d@freebsd.org> Subject: Re: Impossible to push my ports directory to my CI/CD pipeline Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:209242, ipnet:103.168.172.0/24, country:US] X-Rspamd-Queue-Id: 4XHpqB0Y3zz4bBL X-Spamd-Bar: ---- On Mon, 30 Sep 2024, at 10:09, Matthias Fechner wrote: > Dear all, > > I already tried to address that problem on the all-developer list, but=20 > it is maybe better to put it here. > I think by accident someone pushed LFS object with a commit of java/ec= lipse. on fediverse there was speculation that this is just files that look similar to git-lfs, and gitlab gets confused by them, not actually lfs files. In all cases I've seen, its been a gitlab instance that has had issues. > git remote -v > freebsd git@gitrepo.freebsd.org:ports.git (fetch) > freebsd git@gitrepo.freebsd.org:ports.git (push) > freebsd-https=C2=A0=C2=A0 https://git.freebsd.org/ports.git (fetch) > freebsd-https=C2=A0=C2=A0 https://git.freebsd.org/ports.git (push) > githubfreebsd=C2=A0=C2=A0 https://github.com/freebsd/freebsd-ports.git= (fetch) > githubfreebsd=C2=A0=C2=A0 https://github.com/freebsd/freebsd-ports.git= (push) > origin=C2=A0 git@gitlab.fechner.net:mfechner/Gitlab.git (fetch) > origin=C2=A0 git@gitlab.fechner.net:mfechner/Gitlab.git (push) > > git lfs fetch --all freebsd I'm curious why you use the `lfs` here, I guess its just to show lfs-related issues, and normally you don't use it? Anyway on a fresh checkout, this works fine: git clone -vv git@gitrepo.freebsd.org:ports.git -b main ports trying `git lfs clone ...` reports: WARNING: 'git lfs clone' is deprecated and will not be updated with new flags from 'git clone' but also has no issues. In either case, `git lfs ls-files` shows nothing. It's not clear to me how git "knows" about lfs, but there are a bunch of XDG_DIR config files that may impact this, viz: https://git-scm.com/docs/gitattributes > If I now try to push to my local repo I get: > > git push origin > Warning: untrusted X11 forwarding setup failed: xauth key data not gen= erated > Locking support detected on remote "origin". Consider enabling it with: > =C2=A0 $ git config=20 > lfs.https://gitlab.fechner.net/mfechner/Gitlab.git/info/lfs.locksverif= y true > Unable to find source for object=20 > 99a670c083e000008ee29dd972b60cbad6ade1d6ec024b30ff45f41da3d19e1d (try=20 My current thinking is there's nothing (as yet) obviously wrong with FreeBSD's git repos, but there's possibly something interacting with git= lab. Can you create a new github repo, and try pushing your ports tree to tha= t, to see if it sees the same issue? Given I can't replicate this here, perhaps there is a $SOMEWHERE}/.confi= g/git/attributes or similar /config file that influences git tooling? A+ Dave