Merge branch 'master' of ssh://git-annex.branchable.com

This commit is contained in:
Joey Hess 2013-03-17 15:59:28 -04:00
commit 1473ad6ea4
10 changed files with 101 additions and 0 deletions

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="annexuser"
ip="50.46.189.77"
subject="comment 7"
date="2013-03-17T01:29:48Z"
content="""
It's working now! Thanks!
"""]]

View file

@ -0,0 +1,32 @@
## What steps will reproduce the problem?
After the assistant idles for a while, it queues many transfers to remotes configured annex-ignore=true
##What is the expected output? What do you see instead?
No attempts to upload to repos marked 'annex-ignore=true'
Instead I see many queued transfers to the remote 'origin'
[Screenshot](https://www.evernote.com/shard/s1/sh/ea0de76c-4b68-4266-b9f6-8a9c343997b6/72baab4a3ce73b0915b151829bbeaf75/res/8a8ab1fb-3173-47ea-875d-b0e320cb827b/skitch.png)
##What version of git-annex are you using? On what operating system?
% > git annex version
git-annex version: 4.20130315
local repository version: 3
default repository version: 3
supported repository versions: 3 4
upgrade supported from repository versions: 0 1 2
build flags: Assistant Webapp Pairing Testsuite S3 WebDAV FsEvents XMPP DNS
Mac OSX 10.8.2 Build 12C3006
##Please provide any additional information below.
The remote in question:
[remote "origin"]
url = git@git.example.com:annex-home
fetch = +refs/heads/*:refs/remotes/origin/*
annex-ignore = true

View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawnR7hb8IaKB3IKZptRukje0yahmhfLOO98"
nickname="Adam"
subject="comment 1"
date="2013-03-17T00:30:26Z"
content="""
> Made UI changes to encourage user to install git-annex on the server when adding a ssh server, rather than just funneling them through to rsync.
What's the difference between having git-annex available versus not?
"""]]

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawnxp2XU8gIribhhGhGuYtU6eMMwHv5gUGI"
nickname="Amitai"
subject="Google Talk silently drops non-Google invites (at least)"
date="2013-03-17T13:44:18Z"
content="""
Have you seen <http://www.fsf.org/blogs/sysadmin/google-backslides-on-federated-instant-messaging-on-purpose>? Maybe they're also doing other funny stuff that gets in your way.
"""]]

View file

@ -0,0 +1 @@
Is there a way to check if a special remote is setup to use GPG? And, if so, see the ID of keys that it is encrypting to?

View file

@ -0,0 +1,14 @@
[[!comment format=mdwn
username="http://joeyh.name/"
nickname="joey"
subject="comment 1"
date="2013-03-17T18:59:40Z"
content="""
You can tell this by looking at remote.log:
git show git-annex:remote.log
Remotes that are encrypted will have a big \"cipher=\" block in there, and ones that are encrypted to gpg public keys will have a list of the keys following \"cipherkeys=\"
"""]]

View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://joeyh.name/"
nickname="joey"
subject="comment 1"
date="2013-03-17T19:05:27Z"
content="""
There's no UI for it in the assistant. [[Relevant bug report|bugs/The_webapp_doesn't_allow_deleting_repositories]]
"""]]

View file

@ -0,0 +1,5 @@
I have the webapp setup to manage 4 different repositories.
One repository had many gigabytes to upload to a remote. As this was moving along, I wanted to check on the status of one of the other repositories. I knew that this second repository had a lot of data to download. When I switched to the second repo in the webapp, I noticed in my network monitor that the amount of upstream bandwidth I was using dropped and the amount of downstream bandwidth increased. I switched back to the first repo, and my downstream bandwidth dropped and the upstream bandwidth increased.
It looks like git-annex stopped uploading data from the first repo when I switched to the second, and stopped downloading data to the second repo when I switched to the first. Is this correct? I was under the impression that switching repositories in the webapp simply changed the view that I was looking at, but that the assistant would still be managing all the repositories I had setup -- uploading/downloading/syncing concurrently.

View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
nickname="joey"
subject="comment 1"
date="2013-03-17T18:53:26Z"
content="""
Each repository gets its own git-annex assistant daemon, which is entirely separate from the daemons used by other repositories.
The only affect that switching which repository is in view in the webapp can have is it can start a daemon running on a repository that for some reason did not already have the daemon running. This could happen if it was not set to autostart on login, for example.
"""]]

View file

@ -0,0 +1,5 @@
We're nearing the end of the year of development funded by Kickstarter. I'm curious to know what the future of the project looks like.
I assume that development will decrease from its current levels as you focus more of your energy on activities that put bread on the table, but is git-annex still something that you foresee actively working on or will it be in more of a feature-freeze-bug-fix stage?
As a backer my only regret is that during the campaign I wasn't able to donate as much as I would have liked. The project has exceeded my expectations since then. I don't know that another Kickstarter campaign is worth the effort, but if you were to ask for donations to fund another month or two or three I would gladly donate. Or perhaps implement a feature-bounty program where users could donate money toward development of a particular feature they would like to see added. Or perhaps you're sick of working for the Internet!