diff options
Diffstat (limited to 'doc/bugs')
4 files changed, 135 insertions, 0 deletions
diff --git a/doc/bugs/Numcopies_not_checked_when_running_with_--all.mdwn b/doc/bugs/Numcopies_not_checked_when_running_with_--all.mdwn new file mode 100644 index 000000000..87063c2dd --- /dev/null +++ b/doc/bugs/Numcopies_not_checked_when_running_with_--all.mdwn @@ -0,0 +1,24 @@ +### Please describe the problem. +There are a lot of differences in the behaviour of usual commands and commans using --all. +The specific problem I found was that "git annex fsck --all" will only checksum it seems and not report back numcopies failures. +Checking if objects/old versions have propagated is not possible without it or do I miss something. + +(As additional note not sure if related. It seems that git annex fsck --all is running much faster in my tests 1/3 faster. Any reason for that? Bug related?) + + +### What steps will reproduce the problem? +compare "git annex fsck" vs "git annex fsck" (no numcopies check) + +### What version of git-annex are you using? On what operating system? +git-annex version: 5.20140210-gd99db49 +Linux (Ubuntu 13.10) + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log + + +# End of transcript or log. +"""]] diff --git a/doc/bugs/can__39__t_drop_unused_files_that_never_were_added.mdwn b/doc/bugs/can__39__t_drop_unused_files_that_never_were_added.mdwn new file mode 100644 index 000000000..9fedf8955 --- /dev/null +++ b/doc/bugs/can__39__t_drop_unused_files_that_never_were_added.mdwn @@ -0,0 +1,81 @@ +### Please describe the problem. + +When adding files to the annex and then deciding against it in an "unusual" way, git-annex gets confused and the file left behind can't be removed from the annex... + +### What steps will reproduce the problem? + +1. Add file with "git annex add" +2. Decide you don't need the file add all +3. "git rm -f newfile" +4. "git annex unused" +5. "git annex dropunused all" + +### What version of git-annex are you using? On what operating system? + +git-annex version: 5.20140210 on Debian unstable + +### Please provide any additional information below. + +[[!format sh """ +# If you can, paste a complete transcript of the problem occurring here. +# If the problem is with the git-annex assistant, paste in .git/annex/daemon.log +$ git init +Initialized empty Git repository in /tmp/foo/.git/ +$ ls -l +total 0 +$ cp ~/download/hub-ctrl.c . +$ git add hub-ctrl.c +$ git commit +[master (root-commit) ed7eb68] A file. + 1 file changed, 412 insertions(+) + create mode 100644 hub-ctrl.c +$ cp ~/download/hub-ctrl . +$ ls -l +total 28 +-rwxr-xr-x 1 tobias tobias 14130 Feb 19 00:49 hub-ctrl +-rw-r--r-- 1 tobias tobias 9270 Feb 19 00:48 hub-ctrl.c +$ git annex init +init ok +(Recording state in git...) +$ git annex add +add hub-ctrl ok +(Recording state in git...) +$ git status +On branch master +Changes to be committed: + (use "git reset HEAD <file>..." to unstage) + + new file: hub-ctrl + +$ git rm hub-ctrl +error: the following file has changes staged in the index: + hub-ctrl +(use --cached to keep the file, or -f to force removal) +$ git rm -f hub-ctrl +rm 'hub-ctrl' +$ git status +On branch master +nothing to commit, working directory clean +$ git annex unused +unused . (checking for unused data...) (checking HEAD...) + Some annexed data is no longer used by any files: + NUMBER KEY + 1 SHA256E-s14130--d4e777ba2b99ed0a520fbabe7b93cf2165373b4945afe8dcb626231d9051f19d + (To see where data was previously used, try: git log --stat -S'KEY') + + To remove unwanted data: git-annex dropunused NUMBER + +ok +$ git annex dropunused all +dropunused 1 (unsafe) + Could only verify the existence of 0 out of 1 necessary copies + + Rather than dropping this file, try using: git annex move + + (Use --force to override this check, or adjust numcopies.) +failed +git-annex: dropunused: 1 failed +$ + +# End of transcript or log. +"""]] diff --git a/doc/bugs/git_repo_fails_to_checkout.mdwn b/doc/bugs/git_repo_fails_to_checkout.mdwn new file mode 100644 index 000000000..1981ad68f --- /dev/null +++ b/doc/bugs/git_repo_fails_to_checkout.mdwn @@ -0,0 +1,22 @@ +### Please describe the problem. + +Attempting to clone the git repository produces + + (master) cayley:git-annex% git checkout -f HEAD + error: unable to create file doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__.mdwn (File name too long) + fatal: cannot create directory at 'doc/bugs/fatal:_unable_to_access___39__..__47__..__47__..__47__..__47__C:__92__Users__92____91__...__93____92__annex__92__.git__47__config__39__:_Invalid_argument___40__Windows__41__': File name too long + +### What steps will reproduce the problem? + +I get the above with either + + git clone https://github.com/joeyh/git-annex + +or (after this fails) retrying with + + cd git-annex + git checkout -f HEAD + +### What version of git-annex are you using? On what operating system? + +I am running git 1.9.0 from git (5f95c9f850b19b368c43ae399cc831b17a26a5ac in the git git repo) on Ubuntu 13.04. diff --git a/doc/bugs/git_repo_fails_to_checkout/comment_1_d92e7e3b41382501a08f6a66c673b1fd._comment b/doc/bugs/git_repo_fails_to_checkout/comment_1_d92e7e3b41382501a08f6a66c673b1fd._comment new file mode 100644 index 000000000..55e063f39 --- /dev/null +++ b/doc/bugs/git_repo_fails_to_checkout/comment_1_d92e7e3b41382501a08f6a66c673b1fd._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="http://geoffreyirving.myopenid.com/" + nickname="Geoffrey Irving" + subject="encrypted home directory" + date="2014-02-18T18:05:24Z" + content=""" +It looks like this problem is related to using an encrypted home directory. +"""]] |