Added a comment: Problem still occurs but maybe my update did not work
This commit is contained in:
parent
87c487474c
commit
be4727381d
1 changed files with 24 additions and 0 deletions
|
@ -0,0 +1,24 @@
|
|||
[[!comment format=mdwn
|
||||
username="https://www.google.com/accounts/o8/id?id=AItOawmp1ThsNNAbSn46ju-gwFELfStlhl8usJo"
|
||||
nickname="donkeyicydragon"
|
||||
subject="Problem still occurs but maybe my update did not work"
|
||||
date="2014-03-16T18:01:24Z"
|
||||
content="""
|
||||
Hi Joey, thanks for the quick response.
|
||||
|
||||
I tried to update and retry my \"git annex unused\" but it gave the same error. Maybe my updating did not work (see below). But is there a way I can retry it without running \"git annex unused\" again? The problem is that each run takes several hours with my amount of files.
|
||||
It would be nice, if git annex recognized some error in the last approach and recovered.
|
||||
The tmp files that are created by \"git annex unused\" are still in .git/annex/.
|
||||
|
||||
|
||||
Regarding the updating:
|
||||
I tried to obtain the autobuild version but on this website I could not find a link to download the latest autobuild. I could only find the build reports. But I used the git annex installer script from https://github.com/zerodogg/scriptbucket/blob/master/gitannex-install
|
||||
and it apparently knows the location of the daily build. Is this the autobuild or is git annex autobuilt more often?
|
||||
|
||||
This is my version after installing it yesterday evening approx. 2h hours after your answer to the bug description.
|
||||
|
||||
git-annex version: 5.20140314-g48e0f18
|
||||
build flags: Assistant Webapp Webapp-secure Pairing Testsuite S3 WebDAV Inotify DBus XMPP DNS Feeds Quvi TDFA CryptoHash
|
||||
key/value backends: SHA256E SHA1E SHA512E SHA224E SHA384E SKEIN256E SKEIN512E SHA256 SHA1 SHA512 SHA224 SHA384 SKEIN256 SKEIN512 WORM URL
|
||||
remote types: git gcrypt S3 bup directory rsync web webdav tahoe glacier hook external
|
||||
"""]]
|
Loading…
Add table
Reference in a new issue