The same here on Android 8.1.0. likely because .app was build for 5, but there is nothing newer offered on Android downloads.
So the Android Port is abandoned overall?
Finally got to check it out: so indeed hardlinking fails but not because of permissions but "link failed Cross-device link" that lib is -> /mnt/asec/ga.androidterm-1/lib which resides on a different partition (vfat, /dev/block/dm-2, ro) from /data (ext4, /dev/block/mmcblk0p10)
Comment by
http://yarikoptic.myopenid.com/
— Wed Feb 26 23:09:23 2020
Hi, I have exactly the same problem with the link that fails on my phone. However, I checked the permissions and they are as you describe on your tablet (except for the app number). At the same time, everything is fine on my tablet... The phone runs an old Cyanogenmod 7.2.0 (Android 2.3.7) while the tablet is a more recent Asus TF700T (Android 4.1.1). Let me know if you want me to run tests.
Comment by
https://www.google.com/accounts/o8/id?id=AItOawkwjBDXkP9HAQKhjTgThGOxUa1B99y_WRA
— Wed Feb 26 23:09:23 2020
I generated an rsa keypair and added them to /sd/ga-h/.ssh, yet they were overwritten. I couldn't access my annexes located on github. I couldn't login to google talk, as instructed by the web app.
Thanks for letting me know about gitlab supporting git-annex.
Comment by
joseph.rawson.works
— Wed Feb 26 23:09:23 2020
@yarikoptic, there is a process you can perform that will help me determine what's going on.
You should be able to get the git-annex app to let you into a shell. You can do this by starting the app, and then going into its configuration menu, to Preferences, selecting "Command Line", and changing it to run "/system/bin/sh"
Then when you open a new window in the git-annex app, you'll be at a shell prompt. From there, you can run:
ls -ld /data/data/ga.androidterm
I'm interested to know a) whether the directory exists and b) what permissions and owner it has. On my tablet, I get back "drwxr-x--x app_39 app_39" .. and if I run id in the shell, it tells me it's running as app_39.
My guess is the directory probably does exist, but cannot be written to by the app. If you're able to verify that, the next step will be to investigate if there is some other directory that the app can write to. It needs to be able to write to someplace that is not on the /sdcard to install itself.
Comment by
http://joeyh.name/
— Wed Feb 26 23:09:23 2020
Sorry for the delay: my android is stock Samsung-tuned Jelly beans.
Android 4.1.2
Baseband version N7000XXLSO
not sure if that would be of any use :-/ nothing in the logs (aLogcat) if I filter by annex -- should there any debug output? what should be a key to search by?
Comment by
http://yarikoptic.myopenid.com/
— Wed Feb 26 23:09:23 2020
frioux here (something messed up with myopenid or something)
So I deleted the repo on my phone (via the CLI since the web app seemed hung) and recreated it; this time making sure that I set things to manual mode ASAP. It didn't have the problem it was having before, but now what seems to have happened is that it fetches from the remote, commits to the local repo, and then immediately fetches and commits again. It looks like it's about a 4s repeat loop. Any ideas what I should do next?
Comment by
https://www.google.com/accounts/o8/id?id=AItOawnRfQArYOmDd7r2DC7DkIJFOQgqXCVcAeU
— Wed Feb 26 23:09:23 2020
ok, it eventually got the details from the remote server, but now I'm getting some other oddities. here is some of my log that shows what I am running into
Watcher crashed: addWatch: does not exist (No such file or directory) [2013-07-18 06:22:46 CDT] Watcher: warning Watcher crashed: addWatch: does not exist (No such file or directory) (scanning...) [2013-07-18 06:23:19 CDT] Watcher: Performing startup scan Watcher crashed: addWatch: does not exist (No such file or directory) [2013-07-18 06:24:28 CDT] Watcher: warning Watcher crashed: addWatch: does not exist (No such file or directory) (scanning...) [2013-07-18 06:24:31 CDT] Watcher: Performing startup scan Watcher crashed: addWatch: does not exist (No such file or directory) [2013-07-18 06:25:44 CDT] Watcher: warning Watcher crashed: addWatch: does not exist (No such file or directory)
Comment by
http://afoolishmanifesto.com/
— Wed Feb 26 23:09:23 2020
@joey: ok, I got it to connect and it indeed sent over a key etc. For some reason now though git-annex (on android) "crashes" shortly after starting. To be clear, the web app says that the program crashed, the console is still there. I suspect that it may have something to do with my largish remote repo and the time required to sync just the metadata, but I can't tell. Any ideas what I should do next? (Note that I did change it to manual mode because my phone doesn't have 30G of storage :)
Comment by
http://afoolishmanifesto.com/
— Wed Feb 26 23:09:23 2020
@frioux it will automatically generate a new ssh key and configure the server to use it, once you submit the form and enter the password to let it into the server.
Comment by
http://joeyh.name/
— Wed Feb 26 23:09:23 2020
@joey should I be using the nightlies to see that? Under "Adding a remote server using ssh" I only see Host name, user name, directory, and port. Will it only be an option after I type in a password?
Comment by
http://afoolishmanifesto.com/
— Wed Feb 26 23:09:23 2020
The Android app works on many non-rooted Android systems.
The "link busybox: Read-only file system" means that /data/data/ga.androidterm/lib/lib.busybox.so cannot be hard linked to /data/data/ga.androidterm/busybox. That's not normal. I'd appreciate if you could provide more information on your Android device, like Android version and model number.
Comment by
http://joeyh.name/
— Wed Feb 26 23:09:23 2020
Is there a way I can use an SSH Key to connect to a remote server? What would be really cool, though maybe not feasible, would be to use connectbot as an ssh-agent.
Comment by
http://afoolishmanifesto.com/
— Wed Feb 26 23:09:23 2020
joey -- any additional information could I provide to troubleshoot the issue? original repository seems to sync ok, but I can't "administer" it if I can't even switch to it...
Comment by
http://yarikoptic.myopenid.com/
— Wed Feb 26 23:09:23 2020
because working in the terminal to interact with git-annex probably should not be a common case on Android, may be it is worth making default type of new added repository to become a full backup? I have initiated a new one, attached a remote one, it said "synced" but all the files were just containing symlinks and were not usable. I had to switch to "full backup" (or whatever that name) to finally get directory synced
log file might grow too large simply because of containing numerous entries for attempting connect remote repository while offline, e.g.
Please make sure you have the correct access rights
and the repository exists.
ssh: Could not resolve hostname onerussian.com: No address associated with hostname
fatal: Could not read from remote repository.
IMHO those should not be there at all, e.g. if it is known that ATM there is no network connectivity
In addition to two existing repositories (1 local /sdcard/annex, which is also avail at/storage/sdcard0/annex + 1 remote) I have added one more local (and said to keep it in sync with original local). But it didn't work -- it "Synced with onerussian.com_annex but not with Annex" and claimed that the /external/extSdCard/Annex doesn't exist, although it is there (and with .git generated etc). When I restarted the deamon I got into a "new" Repository: /storage/extSdCard/Annex which also listed the 1st local but with "Failed to sync with localhost" message -- no remote one listed. Whenever I try to "Switch repository" to /sdcard/annex (the original local) -- it starts loading a new page but gets stuck right there. The only way to revive webui is to go back to Dashboard. Log there says (retyping from the screen so typos might be there):
error: cannot run git-receive-pack '/storage/sdcard0/annex': No such file or directory
fatal: unable to fork
Comment by
http://yarikoptic.myopenid.com/
— Wed Feb 26 23:09:23 2020
not sure if that is a known issue: whenever "remote server" is added, password needs to be typed back in the original terminal... is a bit challenging to do on android and not straightforward user-wise
Comment by
http://yarikoptic.myopenid.com/
— Wed Feb 26 23:09:23 2020
Hi Joey -- there is success here... previous installation was "updated" by installing the new package without uninstalling previous one, and that apparently didn't work correctly (I didn't even have bin/ directory you mentioned). So I have removed previous installation and reinstalled it again -- it starts now! Thanks ;)
Comment by
http://yarikoptic.myopenid.com/
— Wed Feb 26 23:09:23 2020
Hi, thank you for addressing this issue! I installed the new release but now it fails in another way: the message is just "In mgmain NJI_OnLoad" then the terminal says that the session is closed.
Comment by
https://www.google.com/accounts/o8/id?id=AItOawkwjBDXkP9HAQKhjTgThGOxUa1B99y_WRA
— Wed Feb 26 23:09:23 2020
you said before the error was "Read-only file system". Now you're saying it's "Cross-device link". I'm slightly confused.
;-) Sorry for confusion, here are the details:
"Read-only file system" -- that error appeared when I started "stock git annex", i.e. from running /data/data/ga.androidterm/lib/lib.start.so .
Since you have suggested that it might be coming from hard linking command, I have ran that one manually, and that is when I got "Cross-device link" error, which suggests that hard linking is not the one at fault here.
I will try fresh build now
Cheers,
Comment by
http://yarikoptic.myopenid.com/
— Wed Feb 26 23:09:23 2020
The same here on Android 8.1.0. likely because .app was build for 5, but there is nothing newer offered on Android downloads. So the Android Port is abandoned overall?
@yarikoptic you said before the error was "Read-only file system". Now you're saying it's "Cross-device link". I'm slightly confused.
I've reworked the android app to not need any hard links. Try the current autobuild: http://downloads.kitenet.net/git-annex/autobuild/android/git-annex.apk
Hello, I have installed the APK on Android N. However, the assistant doesn't launch, gives an error on terminal: "Cannot link executive git-annex."
What is causing this? Please help.
I generated an rsa keypair and added them to /sd/ga-h/.ssh, yet they were overwritten. I couldn't access my annexes located on github. I couldn't login to google talk, as instructed by the web app.
Thanks for letting me know about gitlab supporting git-annex.
@mebus : You can put your SSH keys here :
/sdcard/git-annex.home/.ssh/id_rsa
/sdcard/git-annex.home/.ssh/id_rsa.pub
@yarikoptic, there is a process you can perform that will help me determine what's going on.
You should be able to get the git-annex app to let you into a shell. You can do this by starting the app, and then going into its configuration menu, to Preferences, selecting "Command Line", and changing it to run "/system/bin/sh"
Then when you open a new window in the git-annex app, you'll be at a shell prompt. From there, you can run:
ls -ld /data/data/ga.androidterm
I'm interested to know a) whether the directory exists and b) what permissions and owner it has. On my tablet, I get back "drwxr-x--x app_39 app_39" .. and if I run
id
in the shell, it tells me it's running asapp_39
.My guess is the directory probably does exist, but cannot be written to by the app. If you're able to verify that, the next step will be to investigate if there is some other directory that the app can write to. It needs to be able to write to someplace that is not on the
/sdcard
to install itself.How is this designed to work in the contact of Androids crap permissions?
Hallo,
how can I use the app with public/private keys for SSH. Where can I add them?
Thanks
Mebus
I just tried to run this on my Nexus 7 which has Android 4.2.2, and I received the following: http://hodapple.com/files/Screenshot_2013-05-19-09-49-53.png http://hodapple.com/files/git-annex-error.txt
In spite of that, though, the URL provided still worked.
Sorry for the delay: my android is stock Samsung-tuned Jelly beans. Android 4.1.2 Baseband version N7000XXLSO
not sure if that would be of any use :-/ nothing in the logs (aLogcat) if I filter by annex -- should there any debug output? what should be a key to search by?
Phone: HTC EVO 3d 4g Model Number: pg86100 Android Version: 4.0.3
In webapp UI, added on first install, the location for repository: /storage/sdcard1
!warning
Watcher crashed: addWatch:
permission denied (Permission denied)
[Restart Thread]
:Performing startup scan
In terminal Window 1:
nex webapp <
Detected a crippled filesystem.
Enabling direct mode.
Detected a filesystem without fifo support.
Disabling ssh connection caching.
Android 4.1.1 Huawei Y300 Annex.apk v1.0.52 version 4.20130723
@Frew, you should file bug reports when you have a bug.
One problem you mentioned had already had a bug report filed by someone else: http://git-annex.branchable.com/bugs/Watcher_crashed:_addWatch:_does_not_exist/ So you can post your details there.
frioux here (something messed up with myopenid or something)
So I deleted the repo on my phone (via the CLI since the web app seemed hung) and recreated it; this time making sure that I set things to manual mode ASAP. It didn't have the problem it was having before, but now what seems to have happened is that it fetches from the remote, commits to the local repo, and then immediately fetches and commits again. It looks like it's about a 4s repeat loop. Any ideas what I should do next?
ok, it eventually got the details from the remote server, but now I'm getting some other oddities. here is some of my log that shows what I am running into
Watcher crashed: addWatch: does not exist (No such file or directory) [2013-07-18 06:22:46 CDT] Watcher: warning Watcher crashed: addWatch: does not exist (No such file or directory) (scanning...) [2013-07-18 06:23:19 CDT] Watcher: Performing startup scan Watcher crashed: addWatch: does not exist (No such file or directory) [2013-07-18 06:24:28 CDT] Watcher: warning Watcher crashed: addWatch: does not exist (No such file or directory) (scanning...) [2013-07-18 06:24:31 CDT] Watcher: Performing startup scan Watcher crashed: addWatch: does not exist (No such file or directory) [2013-07-18 06:25:44 CDT] Watcher: warning Watcher crashed: addWatch: does not exist (No such file or directory)
@frioux the webapp has a "ssh server" option that will set up a ssh key and use it for passwordless data transfer to a ssh server.
The openssh included in the git-annex app fully supports everything you can usually do with ssh keys, so you can also set this up by hand.
The Android app works on many non-rooted Android systems.
The "link busybox: Read-only file system" means that
/data/data/ga.androidterm/lib/lib.busybox.so
cannot be hard linked to/data/data/ga.androidterm/busybox
. That's not normal. I'd appreciate if you could provide more information on your Android device, like Android version and model number.I too get the 'link busybox: Read-only file system' message. Here is my phone info:
Phone: Samsung Galaxy Y GT-S5360 (rooted)
Android: 2.3.6 Gingerbread
BusyBox path: /system/xbin/
Androids own terminal seems not to understand the d argument (-ld: No such file or directory) but over ssh 'ls -ld /data/data/ga.androidterm' returns
Hi again.
talking about 4.20130523-gcfe07a2 version:
because working in the terminal to interact with git-annex probably should not be a common case on Android, may be it is worth making default type of new added repository to become a full backup? I have initiated a new one, attached a remote one, it said "synced" but all the files were just containing symlinks and were not usable. I had to switch to "full backup" (or whatever that name) to finally get directory synced
log file might grow too large simply because of containing numerous entries for attempting connect remote repository while offline, e.g.
Please make sure you have the correct access rights and the repository exists. ssh: Could not resolve hostname onerussian.com: No address associated with hostname fatal: Could not read from remote repository.
IMHO those should not be there at all, e.g. if it is known that ATM there is no network connectivity
error: cannot run git-receive-pack '/storage/sdcard0/annex': No such file or directory fatal: unable to fork
You should be able to run /data/data/ga.androidterm/runshell even if you cannot ls /data. This adds /data/data/ga.androidterm/bin to PATH
However, the shell that the app starts is started by runshell anyway, so I don't understand how this could happen.
With fresh build got:
u0_a39@android:/ $ git annex webapp /system/bin/sh: git: not found
the PATH is /sbin:/system/bin:/system/xbin
where should git (and ga) reside now ? (/data somehow is not accessible now to u0_a39)
;-) Sorry for confusion, here are the details:
"Read-only file system" -- that error appeared when I started "stock git annex", i.e. from running /data/data/ga.androidterm/lib/lib.start.so . Since you have suggested that it might be coming from hard linking command, I have ran that one manually, and that is when I got "Cross-device link" error, which suggests that hard linking is not the one at fault here.
I will try fresh build now Cheers,
Following your news on kickstarter downloaded the .apk, and installed it. Upn start I just got a terminal window with
link busybox: Read-only file system
[Terminal session finished]
That is on Galaxy Note