git/list[1] front-page[2] threads[3] people[4] search[5] about
 

issues(?) installing git-lfs via fedora "dnf" command

From
Robert P. J. Day <rpjday@crashcourse.ca>
Date
May 21, 2018, 10:31 UTC
Message-ID
<alpine.LFD.2.21.1805210625410.6679@localhost.localdomain>
  first, i realize this is almost entirely a fedora packaging issue
and i'm planning on reporting it there, but i just want to make sure
i'm not doing something stupid.
  knowing nothing about the git-lfs package, i thought i would install
it and just poke around out of sheer curiosity, so on my fully-updated
fedora 28 system, i ran:
  $ sudo dnf install git-lfs

which did in fact install that package, but also generated (abridged version):

  ... snip ...
  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"
  Git LFS initialized.
    Verifying        : git-lfs-2.4.0-1.fc28.x86_64
  Installed:
    git-lfs.x86_64 2.4.0-1.fc28

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?

rday
Next: Jonathan Nieder
Message 1 of 5 in “issues(?) installing git-lfs via fedora "dnf" command”
  1. Robert P. J. DayMay 21, 2018
  2. Jonathan NiederMay 21, 2018
  3. Robert P. J. DayMay 21, 2018
  4. Jonathan NiederMay 21, 2018
  5. Robert P. J. DayMay 21, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.