Hello,
I finally have git annex working on my NAS (QNAP TS-119P II) thanks to the stand-alone arm pre-build package.
I've just extracted all the files on my NAS and I've linked all the exec files from the git-annex.linux folder to links placed in a path folder, so that I can run git annex everywhere on the NAS.
[~] # git annex version
git-annex version: 5.20140528-g92a0591
build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus DesktopNotify XMPP DNS Feeds Quvi TDFA CryptoHash
key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier ddar hook external
Now I'm trying to set it up as an SSH remote of my laptop repository, but I get this error:
git clone ssh://admin@nas:/share/HDA_DATA/myDir ./
Cloning into '.'...
admin@nas's password:
sh: git-upload-pack: command not found
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
I've checked that git-upload-pack is available both on my laptop and on the NAS and the "myDir" folder is supposed to be readable for the admin user on the NAS, even if the user I use on the laptop and on the NAS for git annex is different from the one I use to login. In fact, if I try to scp files from the annex folder then I don't get any permissions error.
scp admin@192.168.132.66:/share/HDA_DATA/myDir/* ./
admin@192.168.132.66's password:
doctest 100% 5 0.0KB/s 0.0KB/s 00:00
doctest2 100% 51 0.1KB/s 0.1KB/s 00:01
Is there something else I should look at, in order to fix it and make it work?
Thanks, Fabio
How did you set your PATH? Note that the bash shell provides a lot of dotfiles which you can set the PATH in -- and reuses to read any single one of them when a noninteractive login is made to run a command.
It might help to install git on the NAS. It's included in the git-annex tarball, but not in a way that will put it on PATH; only in a way that will let git-annex use it.
Actually I didn't set the PATH: I've just sim-linked executable files from git-annex stand-alone folder to a directory that was in my PATH already.
It was installed, bud I've removed it because it was "conflicting" with the one used by git-annex. That is, when I ran any "git annex ..." command, git was complaining it could not find git-annex (because my nas was running the installed git binary file). Without git, I don't have this conflict anymore and I can effectively use git-annex when I'm logged in my NAS, but I still can't add it as an SSH remote.
I don't think it was a good idea to remove git from the NAS. To set up a git remote, you necessarily need to have git installed on the remote.
git annexshould work as long as git-annex is somewhere in PATH -- unless your build of git is very strange and does not check PATH for git-foo commands. Even if this was the case, you could rungit-annexinstead.First of all, I understand this is more a nas-related issue rather than a git-annex-related one, so thank you for your support and valuable software.
But I'm still struggling with this error.
Now I've reinstalled git on the NAS and, as previously, I can run every git command when I'm logged in. But when I try to sync my PC with the git remote on the NAS, then I get this error:
Can this be really related to some access right? What user is git annex using when syncing with an SSH remote (e.g. admin) ? the one I specified when setting up the remote? where is it complaining about git-upload-pack non found, on the nas or on the PC I'm syncing from?
git-upload-pack is a git command, which is not present in PATH on your NAS when git sshes in and tries to run it.
Hello Fabio, I came across this posting from you one year ago. Since I'm also using a QNAP NAS for hosting several of my git-annex repos, it would be very valuable to hear some details about your setup. My setup currently consists of a virtual machine hosted on the NAS with an ordinary linux, nothing special. Would love to have git-annex installed on the NAS operating system rather, which is unfortunately not that easy.
Even in case you may not have been able to solve the issue described in this thread, can you maybe tell for example how you solved the issue of the QNAP operating system purging self-installed software? Or how you managed to let the pre-installed SSH daemon let other users than "admin" log-in?
Probably we're the first ones ever trying this, so it would be very useful to collect all about QNAP NAS and the usage of git-annex on these devices.
Hello Torpidus, I've never managed to get SSH working properly on my NAS because of the issues you have reported and so I eventually gave up with using git-annex on it. But I'm back here every now and then to check how this wonderful software is going on and if anyone has made it work on my NAS