| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
|
|
|
| |
webapp: Adds newly created repositories to one of these groups:
clients, drives, servers
This is heuristic, but it's a pretty good heuristic, and can always be
configured.
|
| |
|
|
|
|
|
|
|
| |
Both when queueing downloads, and uploads, consults the preferred content
settings.
I didn't make it check yet when requeing failed transfers or queuing
deferred downloads; dealing with the preferred content settings (or indeed,
other settings) changing while the assistant is running still needs work.
|
| | |
|
| |
|
|
|
| |
With --from, it needs to examine the preferred content of the repository
being dropped from, instead of the local repository.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
webapp.
|
| |
|
|
|
|
|
|
|
|
|
| |
repository configuration settings stored in the git-annex branch.
Incomplete; I need to finish parsing and saving. This will also be used
for editing transfer control expresssions.
Removed the group display from the status output, I didn't really
like that format, and vicfg can be used to see as well as edit rempository
group membership.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Makes it safe to use git annex unlock with the watcher/assistant.
And also to mix use of the watcher/assistant with regular files stored in git.
Long ago, I had avoided doing this check, except during the startup scan,
because it would be slow to run ls-files repeatedly.
But then I added the lsof check, and to make that fast, got it to detect
batch file adds. So let's move the ls-files check to also occur when it'll
have a batch, and can check them all with one call.
This does slow down adding a single file by just a bit, but really only
a little bit. (The lsof check is probably more expensive.) It also
speeds up the startup scan, especially when there are lots of new files
found by the scan.
Also, fixed the sleep for annex.delayadd to not run while the threadstate
lock is held, so it doesn't unnecessarily freeze everything else.
Also, --force no longer makes it skip the lsof check, which was not
documented, and seems never a good idea.
|
| |
|
|
|
| |
--copies=group:number can now be used to match files that are present in a
specified number of repositories in a group.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
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
|
Joey Hess