| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
|
| |
My upload of -2 seems to have gotten lost, but there is a +b1 binNMU
that rebuilds against the new gnutls.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This adds a dep on haskell's async library, but since that's been
added to the recent haskell platform release, it should not be
much hardship to my poor long-suffering library chasing users.
|
| | |
|
| | |
|
| |
|
|
| |
debian testing still has the buggy version..
|
| | |
|
| | |
|
| |
|
|
| |
operating on a specified directory.
|
| | |
|
| |
|
|
|
|
|
| |
they were originally created using.
It was creating a new special remote with a different name, unless
the stars perfectly aligned and the names matched.
|
| |
|
|
|
|
| |
Wrote a better git remote name sanitizer. Git blows up on lots of weird
stuff, especially if it starts the remote name, but I managed to get
some common punctuation working.
|
| |
|
|
|
| |
Working around what seems to me to be a git bug. Surely there are valid
setups of real git remotes that don't have fetch set?
|
| | |
|
| |
|
|
|
| |
New 0.5 changes the api, rather gratuitously, so run away. I can juse use
Hamlet here.
|
| | |
|
| |
|
|
|
| |
Amoung other things, this makes it immediately sync files from a removable
drive when it's added.
|
| |
|
|
| |
Several things only happen when on a branch, so make sure we're on one.
|
| |
|
|
| |
which blaze-html depends on, so not a significant new dep
|
| |
|
|
| |
~/.ssh/git-annex-shell wrapper the first time it's run.
|
| |
|
|
|
|
|
| |
a key's presence.
Also, use the new withQuietOutput function to avoid running the shell to
/dev/null stderr in two other places.
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Adjust build deps to ensure that only a fixed version of the library will
be used.
Also, removed the bound thread stuff, which I now think was (probably)
a red herring.
|
| | | |
|
| | |\
| |/
|/|
| |
| | |
Conflicts:
Assistant/Threads/NetWatcher.hs
|
| | |
| |
| |
| |
| |
| |
| |
| | |
MountWatcher can't do this, because it uses the session dbus,
and won't have access to the new DBUS_SESSION_BUS_ADDRESS if a new session
is started.
Bumped dbus library version, FD leak in it is fixed.
|
| | |\
| |/
|/|
| |
| |
| | |
Conflicts:
Assistant/Threads/MountWatcher.hs
Assistant/Threads/NetWatcher.hs
|
| | |
| |
| |
| | |
which doesn't work with LDAP or NIS.
|
| | |\
| |/
|/| |
|
| | |
| |
| |
| |
| |
| |
| | |
For now, when dbus goes away, the assistant keeps running but does not fall
back or reconnect. To do so needs more changes to the DBus library; in
particular a connectSessionWith and connectSystemWith to let me specify
my own clientThreadRunner.
|
| | |\
| |/
|/|
| |
| | |
Conflicts:
doc/design/assistant/cloud.mdwn
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
So, it might be called sha1sum, or on some other OS, it might be called
sha1. It might be hidden away off of PATH on that OS. That's just expected
insanity; UNIX has been this way since 1980's. And these days, nobody even
gives the flying flip about standards that we briefly did in the 90's
after the first round of unix wars.
But it's the 2010's now, and we've certainly learned something.
So, let's make it so sometimes sha1 is a crazy program that wants to run as
root so it can lock memory while prompting for a passphrase, and outputting
binary garbage. Yes, that'd be wise. Let's package that in major Linux
distros, too, so users can stumble over it.
|
| | |\
| |/
|/| |
|
| | |
| |
| |
| |
| | |
This used to work, but got broken when the transfer info files were added,
as it failed writing them on the readonly filesystem.
|
| |/ |
|
| |
|
|
|
|
|
| |
bup 0.25 does not accept that; and bup split reads from stdin by
default if no file is given. I'm not sure what version of bup changed this.
This only affected bup special remotes that were encrypted.
|
| | |
|
| |
|
|
| |
not checked into git.
|
| | |
|
| |
|
|
| |
This was a stopgap, and we have the self-contained webapp now.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Monitors git-annex branch for changes, which are noticed by the Merger
thread whenever the branch ref is changed (either due to an incoming push,
or a local change), and refreshes cached config values for modified config
files.
Rate limited to run no more often than once per minute. This is important
because frequent git-annex branch changes happen when files are being
added, or transferred, etc.
A primary use case is that, when preferred content changes are made,
and get pushed to remotes, the remotes start honoring those settings.
Other use cases include propigating repository description and trust
changes to remotes, and learning when a remote has added a new special
remote, so the webapp can present the GUI to enable that special remote
locally.
Also added a uuid.log cache. All other config files already had caches.
|
| | |
|
| |\
| |
| |
| |
| |
| | |
Conflicts:
debian/changelog
git-annex.cabal
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
in= was problimatic in two ways. First, it referred to a remote by name,
but preferred content expressions can be evaluated elsewhere, where that
remote doesn't exist, or a different remote has the same name. This name
lookup code could error out at runtime. Secondly, in= seemed pretty useless.
in=here did not cause content to be gotten, but it did let present content
be dropped.
present is more useful, although "not present" is unstable and should be
avoided.
|
Joey Hess