mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Merge branch 'master' of ssh://git-annex.branchable.com

Browse source
This commit is contained in:
Joey Hess 2014-10-15 14:37:54 -04:00
commit 0a142fdd83
9 changed files with 117 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

8
doc/bugs/Build_error_with_Yesod_1.4/comment_1_42fe9d62c9dcc55deea35d16b67177e6._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawnmF_9CAtfqdZkC4e-_dCX-rK5bqh4RWkw"
nickname="Carl"
subject="Not on hackage"
date="2014-10-15T15:34:02Z"
content="""
I stand corrected, but it seems this release is not on hackage?
"""]]

8
doc/bugs/Build_error_with_Yesod_1.4/comment_2_05f6fb19f2527f6dd72ab0e2f87c021a._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.111"
subject="comment 2"
date="2014-10-15T17:30:45Z"
content="""
Hmm, yeah, it seems the upload to hackage failed, because hackage still rejects cabal files mentioning the legal os(gnu). Sigh. Fixed now.
"""]]

10
doc/forum/Copying_to_S3_does_not_work_-_chunking_does_not_work/comment_1_ec390a7d521c697eb6b17e8db1dc9d1d._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.111"
subject="comment 1"
date="2014-10-15T15:25:14Z"
content="""
You're using an old version of git-annex from before the recent complete rewrite of the chunking code. That old version did not support chunking for S3. QED. Upgrade.
Note that your configuration has both the chunksize= and chunk= set. This is not a good idea, since they enable different types of chunking that are not compatible. If I were you, I'd delete that special remote and make a new one after upgrading, and be careful to only set `chunk=` in that new one.
"""]]

10
doc/forum/Copying_to_S3_does_not_work_-_chunking_does_not_work/comment_2_14a584567ef42d5b7955ee970200e74d._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://digiuser.livejournal.com/"
ip="67.161.4.185"
subject="Homebrew"
date="2014-10-15T15:37:34Z"
content="""
Oh, ok, thank you. I am using the latest version from homebrew. Is there a way to get homebrew to install the latest version?
Thanks.
"""]]

10
doc/forum/Copying_to_S3_does_not_work_-_chunking_does_not_work/comment_3_6cbd7329f1f11edf8dd90df27d45158f._comment Normal file
View file

@ -0,0 +1,10 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="209.250.56.111"
subject="comment 3"
date="2014-10-15T17:25:27Z"
content="""
I think that if you have installed all the build deps for git-annex using homebrew, you should be able to just install git-annex from source.
Or, ask the homebrewers to update the package there..
"""]]

8
doc/forum/Git_annex_hangs/comment_4_2ba5992c32753ed03ddd5c12264e9acf._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawnjssENdbjzvblxOm4Qr8x2C-BdIV_k_y4"
nickname="Tadeusz"
subject="comment 4"
date="2014-10-15T15:25:27Z"
content="""
I will look into PPA. I hope it won't be this slow:) How long would it take for git annex to add/modify/sync files (~100) taking up 100GB or so? Days? Hours? Minutes?
"""]]

47
doc/forum/how_to_set_up_syncing_for_multiple_computer_and_a_centralized_backup_unit/comment_3_2ad4c1a4bfe00c22444ab878c84a8830._comment Normal file
View file

@ -0,0 +1,47 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawncVeolylM8VoRbWhIYDlfGhIP69-aNXm4"
nickname="Espen"
subject="comment 3"
date="2014-10-15T17:32:10Z"
content="""
Finally had some time today to lock at the logs. However, I started from scratch. Created a local repo with the assistant, transferred some real files into the local repo dir (not .git of course). Waiting until everything was added etc. Then I created the remote server repo and it immediately started to transfer files from the local repo to the remote. Then I was slightly surprised when I got back home and saw this in the logfile:
----- cut -----
somefile
32,768 1% 0.00kB/s 0:00:00 To ssh://someserverrepodir
* [new branch] git-annex -> synced/git-annex
* [new branch] annex/direct/master -> synced/master
error: Ref refs/heads/synced/git-annex is at 112bb35566a0ee9434fb74524cdced45792bf8ed but expected 0000000000000000000000000000000000000000
error: Ref refs/heads/synced/master is at d593f3c3a5090009789154bd60c3390d9a1b90d6 but expected 0000000000000000000000000000000000000000
remote: error: failed to lock refs/heads/synced/git-annex
remote: error: failed to lock refs/heads/synced/master
To ssh://someserverrepodir
! [remote rejected] git-annex -> synced/git-annex (failed to lock)
! [remote rejected] annex/direct/master -> synced/master (failed to lock)
error: failed to push some refs to 'ssh://someserverrepodir'
1,966,080 96% 1.73MB/s 0:00:00
2,034,254 100% 1.79MB/s 0:00:01 (xfr#1, to-chk=0/1)
fatal: 'someserverrepodescription' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: 'someserverrepodescription' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: 'someserverrepodescription' does not appear to be a git repository
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
[2014-10-13 21:58:05 CEST] Transferrer: Uploaded somefile
----- cut -----
This was a total surprise to me. If this was the stuff that made the previous setup fail, I don not know, but I will try to track down this error first. I would be quite surprised if it indeed was a permission issue. Also visible is an upload session for one of the files...that seems to go on fine and is probably not related to the error at all. This was the only error printed once during the entire transfer/sync process. Thought the first thing I would check was the size and number of files in the local and remote directory, but I'm not really sure how to do this with all the git stuff around on the remote. Typically \"git ls-files | wc -l\" or similar gets me going on the local repo. How would I do this on the remote (in backup mode if that counts)?
"""]]

8
doc/forum/how_to_set_up_syncing_for_multiple_computer_and_a_centralized_backup_unit/comment_4_44639388349a9ea5eabda9ebf79817b3._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawncVeolylM8VoRbWhIYDlfGhIP69-aNXm4"
nickname="Espen"
subject="comment 4"
date="2014-10-15T17:34:52Z"
content="""
Sorry, forgot to format the text and the typo. Can I edit my own comments?
"""]]

8
doc/forum/how_to_set_up_syncing_for_multiple_computer_and_a_centralized_backup_unit/comment_5_339123ab87b69b11d6e999ad6eaf6df5._comment Normal file
View file

@ -0,0 +1,8 @@
[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawncVeolylM8VoRbWhIYDlfGhIP69-aNXm4"
nickname="Espen"
subject="comment 5"
date="2014-10-15T17:44:55Z"
content="""
Did a quick \"du -h\" on both directories. Local is 27 and remote is 23.7 GB, so some data is obviously missing on the remote. Also, how do I increase either the permitted size of one log file, or the number of log files stored? Seems the logs where rotated over the whole allowed log batch and size before the job was done during the night, so difficult to tell if there were more errors.
"""]]