summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* close bugGravatar Joey Hess2015-10-09
|
* improve display when lockcontent failsGravatar Joey Hess2015-10-09
| | | | | | | | /dev/null stderr; ssh is still able to display a password prompt despite this Show some messages so the user knows it's locking a remote, and knows if that locking failed.
* implement lockContent for ssh remotesGravatar Joey Hess2015-10-09
|
* cleanup changelogGravatar Joey Hess2015-10-09
|
* also generate a drop safety proof for move --from remoteGravatar Joey Hess2015-10-09
|
* tests and verified that the bug is fixed, in all the cases I identifiedGravatar Joey Hess2015-10-09
|
* fix local dropping to not require extra locking of copies, but only that the ↵Gravatar Joey Hess2015-10-09
| | | | local copy be locked for removal
* improve message when drop failed due to no locked copyGravatar Joey Hess2015-10-09
|
* rename constructorGravatar Joey Hess2015-10-09
|
* verify local copy of content with lockingGravatar Joey Hess2015-10-09
|
* display drop safety proofs in debug modeGravatar Joey Hess2015-10-09
|
* fix lockKey to run callback in original Annex monad, not local remote'sGravatar Joey Hess2015-10-09
|
* content locking during drop working for local git remotesGravatar Joey Hess2015-10-09
| | | | Only ssh remotes lack locking now
* finish and use lockContent interfaceGravatar Joey Hess2015-10-09
|
* improve drop proof codeGravatar Joey Hess2015-10-09
|
* refactorGravatar Joey Hess2015-10-09
|
* TrustedCopy is good enough to allow droppingGravatar Joey Hess2015-10-08
| | | | | | | By definition, a trusted repository is trusted to always have its location tracking log accurate. Thus, it should never be in a position where content is being dropped from it concurrently, as that would result in the location tracking log not being accurate.
* try harder to verify until at least one VerifiedCopyLock is obtainedGravatar Joey Hess2015-10-08
| | | | | | | | | This avoids a failure where eg, we start with RecentlyVerifiedCopies for all remotes, and so didn't do any active verification, which is required. Also, dedup the list of VerifiedCopies when checking if we have enough, in case 2 copies of a UUID slip in.
* require 1 locked copy while dropping from local or a remoteGravatar Joey Hess2015-10-08
| | | | | | | | | See doc/bugs/concurrent_drop--from_presence_checking_failures.mdwn for discussion about why 1 locked copy is all we can require, and how this fixes concurrent dropping bugs. Note that, since nothing yet generates a VerifiedCopyLock yet, this commit breaks dropping temporarily.
* support invalidating existing VerifiedCopysGravatar Joey Hess2015-10-08
|
* add VerifiedCopy data typeGravatar Joey Hess2015-10-08
| | | | | | | | | There should be no behavior changes in this commit, it just adds a more expressive data type and adjusts code that had been passing around a [UUID] or sometimes a Maybe Remote to instead use [VerifiedCopy]. Although, since some functions were taking two different [UUID] lists, there's some potential for me to have gotten it horribly wrong.
* add removeKey action to RemoteGravatar Joey Hess2015-10-08
| | | | | Not implemented for any remotes yet; probably the git remote is the only one that will ever implement it.
* unused importGravatar Joey Hess2015-10-08
|
* I think this comment is stale/confusing; removeGravatar Joey Hess2015-10-08
|
* git-annex-shell: Added lockcontent command, to prevent dropping of key's ↵Gravatar Joey Hess2015-10-08
| | | | content.
* add lockContentSharedGravatar Joey Hess2015-10-08
| | | | | | | | Also, rename lockContent to lockContentExclusive inAnnexSafe should perhaps be eliminated, and instead use `lockContentShared inAnnex`. However, I'm waiting on that, as there are only 2 call sites for inAnnexSafe and it's fiddly.
* export FileMode typeGravatar Joey Hess2015-10-08
|
* add tryLockSharedGravatar Joey Hess2015-10-08
|
* open lock file ReadOnly when taking shared lockGravatar Joey Hess2015-10-08
| | | | It's only necessary to open a file for write when taking an exclusive lock.
* getting proof-yGravatar Joey Hess2015-10-07
|
* Debian: Remove dependency on transformers library, as it is now included in ghc.Gravatar Joey Hess2015-10-07
| | | | Backporters will need to revert this.
* titlesGravatar Joey Hess2015-10-07
|
* indentsGravatar Joey Hess2015-10-07
|
* alternative solutionGravatar Joey Hess2015-10-07
|
* analysis of some topologies, and idea to generate movesGravatar Joey Hess2015-10-07
|
* Debian: Add torrent library to build-depends as it's packaged now, and stop ↵Gravatar Joey Hess2015-10-07
| | | | recommending bittornado | bittorrent.
* be verbose to debug problem with awsGravatar Joey Hess2015-10-06
|
* add test cases for copy --autoGravatar Joey Hess2015-10-06
| | | | | | (Only --from for now, should add --to sometime but I'm on low sleep so this is the mininal test to catch the reversion just fixed, bad me for doing it backwards and incompletely.)
* copy --auto was checking the wrong repo's preferred content. (--from was ↵Gravatar Joey Hess2015-10-06
| | | | checking what --to should, and vice-versa.) Fixed this bug, which was introduced in version 5.20150727.
* oops, didn't mean to commit this debugGravatar Joey Hess2015-10-06
|
* analysisGravatar Joey Hess2015-10-06
|
* commentGravatar Joey Hess2015-10-06
|
* force installing older warp; current fails to buildGravatar Joey Hess2015-10-06
|
* sed out the filename from sha1sum outputGravatar Joey Hess2015-10-06
|
* hopefuly fix sha1sum calling; also refactor and check downloaded program's ↵Gravatar Joey Hess2015-10-06
| | | | sha before using it
* confirmedGravatar Joey Hess2015-10-06
|
* Merge branch 'master' of ssh://git-annex.branchable.comGravatar Joey Hess2015-10-06
|\
* | responseGravatar Joey Hess2015-10-06
| |
| * Add some precision about the versions tested and why it is a bug in mind opinionGravatar konubinix2015-10-06
| |
* | responseGravatar Joey Hess2015-10-06
| |