From: "Robert P. J. Day" <rpjday@crashcourse.ca>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: issues(?) installing git-lfs via fedora "dnf" command
Date: Mon, 21 May 2018 13:04:54 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.21.1805211303260.19892@localhost.localdomain> (raw)
In-Reply-To: <20180521170353.GA10623@aiede.svl.corp.google.com>
On Mon, 21 May 2018, Jonathan Nieder wrote:
> Robert P. J. Day wrote:
>
> > $ sudo dnf install git-lfs
> [...]
> > Running transaction
> > Preparing :
> > Installing : git-lfs-2.4.0-1.fc28.x86_64
> > Running scriptlet: git-lfs-2.4.0-1.fc28.x86_64
> > Error: Failed to call git rev-parse --git-dir --show-toplevel: "fatal:
> > not a git repository (or any of the parent directories): .git\n"
> [...]
> > is one supposed to be *in* a git repository when installing, because i
> > was in fact at the top level of my linux kernel source repo, so i'm
> > unclear on what that "Error" is trying to tell me. am i just being
> > clueless? is this something that i should submit as a fedora packaging
> > issue?
>
> Yes, this looks like something that should be reported as a Fedora
> packaging issue.
>
> The packager should be able to find out whether it's an issue in
> git-lfs upstream and report it to that project if it is. Git-lfs is
> not part of git.git; it's a separate project:
> https://github.com/git-lfs/git-lfs/blob/master/CONTRIBUTING.md
> I believe they use github's issue tracker to track bugs.
it would *appear* that this is a combination of both a git issue,
and a red hat packaging issue:
https://bugzilla.redhat.com/show_bug.cgi?id=1580357
https://github.com/git-lfs/git-lfs/issues/3013
rday
next prev parent reply other threads:[~2018-05-21 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 10:31 issues(?) installing git-lfs via fedora "dnf" command Robert P. J. Day
2018-05-21 17:03 ` Jonathan Nieder
2018-05-21 17:04 ` Robert P. J. Day [this message]
2018-05-21 17:14 ` Jonathan Nieder
2018-05-21 17:16 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.21.1805211303260.19892@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).