| Commit message (Collapse) | Author | Age |
|
|
|
| |
template haskell and thus yesod. (Should be available for arm soonish I hope).
|
| |
|
|
|
|
|
| |
Systems like Debian that have the old yesod 1.0.1 should set
GIT_ANNEX_LOCAL_FEATURES=-DWITH_OLD_YESOD
|
| |
|
|
|
|
|
|
|
| |
At recommends it causes avahi-daemon to be pulled in on upgrade, which is
just too annoying to deal with avoiding on servers. MDNS is needed for
robust peering, but probably most desktop systems have it anyway; it's in
task-desktop.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Really the fix here is to make Utility.Process only throw IOErrors,
which is what I naturally assumed it'd throw.
|
| |
|
|
|
|
| |
monthly incremental fsck runs in cron jobs.
|
|
|
|
| |
specified amount of time.
|
| |
|
| |
|
|
|
|
|
| |
git annex copy --to remote often does not need to copy a file,
but it was still updating the location log in this case.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This means that anyone serving up the webapp to users as a service
(ie, without providing any git-annex binary at all to the user) still needs
to provide a link to the source code for it, including any modifications
they may make.
This may make git-annex be covered by the AGPL as a whole when it is built
with the webapp. If in doubt, you should ask a lawyer.
When git-annex is built with the webapp disabled, no AGPLed code is used.
Even building in the assistant does not pull in AGPLed code.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
directly to remote/git-annex.
This fixes a problem I was seeing in the assistant where two remotes would
attempt to sync with one another at the same time, and both failed pushing
the diverged git-annex branch. Then when both tried to resolve the failed
push, they each modified their git-annex branch, which again each blocked
the other from pushing into it. The result was that the git-annex
branches were perpetually diverged (despite having the same content!) and
once the assistant fell into this trap, it couldn't get out and always
had to do the slow push/fail/pull/merge/push/fail cycle.
|
|
|
|
| |
files and reading from checksum commands.
|
|
|
|
| |
than moving to .git/annex/bad/
|
| |
|
|
|
|
| |
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..
|
|\| |
|