| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
| |
key for corrupt data.
|
| |
|
|
| |
too long (and use relative path to minimise path to the control socket).
|
| |
|
|
|
|
|
|
| |
The default backend used when adding files to the annex is changed from
SHA256 to SHA256E, to simplify interoperability with OSX, media players,
and various programs that needlessly look at symlink targets.
To get old behavior, add a .gitattributes containing: * annex.backend=SHA256
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
environments that normally need git config to set names, etc. Closes: #682351 Thanks, gregor herrmann
|
| |\
| |
| |
| |
| |
| |
| | |
Conflicts:
debian/changelog
Updated changelog for assistant and webapp
|
| | | |
|
| | |
| |
| |
| | |
extensions, as added in 3.20120721.
|
| | |
| |
| |
| | |
extensions, as added in 3.20120721.
|
| |\|
| |
| |
| |
| |
| | |
Conflicts:
Makefile
debian/copyright
|
| | |
| |
| |
| |
| | |
This is a simple application of inkscape's rather amazing tracing
capabilities.
|
| |\|
| |
| |
| |
| | |
Conflicts:
debian/changelog
|
| | | |
|
| |\|
| |
| |
| |
| | |
Conflicts:
debian/changelog
|
| |\ \
| | |
| | |
| | |
| | | |
Conflicts:
debian/changelog
|
| | |/ |
|
| | | |
|
| |\| |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Avoid crashing when "git annex get" fails to download from one location,
and falls back to downloading from a second location.
The problem is that git annex get calls download recursively from within
itself if the first download attempt fails. So the first time through, it
writes a transfer info file, which is then overwritten on the second,
recursive call. Then on cleanup, it tries to delete the file twice, which
of course doesn't work.
Fixed both by not crashing if the transfer file is removed, and by
changing Get to not run download recursively like that. It's the only
thing that did so, and it just seems like a bad idea.
|
| |\|
| |
| |
| |
| | |
Conflicts:
Init.hs
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
automatically be generated, like "joey@gnu:~/foo""
This reverts commit abde98cda21d5deeb16ed3baf736b06fdc2fce2f.
Temporarily dropping from master, since this actually uses stuff
that's only currently availble in the assistant branch. Will come back when
I merge that, and can wait..
|
| |\| |
|
| | |
| |
| |
| | |
automatically be generated, like "joey@gnu:~/foo"
|
| |\| |
|
| | |
| |
| |
| | |
config is valid.
|
| | |
| |
| |
| | |
This does fix some UI issues I was having.
|
| | |
| |
| |
| | |
another dependency cabal works without here, oddly
|
| | |
| |
| |
| | |
mocked up the main screen, and am actually pretty happy with it!
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Had to switch to toWaiAppPlain to avoid a seeming bug in toWaiApp;
chromium only received a partial copy of jquery. Always the same length
each time, which makes me think it's a bug in the compression, although
a bug in the autohead middleware is also a possibility.
Anyway, there's little need for compression for a local webapp. Not wasting
time compressing things is probably a net gain.
Similarly, I've not worried about minifying this yet. Although that would
avoid bloating the git-annex binary quite so much.
|
| | |
| |
| |
| |
| |
| | |
Note that here I don't need blaze-markup for cabal to succeed, but Jimmy
reports he does. Seems like Text.Blaze.Renderer.String moved from blaze to
blaze-markup in some version.
|
| | | |
|
| | | |
|
| | | |
|
| |\|
| |
| |
| |
| | |
Conflicts:
git-annex.cabal
|
| | | |
|
| | |
| |
| |
| |
| | |
This is an unholy mashup, but it just might work. It works on Linux,
that's all I've tested. :)
|
| | |
| |
| |
| | |
Currently only prints mount points when mounts happen.
|
| |/
|
|
|
|
|
|
|
| |
Converted from using c2hs to using hsc2hs, just because other code
in git-annex uses hsc2hs.
Various cleanups.
This code is LGPLed, so I had to include that licence.
|
| | |
|
| |
|
|
| |
Closes: #680450
|
| |
|
|
| |
faster than forking the more optimised external program.
|
| |
|
|
|
|
|
|
| |
a dependency) to do the checksumming. This may be slower, but avoids portability problems.
Using Crypto's version of the hashes would be another option.
I need to benchmark it. The SHA2 library (which provides SHA1 also,
confusing name) may be the fastest option, but is not currently in Debian.
|
| |
|
|
|
|
|
|
| |
This *almost* works.
Along the way, I noticed that the --uuid parameter was being accidentially
passed after the --, so that has never been actually used by
git-annex-shell to verify it's running in the expected repository. Oops. Fixed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In order to record a semi-useful filename associated with the key,
this required plumbing the filename all the way through to the remotes'
storeKey and retrieveKeyFile.
Note that there is potential for deadlock here, narrowly avoided.
Suppose the repos are A and B. A sends file foo to B, and at the same
time, B gets file foo from A. So, A locks its upload transfer info file,
and then locks B's download transfer info file. At the same time,
B is taking the two locks in the opposite order. This is only not a
deadlock because the lock code does not wait, and aborts. So one of A or
B's transfers will be aborted and the other transfer will continue.
Whew!
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
is already in progress by another process.
Note this is per-remote, so trying to get the same file from multiple
remotes can still let duplicate downloads run. (And uploading the same file
to multiple remotes is not duplicate at all of course.)
get, move, and copy are the only git-annex subcommands that transfer
files, but there's still git-annex-shell recvkey and sendkey to deal with too.
I considered modifying retrieveKeyFile or getViaTmp, but they are called
by other code that does not involve expensive file transfers (migrate)
or that does file transfers that should not be checked by this (fsck --from).
|
Joey Hess