bug triaging and tagging
This commit is contained in:
Joey Hess
parent
243bda3c52
commit
1a430daca4
28 changed files with 74 additions and 8 deletions
|
|
@ -1,9 +1,30 @@
|
|||
This follows up to the [comment made by Laszlo](http://git-annex.branchable.com/design/assistant/polls/what_is_preventing_me_from_using_git-annex_assistant/#comment-f26d3b6b45bb66601ecfaa883ace161c) on the [recent poll](http://git-annex.branchable.com/design/assistant/polls/what_is_preventing_me_from_using_git-annex_assistant/).
|
||||
This follows up to the [comment made by
|
||||
Laszlo](http://git-annex.branchable.com/design/assistant/polls/what_is_preventing_me_from_using_git-annex_assistant/#comment-f26d3b6b45bb66601ecfaa883ace161c)
|
||||
on the [recent
|
||||
poll](http://git-annex.branchable.com/design/assistant/polls/what_is_preventing_me_from_using_git-annex_assistant/).
|
||||
|
||||
I too need to be able to select the directory on the remote drive that the annex will be synced to.
|
||||
I too need to be able to select the directory on the remote drive that the
|
||||
annex will be synced to.
|
||||
|
||||
If I just add a remote drive via the web app, it syncs the repository to `/mnt/usb/annex`, and it looks like it just creates a bare repository in that folder. I need the repository to be synced to something like `/mnt/usb/subfolder/myspecifiedfoldername` and I need that remote to be a full repository.
|
||||
If I just add a remote drive via the web app, it syncs the repository to
|
||||
`/mnt/usb/annex`, and it looks like it just creates a bare repository in
|
||||
that folder. I need the repository to be synced to something like
|
||||
`/mnt/usb/subfolder/myspecifiedfoldername` and I need that remote to be a
|
||||
full repository.
|
||||
|
||||
My use case is that I use the USB drive to keep annexes in sync between two computers. I have multiple annexes that need to be synced between the two computers, and none of them are in a directory called `annex`. I also need to be able to plug the drive into other computers and access the files directly, without doing a `git clone` or anything like that. I have all of this setup and working fine with just plain old git annex, but the web app does not seem to support creating new repositories with this workflow.
|
||||
My use case is that I use the USB drive to keep annexes in sync between two
|
||||
computers. I have multiple annexes that need to be synced between the two
|
||||
computers, and none of them are in a directory called `annex`. I also need
|
||||
to be able to plug the drive into other computers and access the files
|
||||
directly, without doing a `git clone` or anything like that. I have all of
|
||||
this setup and working fine with just plain old git annex, but the web app
|
||||
does not seem to support creating new repositories with this workflow.
|
||||
|
||||
I think it makes a lot of sense to allow the web application to add a new remote that is simply a directory. People like me could specify the path of the directory to be on the mounted USB drive. Others may want to add a remote that is a mounted network share or something like that.
|
||||
I think it makes a lot of sense to allow the web application to add a new
|
||||
remote that is simply a directory. People like me could specify the path of
|
||||
the directory to be on the mounted USB drive. Others may want to add a
|
||||
remote that is a mounted network share or something like that.
|
||||
|
||||
> [[done]], the webapp now has a "Add another repository" option,
|
||||
> and you can just enter the path to whatever place you like inside a USB
|
||||
> drive. --[[Joey]]
|
||||
|
|
|
|||
|
|
@ -24,3 +24,5 @@ Alternatively, git-annex should stop relying on any per-user services, and use k
|
|||
### What version of git-annex are you using? On what operating system?
|
||||
|
||||
git-annex 3.20130102 on Linux 3.7.1, GNOME 3.7
|
||||
|
||||
> [[done]] --[[Joey]]
|
||||
|
|
|
|||
|
|
@ -12,3 +12,4 @@ Latest Head from git, Ubuntu 12.04
|
|||
Please provide any additional information below.
|
||||
I'm not sure whether this is a bug or not. I just ran into problems because I did not expect the cabal build process to create my desktop file but instead thought that git-annex will create it by it-self taking its own path. Perhaps it would make sense to produce an error if the bindir is invalid. An automatic expansion of '~' in the build script would be even better.
|
||||
|
||||
> [[done]], I think it was a typo. --[[Joey]]
|
||||
|
|
|
|||
|
|
@ -17,3 +17,5 @@ What version of git-annex are you using? On what operating system?
|
|||
I'm using 9e57edff287ac53fc4b1cefef7271e9ed17f2285 (Fri Feb 22 15:19:25 2013 +0000).
|
||||
|
||||
Ubuntu 12.10 x86_64
|
||||
|
||||
[[!tag /design/assistant]]
|
||||
|
|
|
|||
|
|
@ -65,3 +65,5 @@ the `SHA256` key is not present.
|
|||
|
||||
It looks like I'll have to rollback my ZFS snapshots and start over, but I'm
|
||||
wondering: how was I even able to create this situation?
|
||||
|
||||
> [[Done]]; user error. --[[Joey]]
|
||||
|
|
|
|||
|
|
@ -28,3 +28,5 @@ OS: Ubuntu 12.04.1 LTS 3.2.0-35-generic-pae #55-Ubuntu SMP Wed Dec 5 18:04:39 UT
|
|||
On dmesg:
|
||||
[45773.212717] git-annex[26779]: segfault at b724e840 ip 09699150 sp b4cfd038 error 7 in git-annex[8048000+1762000]
|
||||
|
||||
[[!tag /design/assistant]]
|
||||
> [[done]], see comments --[[Joey]]
|
||||
|
|
|
|||
|
|
@ -15,3 +15,4 @@ What version of git-annex are you using? On what operating system?
|
|||
|
||||
Please provide any additional information below.
|
||||
|
||||
[[!tag /design/assistant/OSX]]
|
||||
|
|
|
|||
|
|
@ -15,3 +15,5 @@ Version: 4.20130314, Debian
|
|||
Please provide any additional information below.
|
||||
|
||||
I am an "webinterface only" user.
|
||||
|
||||
[[!tag /design/assistant]]
|
||||
|
|
|
|||
|
|
@ -21,3 +21,5 @@ What version of git-annex are you using? On what operating system?
|
|||
|
||||
Please provide any additional information below.
|
||||
|
||||
[[!meta title="strange OSX behavior when killed"]]
|
||||
[[!tag /design/assistant/OSX unreproducible]]
|
||||
|
|
|
|||
|
|
@ -1 +1,6 @@
|
|||
The 32-bit standalone build appears to require two libraries (lib32-libyaml and lib32-gsasl) that are not available on Arch Linux. [See the comments on the AUR package](https://aur.archlinux.org/packages/git-annex-bin/). I'd appreciate it if you could bring back the 64-bit build.
|
||||
|
||||
> [[done]], based on <https://aur.archlinux.org/packages/git-annex-bin/>
|
||||
> they are managing with what I am providing. Also, Arch Linux has a
|
||||
> proper build of git-annex from source, so I'm not going to worry about
|
||||
> git-annex-bin, the rationalle for which I don't even understand. --[[Joey]]
|
||||
|
|
|
|||
|
|
@ -26,3 +26,5 @@ Workaround:
|
|||
* rename `metaarray` to `ma` again using the webapp
|
||||
|
||||
Perhaps the renaming of the remote not surviving clones is unavoidable, but the webapp should be able to cope with the situation. Thanks.
|
||||
|
||||
[[!tag /design/assistant]]
|
||||
|
|
|
|||
|
|
@ -24,3 +24,4 @@ What version of git-annex are you using? On what operating system?
|
|||
Please provide any additional information below.
|
||||
|
||||
|
||||
[[!meta title="rsync special remote does not use ssh connection caching"]]
|
||||
|
|
|
|||
|
|
@ -48,4 +48,4 @@ git-annex HEAD from yesterdays git. Ubuntu 12.10
|
|||
|
||||
Please provide any additional information below.
|
||||
|
||||
|
||||
[[!tag /design/assistant unreproducible]]
|
||||
|
|
|
|||
|
|
@ -13,3 +13,5 @@ I expect to remain invisible, but I get the following warning: "Oops! You are no
|
|||
##Please provide any additional information below.
|
||||
|
||||
Syncing between the repositories works ok.
|
||||
|
||||
[[!tag /design/assistant]]
|
||||
|
|
|
|||
|
|
@ -21,4 +21,4 @@ Version: 3.20130124
|
|||
Please provide any additional information below.
|
||||
|
||||
[[!tag /design/assistant]]
|
||||
[[!meta title="ssh password prompting"]]
|
||||
[[!meta title="ssh password prompting issue with assistant"]]
|
||||
|
|
|
|||
|
|
@ -17,3 +17,6 @@ Debian wheezy with git-annex version: 3.20130114
|
|||
Please provide any additional information below.
|
||||
|
||||
Its working if i start `git-annex webapp` as root. I had the same error on previous version.
|
||||
|
||||
> I've made some improvements. Think this was user error. [[done]]
|
||||
> --[[Joey]]
|
||||
|
|
|
|||
|
|
@ -10,3 +10,6 @@ What version of git-annex are you using? On what operating system?
|
|||
|
||||
Please provide any additional information below.
|
||||
ssh keys were installed to allow login, when ssh-askpass was not found on osx version
|
||||
|
||||
[[!meta title="webapp rsync probe command failed on FreeNAS box"]]
|
||||
[[!tag /design/assistant]]
|
||||
|
|
@ -35,3 +35,4 @@ relevant part of .git/config:
|
|||
supported repository versions: 3
|
||||
upgrade supported from repository versions: 0 1 2
|
||||
|
||||
> [[done]], see comment --[[Joey]]
|
||||
|
|
|
|||
|
|
@ -30,3 +30,5 @@ The remote in question:
|
|||
url = git@git.example.com:annex-home
|
||||
fetch = +refs/heads/*:refs/remotes/origin/*
|
||||
annex-ignore = true
|
||||
|
||||
> belived to be [[fixed|done]] --[[Joey]]
|
||||
|
|
|
|||
|
|
@ -28,3 +28,10 @@ Possible approaches:
|
|||
how to find the file to unlock it.
|
||||
|
||||
[[!meta title="assistant: watcher_commits_unlocked_files"]]
|
||||
|
||||
> [[done]]; I just tested and somehow this no longer happens;
|
||||
> the watcher/assistant leaves the unlocked file alone, and then
|
||||
> as soon as it's modified re-adds it.
|
||||
>
|
||||
> Also, of course, there is direct mode, which avoids needing to unlock...
|
||||
> --[[Joey]]
|
||||
|
|
|
|||
|
|
@ -139,3 +139,6 @@ expecting a request body?
|
|||
0x0020: 8010 0800 fe28 0000 0101 080a 004a dfe0 .....(.......J..
|
||||
0x0030: 004a b3da .J..
|
||||
</pre>
|
||||
|
||||
[[!tag /design/assistant]]
|
||||
[[done]]
|
||||
|
|
|
|||
|
|
@ -8,7 +8,9 @@ alias for a hostname at no-ip.com.) Despite the fact that "homeworld" is a
|
|||
viable ssh target because of the alias, the assistant doesn't recognize it
|
||||
as a valid host to ssh to.
|
||||
|
||||
I had trouble with an ip address the first time I tried it but just tried it again and it worked fine, so please disregard that part of the title of this bug report.
|
||||
I had trouble with an ip address the first time I tried it but just tried
|
||||
it again and it worked fine, so please disregard that part of the title of
|
||||
this bug report.
|
||||
|
||||
|
||||
What is the expected output? What do you see instead?
|
||||
Loading…
Reference in a new issue