| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
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.
|
| | |
| |
| |
| |
| |
| |
| | |
When in a subdir, both the normal filepath, and the filepath relative to
the top of the git repo are needed for matching. The former for key lookup,
and the latter for include/exclude to match against. Previously, key lookup
didn't work in this situation.
|
| | |
| |
| |
| |
| |
| | |
The old code was just wrong in taking fromPath of GIT_DIR -- that made an
localUnknown location with the GIT_DIR in it, which only worked by
accident, and failed in submodules.
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
losing connection, which will need to be fixed upstream.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Now that this is handled correctly, git-annex can be used in git submodules.
Also, fixed infelicity where Git.CurrentRepo and Git.Config.updateLocation
were both dealing with core.worktree. Now updateLocation handles it for
Local as well as for LocalUnknown repos.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
description, or no description.
This is also nice in that uuids are all the same length, so the values
of each line, line up.
Also a great deal of boilerplate elimination.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
installed, and set annex-ignore.
Aka solve the github problem.
Note that it's possible the initial configlist will fail for some network
reason etc, and then the fetch succeeds. In this case, a usable remote gets
disabled. But it does print a message, and this only happens once per
remote, so that seems ok.
|
| | |
| |
| |
| |
| |
| |
| | |
utf8.
The crash actually occurred when writing out the file, which was done to a
handle that had not had fileSystemEncoding applied to it.
|
| | |
| |
| |
| | |
gets synced.
|
| | |
| |
| |
| |
| | |
This is not quite right yet, since it disables it so hard it doesn't show
up in the repo list anymore!
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
exist.
This should fix build on mips, mipsel, s390, s390x, and sparc.
cabal doesn't test this yet.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
There was one forkProcess lurking in test.hs, and that seems to be
responsible for recent buildd failures on amd64 and armhf. I was able to
reproduce it pretty easily on amd64, and even once on i386, and it was
clearly that same bad old threaded runtime hang. So removing this
forkProcess should fix it. Odd that it lurked for some months before
popping up.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Setting GIT_INDEX_FILE clobbers the rest of the environment, making git
not read ~/.gitconfig, and blow up if GECOS didn't have a name for the
user.
I'm not entirely happy with getEnvironment being run every time now,
that's somewhat expensive. It may make sense to just set GIT_COMMITTER_*
and GIT_AUTHOR_*, but I worry that clobbering the rest could break PATH,
or GIT_PATH, or something else that might be used by a command run in here.
And caching the environment is not a good idea either; it can change..
|
| | |
| |
| |
| | |
This is less expensive than having inallgroup weed out dead repositories.
|
| | | |
|
| | | |
|
| | | |
|
Joey Hess