git-lfs-authenticate not found

[topyra]

Is this a new Bug?

• I checked that the bug hasn't been reported before

Package Name

git

Package Version

2.48.1-34

Device Model

DS418j

Device Architecture

AArch64 (ARMv8)

Firmware Version

DSM 6.2.4-25556 Update 6

What happened?

When trying to commit (from my Windows host) an LFS file to repo got an error message:

$ git push
batch request: sh: git-lfs-authenticate: command not found: exit status 127
error: failed to push some refs to 'ssh://192.168.0.3/volume1/git/myrepo.git'
$ git --version
git version 2.48.1.windows.1

Maybe it is configuration issue - internet says that missing git-lfs-authenticate is used to reach LFS vis ssh, but it seems to be default setup, for clean "out of box" configuration.

Packet seems to work (for non-lfs files there is no issues):
'dysk' is my Synology NAS

hellfire@dysk:/usr/local/bin$ git --version
git version 2.48.1
hellfire@dysk:/usr/local/bin$ git-lfs --version
git-lfs/3.6.1 (GitHub; linux arm64; go 1.23.5)
hellfire@dysk:/usr/local/bin$ which git
/usr/local/bin/git
hellfire@dysk:/usr/local/bin$ which git-lfs
/usr/local/bin/git-lfs
hellfire@dysk:/usr/local/bin$ ls -l /usr/local/bin/git*
lrwxrwxrwx 1 root root 32 Feb 23 01:21 /usr/local/bin/git -> /var/packages/git/target/bin/git
lrwxrwxrwx 1 root root 42 Feb 23 01:21 /usr/local/bin/git-cvsserver -> /var/packages/git/target/bin/git-cvsserver
lrwxrwxrwx 1 root root 36 Feb 23 01:21 /usr/local/bin/git-lfs -> /var/packages/git/target/bin/git-lfs
lrwxrwxrwx 1 root root 45 Feb 23 01:21 /usr/local/bin/git-receive-pack -> /var/packages/git/target/bin/git-receive-pack
lrwxrwxrwx 1 root root 38 Feb 23 01:21 /usr/local/bin/git-shell -> /var/packages/git/target/bin/git-shell
lrwxrwxrwx 1 root root 47 Feb 23 01:21 /usr/local/bin/git-upload-archive -> /var/packages/git/target/bin/git-upload-archive
lrwxrwxrwx 1 root root 44 Feb 23 01:21 /usr/local/bin/git-upload-pack -> /var/packages/git/target/bin/git-upload-pack
hellfire@dysk:/usr/local/bin$ ls -l /var/packages/git/target/bin/
total 28520
-rwxr-xr-x 143 root root  3171984 Jan 19 16:41 git
-rwxr-xr-x   2 root root   163772 Jan 19 16:40 git-cvsserver
-rwxr-xr-x   1 root root 11772120 Jan 19 16:41 git-lfs
-rwxr-xr-x 143 root root  3171984 Jan 19 16:41 git-receive-pack
-rwxr-xr-x   2 root root  1766992 Jan 19 16:41 git-shell
-rwxr-xr-x 143 root root  3171984 Jan 19 16:41 git-upload-archive
-rwxr-xr-x 143 root root  3171984 Jan 19 16:41 git-upload-pack
-rwxr-xr-x   1 root root   979776 Jan 19 16:41 openssl
-rwxr-xr-x   2 root root  1812536 Jan 19 16:41 scalar

Reproduction steps

1. on NAS:
   mkdir myrepo.git
   cd myrepo.git
   git init --bare

2. on Windows:
   $ mkdir myrepo
   $ cd myrepo
   $ git init
   $ git lfs track "*.bin"

topyr@DESKTOP-NR5FSEB MINGW64 /d/test/myrepo (master)
$ git lfs track ".bin"
git add .gitattributes # Commit the LFS tracking rules
Tracking ".bin"

topyr@DESKTOP-NR5FSEB MINGW64 /d/test/myrepo (master)
$ git remote add origin ssh://hellfire@192.168.0.3/volume1/git/myrepo.git

topyr@DESKTOP-NR5FSEB MINGW64 /d/test/myrepo (master)
$ fsutil file createnew test.bin 1048576
File D:\test\myrepo\test.bin is created

topyr@DESKTOP-NR5FSEB MINGW64 /d/test/myrepo (master)
$ echo "Hello World" > README.md

git add .
git commit -m "Initial commit with LFS and test files"
git push -u origin master

$ git push
Remote "origin" does not support the Git LFS locking API. Consider disabling it with:
$ git config lfs.https://192.168.0.3/volume1/git/myrepo.git/info/lfs.locksverify false
batch request: sh: git-lfs-authenticate: command not found: exit status 127
error: failed to push some refs to 'ssh://192.168.0.3/volume1/git/myrepo.git'

topyr@DESKTOP-NR5FSEB MINGW64 /d/test/myrepo (master)
$ git config lfs.https://192.168.0.3/volume1/git/myrepo.git/info/lfs.locksverify false

topyr@DESKTOP-NR5FSEB MINGW64 /d/test/myrepo (master)
$ git push
batch request: sh: git-lfs-authenticate: command not found: exit status 127
error: failed to push some refs to 'ssh://192.168.0.3/volume1/git/myrepo.git'

...

Install Log

2025/02/23 00:06:50 install git 2.48.1-34 Begin preinst
2025/02/23 00:06:50 Begin initialize_variables
2025/02/23 00:06:50 End initialize_variables
2025/02/23 00:06:50 ===> Step preinst. STATUS=INSTALL USER= GROUP= SHARE_PATH=
2025/02/23 00:06:50 install git 2.48.1-34 End preinst ret=[0]
2025/02/23 00:06:50 install git 2.48.1-34 Begin /bin/rm -rf /volume1/@appstore/git
2025/02/23 00:06:50 install git 2.48.1-34 End /bin/rm -rf /volume1/@appstore/git ret=[0]
2025/02/23 00:06:50 install git 2.48.1-34 Begin /bin/mv -f /volume1/@tmp/pkginstall/package /volume1/@appstore/git
2025/02/23 00:06:50 install git 2.48.1-34 End /bin/mv -f /volume1/@tmp/pkginstall/package /volume1/@appstore/git ret=[0]
2025/02/23 00:06:50 install git 2.48.1-34 Begin /bin/rm -rf /var/packages/git
2025/02/23 00:06:50 install git 2.48.1-34 End /bin/rm -rf /var/packages/git ret=[0]
2025/02/23 00:06:50 install git 2.48.1-34 Begin /bin/mkdir -p /var/packages/git
2025/02/23 00:06:50 install git 2.48.1-34 End /bin/mkdir -p /var/packages/git ret=[0]
2025/02/23 00:06:50 install git 2.48.1-34 Begin /bin/mv -f /volume1/@tmp/pkginstall/INFO /var/packages/git/INFO
2025/02/23 00:06:50 install git 2.48.1-34 End /bin/mv -f /volume1/@tmp/pkginstall/INFO /var/packages/git/INFO ret=[0]
2025/02/23 00:06:50 install git 2.48.1-34 Begin /bin/rm -rf /var/packages/git/scripts
2025/02/23 00:06:50 install git 2.48.1-34 End /bin/rm -rf /var/packages/git/scripts ret=[0]
2025/02/23 00:06:50 install git 2.48.1-34 Begin /bin/mv -f /volume1/@tmp/pkginstall/scripts /var/packages/git/scripts
2025/02/23 00:06:51 install git 2.48.1-34 End /bin/mv -f /volume1/@tmp/pkginstall/scripts /var/packages/git/scripts ret=[0]
2025/02/23 00:06:51 install git 2.48.1-34 Begin /bin/rm -rf /var/packages/git/conf
2025/02/23 00:06:51 install git 2.48.1-34 End /bin/rm -rf /var/packages/git/conf ret=[0]
2025/02/23 00:06:51 install git 2.48.1-34 Begin /bin/mv -f /volume1/@tmp/pkginstall/conf /var/packages/git/conf
2025/02/23 00:06:51 install git 2.48.1-34 End /bin/mv -f /volume1/@tmp/pkginstall/conf /var/packages/git/conf ret=[0]
2025/02/23 00:06:52 install git 2.48.1-34 Begin postinst
2025/02/23 00:06:52 Begin initialize_variables
2025/02/23 00:06:52 End initialize_variables
2025/02/23 00:06:52 ===> Step postinst. STATUS=INSTALL USER= GROUP= SHARE_PATH=
2025/02/23 00:06:52 Begin save_wizard_variables
2025/02/23 00:06:52 End save_wizard_variables
2025/02/23 00:06:52 install git 2.48.1-34 End postinst ret=[0]
2025/02/23 00:06:55 install git 2.48.1-34 Begin start-stop-status start
2025/02/23 00:06:55 install git 2.48.1-34 End start-stop-status start ret=[0]
2025/02/23 00:06:56 install git 2.48.1-34 Begin /bin/rm -rf /volume1/@tmp/pkginstall
2025/02/23 00:06:56 install git 2.48.1-34 End /bin/rm -rf /volume1/@tmp/pkginstall ret=[0]
2025/02/23 01:18:15 (system) trigger git 2.48.1-34 Begin start-stop-status stop
2025/02/23 01:18:15 (system) trigger git 2.48.1-34 End start-stop-status stop ret=[0]
2025/02/23 01:21:15 (system) trigger git 2.48.1-34 Begin start-stop-status start
2025/02/23 01:21:15 (system) trigger git 2.48.1-34 End start-stop-status start ret=[0]

Service Log

nothing here:

$ ls -l /var/packages/git/var/
total 0

Other Logs

[ymartin59]

Hello,

I am wondering what you expect to achieve with Git LFS... without configuring your LFS backend storage properly before any push tentative.

The Git package created for DSM does not support LFS storage on its own as "a git server".

I propose to first clone a GitHub repository and try to push a LFS file: https://docs.github.com/en/repositories/working-with-files/managing-large-files/configuring-git-large-file-storage
which will confirm if a component is lacking in Git package "as a git client".

[hgy59]

The Git package created for DSM does not support LFS storage on its own as "a git server".

Yes, the synocommunity git package does not provide a git server, it is a git client tools package.

@topyra If you want to run a git server under DSM, you can try the gitea package. (for how to setup git lfs in gitea see https://docs.gitea.com/administration/git-lfs-setup)
And there is a git server package by synology, but I guess it does not support git-lfs at all.

[topyra]

Got it... Thanks
I was thinking (without clear reason) that git package contains git server, rather than git client.
I think it was intuition that devices like NAS works rather as servers.