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

remove old closed bugs and todo items to speed up wiki updates and reduce size

Browse source 
Remove closed bugs and todos that were last edited or commented before 2020.

Except for ones tagged projects/* since projects like datalad want to keep
around records of old deleted bugs longer.

Command line used:

for f in $(grep -l '|done\]\]' -- ./*.mdwn); do if ! grep -q "projects/" "$f"; then d="$(echo "$f" | sed 's/.mdwn$//')"; if [ -z "$(git log --since=01-01-2020 --pretty=oneline -- "$f")" -a -z "$(git log --since=01-01-2020 --pretty=oneline -- "$d")" ]; then git rm -- "./$f" ; git rm -rf "./$d"; fi; fi; done
for f in $(grep -l '\[\[done\]\]' -- ./*.mdwn); do if ! grep -q "projects/" "$f"; then d="$(echo "$f" | sed 's/.mdwn$//')"; if [ -z "$(git log --since=01-01-2020 --pretty=oneline -- "$f")" -a -z "$(git log --since=01-01-2020 --pretty=oneline -- "$d")" ]; then git rm -- "./$f" ; git rm -rf "./$d"; fi; fi; done
This commit is contained in:
Joey Hess 2021-06-21 13:10:13 -04:00
parent 4eb3778aec
commit a6a6217322
No known key found for this signature in database
GPG key ID: DB12DB0FF05F8F38
1141 changed files with 1 additions and 32370 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

40
doc/bugs/20151116_tests_fail_on_OS_X.mdwn
View file

@ -1,40 +0,0 @@
Test output on OS X. Btw, the previous version works:
```
OK (4.87s)
map: OK (0.33s)
uninit: Deleted branch git-annex (was 9a28b38).
OK (0.38s)
uninit (in git-annex branch): Switched to branch 'git-annex'
OK (0.26s)
upgrade: OK (0.21s)
whereis: OK (0.61s)
hook remote: OK (0.91s)
directory remote: OK (0.85s)
rsync remote: OK (1.40s)
bup remote: Reinitialized existing Git repository in /private/var/folders/4j/br7bdhjx4b384_snb2087gt00000gn/T/nix-build-git-annex-5.20151116.drv-0/.bup/
Initialized empty Git repository in /private/var/folders/4j/br7bdhjx4b384_snb2087gt00000gn/T/nix-build-git-annex-5.20151116.drv-0/git-annex-5.20151116/.t/tmprepo0/dir/
content cannot be completely removed from bup remote
OK (2.62s)
crypto: OK (4.16s)
preferred content: OK (1.97s)
add subdirs: Merge made by the 'recursive' strategy.
conflictor.variant-cc12 | 1 +
conflictor/subfile | 1 +
2 files changed, 2 insertions(+)
create mode 120000 conflictor.variant-cc12
create mode 120000 conflictor/subfile
To /private/var/folders/4j/br7bdhjx4b384_snb2087gt00000gn/T/nix-build-git-annex-5.20151116.drv-0/git-annex-5.20151116/.t/repo
e4d3d14..60148c4 git-annex -> synced/git-annex
efda76d..f76baae master -> synced/master
OK (0.55s)
addurl: git-annex: .git/annex/objects/2Q/J8/SHA256E-s3--2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae/SHA256E-s3--2c26b46b68ffc68ff99b453c1d30413413422d706483bfa0f98a5e886266e7ae: createSymbolicLink: invalid argument (File name too long)
FAIL (0.29s)
addurl failed on file:///private/var/folders/4j/br7bdhjx4b384_snb2087gt00000gn/T/nix-build-git-annex-5.20151116.drv-0/git-annex-5.20151116/.t/tmprepo0/myurl
2 out of 150 tests failed (126.13s)
(This could be due to a bug in git-annex, or an incompatibility
with utilities, such as git, installed on this system.)
```
> [[fixed|done]] --[[Joey]]

15
doc/bugs/20151116_tests_fail_on_OS_X/comment_1_6c5cfe02b686d063e8f336620a81cca1._comment
View file

@ -1,15 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2015-11-30T19:22:43Z"
content="""
You may have omitted 1 of the 2 failures in your paste.
The only one I see has something to do with a filename being too long.
Since the filename in question is 77 bytes long, or 178 with the full path,
and industry standard for filename size is 1024 or longer, I am at a loss
why that would be considered too long.
AFAIK there have been no changes in git-annex's filenames recently. What
was the previous version that worked?
"""]]

12
doc/bugs/20151116_tests_fail_on_OS_X/comment_2_59f7803b9a9ee939a8a50605fe5c4682._comment
View file

@ -1,12 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2015-12-06T20:02:49Z"
content="""
Ok, this involves where the test suite is run.
The addurl test adds `file://`pwd`/somefile`, and that will create a file
with a name like `_home_you_sub_dir_path_here_somefile`. Which can easily
exceed filename length limits of 255 bytes.
There was indeed a reversion in addurl's handling of that.
"""]]

63
doc/bugs/7.20181105+git172-g76fc9af4_not_buildable.mdwn
View file

@ -1,63 +0,0 @@
first ran into on my laptop and just thought that my setup is outdated... this is now in clean uptodate debian sid
[[!format sh """
Annex/Ssh.hs:207:25: error:
* Couldn't match type `IO' with `Annex'
Expected type: Annex ()
Actual type: IO ()
* In the second argument of `($)', namely
`unlessM (tryssh ["-o", "BatchMode=true"])
$ do liftIO $ print "ok then"
let p = ... in p `concurrently` p'
In the second argument of `($)', namely
`whenM (isNothing <$> fromLockCache socketlock)
$ unlessM (tryssh ["-o", "BatchMode=true"])
$ do liftIO $ print "ok then"
let p = ... in p `concurrently` p'
In the expression:
debugLocks
$ whenM (isNothing <$> fromLockCache socketlock)
$ unlessM (tryssh ["-o", "BatchMode=true"])
$ do liftIO $ print "ok then"
let p = ... in p `concurrently` p
|
207 | unlessM (tryssh ["-o", "BatchMode=true"]) $ do
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^...
Annex/Ssh.hs:213:70: error:
* Couldn't match expected type `IO a0' with actual type `Annex ()'
* In the first argument of `concurrently', namely `p'
In the expression: p `concurrently` p
In a stmt of a 'do' block:
let p = void $ prompt $ tryssh [] in p `concurrently` p
|
213 | let p = void $ prompt $ tryssh [] in p `concurrently` p
| ^
Annex/Ssh.hs:213:70: error:
* Couldn't match type `(a0, b0)' with `()'
Expected type: IO ()
Actual type: IO (a0, b0)
* In the expression: p `concurrently` p
In a stmt of a 'do' block:
let p = void $ prompt $ tryssh [] in p `concurrently` p
In the second argument of `($)', namely
`do liftIO $ print "ok then"
let p = ... in p `concurrently` p'
|
213 | let p = void $ prompt $ tryssh [] in p `concurrently` p
| ^^^^^^^^^^^^^^^^^^
Annex/Ssh.hs:213:87: error:
* Couldn't match expected type `IO b0' with actual type `Annex ()'
* In the second argument of `concurrently', namely `p'
In the expression: p `concurrently` p
In a stmt of a 'do' block:
let p = void $ prompt $ tryssh [] in p `concurrently` p
|
213 | let p = void $ prompt $ tryssh [] in p `concurrently` p
| ^
"""]]
> [[fixed|done]] --[[Joey]]

29
doc/bugs/8_unit_tests_fail.mdwn
View file

@ -1,29 +0,0 @@
### Please describe the problem.
8 out of 293 tests failed (200.39s)
(This could be due to a bug in git-annex, or an incompatibility
with utilities, such as git, installed on this system.)
full log https://headcounter.org/hydra/build/1819294/nixlog/1
### What steps will reproduce the problem?
./make test
### What version of git-annex are you using? On what operating system?
6.20170510
nix-build and inside a nix shell with manual building.
### Please provide any additional information below.
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yep, works apart from the few tests that fail.
> Duplicate of [[git-annex_in_nixpkgs_fails_with_git-2.13.0]]; closing. [[done]] --[[Joey]]

86
doc/bugs/Aborts_with_SQLite_error_when_dropping_contents.mdwn
View file

@ -1,86 +0,0 @@
(Found the problem, so you might want to skip to the comments to see
what's wrong.)
### Please describe the problem.
Trying to drop the contents of 131 files in a subdirectory, but it dies
with an "sqlite worker thread crashed" error. The contents of one file
is deleted, and then it dies. The files in that directory are exactly 1G
(1000000000) bytes each.
There's no data loss here, it creates files in `.git/annex/journal/`
which is added to the git-annex branch after a git annex sync. "git
annex fsck --fast --quiet" is happy and finds no errors.
### What steps will reproduce the problem?
"git annex drop" with and without --force. Tried to copy one of the
files to another server with Debian 8.7, and it's successfully dropped
there. Same git-annex version.
### What version of git-annex are you using? On what operating system?
OS: Ubuntu 14.04.5 LTS
git-annex: 6.20161211-gc3ab3c668 (from
`git-annex-standalone-amd64.tar.gz` in the annex at
downloads.kitenet.net)
I have compiled the newest sqlite3 3.16.2 and placed it in
/usr/local/bin/, just mentioning it because it's some kind of SQLite
error. but executing the command with a PATH without /usr/local/bin
makes no difference.
### Please provide any additional information below.
# 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 annex drop -d --force
[2017-01-16 08:58:39.947856861] read: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","ls-files","--cached","-z","--"]
[2017-01-16 08:58:39.953150944] chat: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","check-attr","-z","--stdin","annex.backend","annex.numcopies","annex.largefiles","--"]
[2017-01-16 08:58:39.953742873] read: git ["--version"]
[2017-01-16 08:58:39.959438053] process done ExitSuccess
[2017-01-16 08:58:39.959919735] read: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","show-ref","git-annex"]
[2017-01-16 08:58:39.963707897] process done ExitSuccess
[2017-01-16 08:58:39.963882344] read: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"]
[2017-01-16 08:58:39.967078602] process done ExitSuccess
[2017-01-16 08:58:39.969062554] chat: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","cat-file","--batch"]
[2017-01-16 08:58:39.970168767] chat: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","cat-file","--batch-check=%(objectname) %(objecttype) %(objectsize)"]
drop MyStream_3/MyStream_3.mp4.split_ag [2017-01-16 08:58:39.984359273] Dropping from here proof: Nothing
sqlite worker thread crashed: SQLite3 returned ErrorCan'tOpen while attempting to perform prepare "SELECT null from content limit 1": unable to open database file
ok
git-annex: thread blocked indefinitely in an MVar operation
$ git annex drop -d --force
[2017-01-16 08:58:58.890031175] read: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","ls-files","--cached","-z","--"]
[2017-01-16 08:58:58.895047131] chat: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","check-attr","-z","--stdin","annex.backend","annex.numcopies","annex.largefiles","--"]
[2017-01-16 08:58:58.895690334] read: git ["--version"]
[2017-01-16 08:58:58.901206493] process done ExitSuccess
[2017-01-16 08:58:58.901836453] read: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","show-ref","git-annex"]
[2017-01-16 08:58:58.905632574] process done ExitSuccess
[2017-01-16 08:58:58.905793223] read: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"]
[2017-01-16 08:58:58.909227509] process done ExitSuccess
[2017-01-16 08:58:58.910902084] chat: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","cat-file","--batch"]
[2017-01-16 08:58:58.912164764] chat: git ["--git-dir=../../../../../../../.git","--work-tree=../../../../../../..","--literal-pathspecs","cat-file","--batch-check=%(objectname) %(objecttype) %(objectsize)"]
drop MyStream_3/MyStream_3.mp4.split_ah [2017-01-16 08:58:58.927477693] Dropping from here proof: Nothing
sqlite worker thread crashed: SQLite3 returned ErrorCan'tOpen while attempting to perform prepare "SELECT null from content limit 1": unable to open database file
ok
git-annex: thread blocked indefinitely in an MVar operation
$
# End of transcript or log.
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Indeed. All my stuff (around 3.5 terabytes) is stored in git-annex with
at least three copies of each file on different disks and locations,
spread over various hard disks, memory sticks, servers and you name it.
Unused disk space is a waste, so I fill everything up to the brim with
extra copies.
In other words, Git-Annex and I are very happy together, and I'd like to
marry it. And because you are the father, I hereby respectfully ask for
your blessing.
> [[fixed|done]] (and I suppose you have my blessing, but I'm not sure
> that's legal yet!) --[[Joey]]

8
doc/bugs/Aborts_with_SQLite_error_when_dropping_contents/comment_1_cd09e4d4a73e003735e3297922b8faa8._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="sunny256"
avatar="http://cdn.libravatar.org/avatar/8a221001f74d0e8f4dadee3c7d1996e4"
subject="Found the reason"
date="2017-01-16T11:03:45Z"
content="""
I managed to find the reason why it failed. The files in .git/annex/keys/ had wrong permissions, so I wasn't able to write to them. This is a shared repository where everyone within the Unix group can read and write. All the directories including .git/annex/keys have chmod +s so any additions or edits are stored within the correct group. But the SQLite files were stored with permission 0644 instead of 0664, and my umask in the shell is 0002. Maybe SQLite is creating the database with wrong permissions?
"""]]

8
doc/bugs/Aborts_with_SQLite_error_when_dropping_contents/comment_2_9a0fec331a858746e2fecc6b86ab8cbb._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="sunny256"
avatar="http://cdn.libravatar.org/avatar/8a221001f74d0e8f4dadee3c7d1996e4"
subject="Wrong permissions"
date="2017-01-16T11:17:31Z"
content="""
Yes, confirmed. I tried to create a new test repository and chmod all directories with +s. I'm using umask 0002, so new files are created with perm 0664 and the correct shared group. But the SQLite files in .git/annex/keys/ are created with permission 0644, so other users in the group are not able to update the files there.
"""]]

53
doc/bugs/Aborts_with_SQLite_error_when_dropping_contents/comment_3_88a09558f2da0a5733aa3dd042f9d59b._comment
View file

@ -1,53 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2017-02-13T20:21:09Z"
content="""
Thanks for following up with the cause of this.
In fact, assuming you're not using a v6 git-annex repository, it doesn't
really need to update that database at all. But since we'll be upgrading to
v6 eventually, I need to deal with problems like this. Also,
this same problem will also impact the database used for incremental fsck.
I can reproduce this with a v5 repository; dropping a file happens to run a
code path that updates the database. And reproducing it w/o using git-annex too:
joey@darkstar:~/tmp>mkdir empty
joey@darkstar:~/tmp>umask
0002
joey@darkstar:~/tmp>touch empty/file
joey@darkstar:~/tmp>sqlite3 empty/db
SQLite version 3.16.2 2017-01-06 16:32:41
Enter ".help" for usage hints.
sqlite> create table foo;
Error: near ";": syntax error
sqlite>
joey@darkstar:~/tmp>ls -l empty/
total 0
-rw-r--r-- 1 joey joey 0 Feb 13 16:33 db
-rw-rw-r-- 1 joey joey 0 Feb 13 16:32 file
Seems that sqlite uses `0644 & umask` for the db permissions,
which is *bad* because it doesn't allow the umask to enable the group
write bit. That 0644 is `SQLITE_DEFAULT_FILE_PERMISSIONS`, so it can
be changed to something saner at compile time.
`http://www.sqlite.org/src/doc/trunk/src/os_unix.c` has a useful comment.
Seems that sqlite is careful to make -wal, -journal, and -shm files
have the exact same permissions as main database file.
So, if `.git/annex/keys/*` is updated to have the desired permissions when
the database is created, every further write to the database will keep
using the desired permissions.
Hmm, it turns out that git-annex does already set the database permissions when
creating it, but only if core.sharedRepository is set to group or all. So
there's a workaround; just `git config core.sharedRepository group` when
setting up a repository that's going to be accessed by multiple users. Almost
certianly a better idea than relying on umask anyway; people mess up umask
settings.
I'll go ahead and make it always set sane permissions when creating databases.
I'm not going to try to fix up permissions in existing repositories though.
"""]]

49
doc/bugs/Add_custom-setup_stanza_to_.cabal_file.mdwn
View file

@ -1,49 +0,0 @@
### Please describe the problem.
git-annex uses a custom setup script but does not have a custom-setup stanza. This causes
git-annex to be unbuildable with `cabal new-build` and I'm told it's also unbuildable with
the old `cabal build` under certain circumstances.
### What steps will reproduce the problem?
Try building git-annex with `cabal new-build`.
### What version of git-annex are you using? On what operating system?
git-annex-6.20171214 on Debian GNU/Linux 9.
### 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
$ cabal new-build --constraint="any.git-annex -testsuite"
Resolving dependencies...
In order, the following will be built (use -v for more details):
- git-annex-6.20171214 (exe:git-annex) -testsuite -dbus -concurrentoutput (requires build)
- dummypkg-0 (lib) (first run)
Configuring git-annex-6.20171214 (all, legacy fallback)...
cabal: Failed to build git-annex-6.20171214 (which is required by dummypkg-0).
The failure occurred during the configure step. The exception was:
dieVerbatim: user error (cabal: '/usr/bin/ghc' exited with an error:
/home/matthew/dummypkg/dist-newstyle/tmp/src-3285/git-annex-6.20171214/Utility/FileSize.hs:10:1:
error:
Failed to load interface for ‘System.PosixCompat.Files’
It is a member of the hidden package ‘unix-compat-0.5.0.1’.
Perhaps you need to add ‘unix-compat’ to the build-depends in your .cabal
file.
Use -v to see a list of the files searched for.
)
# End of transcript or log.
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yeah, it's amazing! I've been using the version from the Debian repos and then
wanted to try building the new version for youtube-dl support.
> Revisited it and seem to have managed to add custom-setup back. [[done]]
> --[[Joey]]

9
doc/bugs/Add_custom-setup_stanza_to_.cabal_file/comment_1_88d5109a342e6a06d2f9f400cf850e3d._comment
View file

@ -1,9 +0,0 @@
[[!comment format=mdwn
username="mbekkema97@66b135681014f005a3a14c4011d148fcb6655f81"
nickname="mbekkema97"
avatar="http://cdn.libravatar.org/avatar/a5037b8a5914bd9f803af7b7e881d632"
subject="I just found out you're already aware of this"
date="2017-12-15T07:16:13Z"
content="""
https://github.com/haskell/cabal/issues/4852
"""]]

29
doc/bugs/Add_explicit_retries_for_curl__47__wget_on___34__transient__34___errors__63__.mdwn
View file

@ -1,29 +0,0 @@
### Please describe the problem.
While download content from dropbox (via regular urls associated with the files, so "web" remote), some fail some time with error code returned 500 (internal server failure without explicit reason), which causes git-annex get also to fail if that was the only source for the file to try.
### What steps will reproduce the problem?
This is all happening with http://datasets.datalad.org/workshops/nih-2017/ds000114/derivatives/freesurfer/ repository (on eg https://dl.dropboxusercontent.com/s/sn4et1e3d2run9g/rh.aparc.dktatlas.annot?dl=0 url ), but for testing wget/curl I just created http://www.onerussian.com/tmp/errors/500 which would always return 500.
### What version of git-annex are you using? On what operating system?
6.20180316+gitg308f3ecf6
### Please provide any additional information below.
here are options for wget and curl which could help us out here:
[[!format sh """
# to make wget retry
> wget --retry-on-http-error=500 http://www.onerussian.com/tmp/errors/500
# to make curl retry, just needs --retry 10 which then considers 5xx errors intermittent
> curl --retry 10 http://www.onerussian.com/tmp/errors/500
"""]]
Could git-annex add those options to curl/wget invocations for more robust access to the web remote?
> [[done]] --[[Joey]]

33
doc/bugs/Add_explicit_retries_for_curl__47__wget_on___34__transient__34___errors__63__/comment_1_9eafb42dce4c437a777cda0048756f42._comment
View file

@ -1,33 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-03-24T13:54:31Z"
content="""
Note that with --retry 10, curl will back off 10 times, with wait doubling,
so it could get stuck for 20+ minutes. That seems too long, but the right
number of retries seems to depend on how overloaded the http server is; you
may need a number that would otherwise be excessive in order to get a high
enough probability of success.
Also worth noting that http *has* status codes such as 503 that are
intended to be used when the client should wait and retry; 500 is not such
a code.
If this is done at the wget/curl level, it will also need to be done
when using the http-client library (which does not currently retry on any
code, AFAICs).
And, it could just as easily be a S3 or webdav server that is throwing the
http retry codes, and the libraries for those will have their own retrying
behavior. (And it could even be a ssh server ot other non-http protocol
that connections to fail intermittently.)
Putting all this together, I'm wondering if the http level is the right
place to put this retrying. It's not a matter of complying with the http
spec; it seems to need user configuration in order to handle their
particular use case.
git-annex already does generic retrying as long as some data was
received, to recover from broken connections. That could be extended to
support a config option that enables a number of retries.
"""]]

13
doc/bugs/Add_explicit_retries_for_curl__47__wget_on___34__transient__34___errors__63__/comment_2_23fe5ddd3a77c20d66c6847bdb83c94b._comment
View file

@ -1,13 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2018-03-29T17:24:35Z"
content="""
I've implemented `remote.<name>.annex-retry`, `annex.retry`,
`remote.<name>.annex-retry-delay`, `annex.retry-delay` configs, so you can
have full control over retry behavior for remotes.
Since these are fully generic, not at the HTTP level, they'll
make any and all transfer failures be retried, no matter why it failed.
Which could be a good thing or a bad thing..
"""]]

18
doc/bugs/Adding_metadata.mdwn
View file

@ -1,18 +0,0 @@
### Please describe the problem.
This is less of a bug and more of a feature(?) request. Currently, when assigning metadata to a datafile, git annex (v5.20150710-g8fd705) will produce no error or warning message if the file entered does not exist. This can be a tad confusing to users who might expect to see some output if they typed their path wrong. A successful `git annex metadata <filename> -s tags=best` will produce output acknowledging the change, but a failure produces no output at all. A quick check if the file exists, and a `File does not exist` error message if not, would be easy implement and helpful to new users.
### What steps will reproduce the problem?
git annex metadata <filename> -s tags+=atlas
Where <filename> does not exist.
### What version of git-annex are you using? On what operating system?
v5.20150710-g8fd705
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
We use git-annex for our open-source !FreeSurfer software and find very helpful indeed. Thank you. https://surfer.nmr.mgh.harvard.edu/
> [[fixed|done]] --[[Joey]]

57
doc/bugs/Adding_torrent_via_addurl_fails.mdwn
View file

@ -1,57 +0,0 @@
[[!meta title="addurl failure with non-standard torrent file"]]
### Please describe the problem.
Adding a magnet link via addurl fails after downloading the torrent metatdata if the "announce" field of the torrent is empty
### What steps will reproduce the problem?
git annex addurl "magnet:?xt=urn:btih:88066b90278f2de655ee2dd44e784c340b54e45c"
### What version of git-annex are you using? On what operating system?
git-annex version: 6.20160126
archlinux
### Please provide any additional information below.
I have traced back the Problem to the parsing of the torrent metatdata.
Since you also seem to be the author of the haskel-torrent parser I felt it is apropriate to post here.
The above magnet link (an Archlinux Iso) results in a .torrent file that has no "announce" entry. Instead it only has the entry "announce-list" with multiple urls.
This causes the parser to fail.
I dont know if having only "announce-list" horribly violates some standard, however a second magnet link that i tried showed the same behaviour so this might not be an unusual case.
I was able to put in a workarround in btshowmetainfo.py to set "annonuce" to the first entry from "announce-list" if it wasn't defined.
My git-annex binary is compiled with the haskel parser enabled do this doesn't change annexs' behaviour.
It's not a big dealbreaker for me, just playing arround with the torrent feaure for now.
[[!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 annex addurl "magnet:?xt=urn:btih:88066b90278f2de655ee2dd44e784c340b54e45c"
(downloading torrent file...)
02/07 16:42:13 [NOTICE] IPv4 DHT: listening on UDP port 6964
02/07 16:42:13 [NOTICE] IPv4 BitTorrent: listening on TCP port 6927
02/07 16:42:13 [NOTICE] IPv6 BitTorrent: listening on TCP port 6927
[#96c5b2 27KiB/27KiB(100%) CN:11 SD:2]
02/07 16:42:32 [NOTICE] Download complete: [METADATA]88066b90278f2de655ee2dd44e784c340b54e45c
02/07 16:42:32 [NOTICE] Saved metadata as ../../.git/annex/misctmp/URL--magnet&c,63xt,61urn&cbtih&c88066b90278f2de655ee2dd44e784c340b54e45c/meta/88066b90278f2de655ee2dd44e784c340b54e45c.torrent.
Download Results:
gid |stat|avg speed |path/URI
======+====+===========+=======================================================
96c5b2|OK | 0B/s|[MEMORY][METADATA]88066b90278f2de655ee2dd44e784c340b54e45c
Status Legend:
(OK):download completed.
git-annex: failed to parse torrent: Name not found in dictionary: announce
# End of transcript or log.
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
> This was fixed in haskell-torrent version 10000.1.0. [[done]]

18
doc/bugs/Adding_torrent_via_addurl_fails/comment_1_477913541446737692c2d3ae2cc197bb._comment
View file

@ -1,18 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2016-02-08T18:53:00Z"
content="""
announce-list comes from BEP-0012. Reading that spec, the torrent file is
supposed to still have the announce field, although its contents are
supposed to be ignored by clients that support announce-list.
When I download that torrent, it doesn't seem to have an
announce-list either. No announce and no announce-list? It's possible that
aria2c, which I used to download it like git-annex does, doesn't know about
announce-list and left it out when saving the torrent file. Maybe it left
out announce too? Do you have a non-magnet url for this torrent file?
I'll make the haskell torrent library support parsing announce-list once
<https://github.com/creichert/bencode/issues/12> is fixed.
"""]]

24
doc/bugs/Adding_torrent_via_addurl_fails/comment_2_e317aee1ff6e60aafcd106751af660c8._comment
View file

@ -1,24 +0,0 @@
[[!comment format=mdwn
username="annuges"
subject="comment 2"
date="2016-02-09T13:49:42Z"
content="""
sorry looks like i hadd a litle mixup, the full magnet link that i used when checking btshowmetainfo was
magnet:?xt=urn:btih:88066b90278f2de655ee2dd44e784c340b54e45c&dn=archlinux-2016.02.01-dual.iso&tr=udp://tracker.archlinux.org:6969&tr=http://tracker.archlinux.org:6969/announce
Using this one with aria2c --bt-save-metadata results in a torrent file with the announce-list entry only.
Modifying the link to only contain one tracker url still results in an announce-list with a single entry.
There also is a separate torrent file on the arch website that has the announce field set correctly.
https://www.archlinux.org/releng/releases/2016.02.01/torrent/
They hide the actuall .torrent file though so addurl doesn't trigger the torrent parsing with led me to try the magnet link to begin with.
Anyway, looks like aria2c is at fault because it doesn't generate standard compliant .torrent files from magnet links.
"""]]

9
doc/bugs/Adding_torrent_via_addurl_fails/comment_3_7ff48f1b6426f7bbf6f3aaa4e1526d19._comment
View file

@ -1,9 +0,0 @@
[[!comment format=mdwn
username="mbekkema97@66b135681014f005a3a14c4011d148fcb6655f81"
nickname="mbekkema97"
avatar="http://cdn.libravatar.org/avatar/a5037b8a5914bd9f803af7b7e881d632"
subject="comment 3"
date="2018-01-12T12:01:30Z"
content="""
This seems to be fixed now due to an update to Haskell's torrent library.
"""]]

297
doc/bugs/Android_4.4_install_fails_with_permission_denied_errors.mdwn
View file

@ -1,297 +0,0 @@
### Please describe the problem.
Installing git-annex on a new Nexus 5 with Android 4.4.4 using [Android 4.4 and 4.3 git-annex.apk](http://downloads.kitenet.net/git-annex/android/current/4.3/git-annex.apk) does not give me a working git-annex environment. It seems permission is denied to install many of the app files.
### What steps will reproduce the problem?
1. Install git-annex
2. From within `adb shell`, run: `/data/data/ga.androidterm/runshell`
3. Try one of the included programs, e.g., `git`
### What version of git-annex are you using? On what operating system?
The current (as of 2014-08-30) git-annex for Android 4.3 and up on Android 4.4.4.
### Please provide any additional information below.
Running `/data/data/ga.androidterm/runshell` from `adb shell` gives me:
[[!format txt """
shell@hammerhead:/ $ /data/data/ga.androidterm/runshell
Falling back to hardcoded app location; cannot find expected files in /data/app-lib
shell@hammerhead:/sdcard/git-annex.home $ ls
git-annex-install.log
shell@hammerhead:/sdcard/git-annex.home $ cat git-annex-install.log
Installation starting to /data/data/ga.androidterm
71c22504d777380dd59d2128b97715fde9ef6bec
mv: can't rename '/data/data/ga.androidterm/bin': Permission denied
installing busybox
ln: /data/data/ga.androidterm/bin/busybox: Permission denied
installing git-annex
ln: /data/data/ga.androidterm/bin/git-annex: Permission denied
installing git-shell
ln: /data/data/ga.androidterm/bin/git-shell: Permission denied
installing git-upload-pack
ln: /data/data/ga.androidterm/bin/git-upload-pack: Permission denied
installing git
ln: /data/data/ga.androidterm/bin/git: Permission denied
installing gpg
ln: /data/data/ga.androidterm/bin/gpg: Permission denied
installing rsync
ln: /data/data/ga.androidterm/bin/rsync: Permission denied
installing ssh
ln: /data/data/ga.androidterm/bin/ssh: Permission denied
installing ssh-keygen
ln: /data/data/ga.androidterm/bin/ssh-keygen: Permission denied
busybox: /data/data/ga.androidterm/bin/[: Permission denied
busybox: /data/data/ga.androidterm/bin/[[: Permission denied
busybox: /data/data/ga.androidterm/bin/ar: Permission denied
busybox: /data/data/ga.androidterm/bin/arp: Permission denied
busybox: /data/data/ga.androidterm/bin/ash: Permission denied
busybox: /data/data/ga.androidterm/bin/base64: Permission denied
busybox: /data/data/ga.androidterm/bin/basename: Permission denied
busybox: /data/data/ga.androidterm/bin/beep: Permission denied
busybox: /data/data/ga.androidterm/bin/blkid: Permission denied
busybox: /data/data/ga.androidterm/bin/blockdev: Permission denied
busybox: /data/data/ga.androidterm/bin/bunzip2: Permission denied
busybox: /data/data/ga.androidterm/bin/bzcat: Permission denied
busybox: /data/data/ga.androidterm/bin/bzip2: Permission denied
busybox: /data/data/ga.androidterm/bin/cal: Permission denied
busybox: /data/data/ga.androidterm/bin/cat: Permission denied
busybox: /data/data/ga.androidterm/bin/catv: Permission denied
busybox: /data/data/ga.androidterm/bin/chat: Permission denied
busybox: /data/data/ga.androidterm/bin/chattr: Permission denied
busybox: /data/data/ga.androidterm/bin/chgrp: Permission denied
busybox: /data/data/ga.androidterm/bin/chmod: Permission denied
busybox: /data/data/ga.androidterm/bin/chown: Permission denied
busybox: /data/data/ga.androidterm/bin/chpst: Permission denied
busybox: /data/data/ga.androidterm/bin/chroot: Permission denied
busybox: /data/data/ga.androidterm/bin/chrt: Permission denied
busybox: /data/data/ga.androidterm/bin/chvt: Permission denied
busybox: /data/data/ga.androidterm/bin/cksum: Permission denied
busybox: /data/data/ga.androidterm/bin/clear: Permission denied
busybox: /data/data/ga.androidterm/bin/cmp: Permission denied
busybox: /data/data/ga.androidterm/bin/comm: Permission denied
busybox: /data/data/ga.androidterm/bin/cp: Permission denied
busybox: /data/data/ga.androidterm/bin/cpio: Permission denied
busybox: /data/data/ga.androidterm/bin/cttyhack: Permission denied
busybox: /data/data/ga.androidterm/bin/cut: Permission denied
busybox: /data/data/ga.androidterm/bin/dc: Permission denied
busybox: /data/data/ga.androidterm/bin/dd: Permission denied
busybox: /data/data/ga.androidterm/bin/deallocvt: Permission denied
busybox: /data/data/ga.androidterm/bin/devmem: Permission denied
busybox: /data/data/ga.androidterm/bin/diff: Permission denied
busybox: /data/data/ga.androidterm/bin/dirname: Permission denied
busybox: /data/data/ga.androidterm/bin/dmesg: Permission denied
busybox: /data/data/ga.androidterm/bin/dnsd: Permission denied
busybox: /data/data/ga.androidterm/bin/dos2unix: Permission denied
busybox: /data/data/ga.androidterm/bin/dpkg: Permission denied
busybox: /data/data/ga.androidterm/bin/dpkg-deb: Permission denied
busybox: /data/data/ga.androidterm/bin/du: Permission denied
busybox: /data/data/ga.androidterm/bin/dumpkmap: Permission denied
busybox: /data/data/ga.androidterm/bin/echo: Permission denied
busybox: /data/data/ga.androidterm/bin/envdir: Permission denied
busybox: /data/data/ga.androidterm/bin/envuidgid: Permission denied
busybox: /data/data/ga.androidterm/bin/expand: Permission denied
busybox: /data/data/ga.androidterm/bin/fakeidentd: Permission denied
busybox: /data/data/ga.androidterm/bin/false: Permission denied
busybox: /data/data/ga.androidterm/bin/fbset: Permission denied
busybox: /data/data/ga.androidterm/bin/fbsplash: Permission denied
busybox: /data/data/ga.androidterm/bin/fdflush: Permission denied
busybox: /data/data/ga.androidterm/bin/fdformat: Permission denied
busybox: /data/data/ga.androidterm/bin/fdisk: Permission denied
busybox: /data/data/ga.androidterm/bin/fgconsole: Permission denied
busybox: /data/data/ga.androidterm/bin/find: Permission denied
busybox: /data/data/ga.androidterm/bin/findfs: Permission denied
busybox: /data/data/ga.androidterm/bin/flash_lock: Permission denied
busybox: /data/data/ga.androidterm/bin/flash_unlock: Permission denied
busybox: /data/data/ga.androidterm/bin/flashcp: Permission denied
busybox: /data/data/ga.androidterm/bin/flock: Permission denied
busybox: /data/data/ga.androidterm/bin/fold: Permission denied
busybox: /data/data/ga.androidterm/bin/freeramdisk: Permission denied
busybox: /data/data/ga.androidterm/bin/ftpd: Permission denied
busybox: /data/data/ga.androidterm/bin/ftpget: Permission denied
busybox: /data/data/ga.androidterm/bin/ftpput: Permission denied
busybox: /data/data/ga.androidterm/bin/fuser: Permission denied
busybox: /data/data/ga.androidterm/bin/getopt: Permission denied
busybox: /data/data/ga.androidterm/bin/grep: Permission denied
busybox: /data/data/ga.androidterm/bin/gunzip: Permission denied
busybox: /data/data/ga.androidterm/bin/gzip: Permission denied
busybox: /data/data/ga.androidterm/bin/hd: Permission denied
busybox: /data/data/ga.androidterm/bin/hdparm: Permission denied
busybox: /data/data/ga.androidterm/bin/head: Permission denied
busybox: /data/data/ga.androidterm/bin/hexdump: Permission denied
busybox: /data/data/ga.androidterm/bin/httpd: Permission denied
busybox: /data/data/ga.androidterm/bin/ifconfig: Permission denied
busybox: /data/data/ga.androidterm/bin/ifdown: Permission denied
busybox: /data/data/ga.androidterm/bin/ifup: Permission denied
busybox: /data/data/ga.androidterm/bin/inotifyd: Permission denied
busybox: /data/data/ga.androidterm/bin/install: Permission denied
busybox: /data/data/ga.androidterm/bin/iostat: Permission denied
busybox: /data/data/ga.androidterm/bin/ip: Permission denied
busybox: /data/data/ga.androidterm/bin/ipaddr: Permission denied
busybox: /data/data/ga.androidterm/bin/ipcalc: Permission denied
busybox: /data/data/ga.androidterm/bin/iplink: Permission denied
busybox: /data/data/ga.androidterm/bin/iproute: Permission denied
busybox: /data/data/ga.androidterm/bin/iprule: Permission denied
busybox: /data/data/ga.androidterm/bin/iptunnel: Permission denied
busybox: /data/data/ga.androidterm/bin/klogd: Permission denied
busybox: /data/data/ga.androidterm/bin/ln: Permission denied
busybox: /data/data/ga.androidterm/bin/loadkmap: Permission denied
busybox: /data/data/ga.androidterm/bin/losetup: Permission denied
busybox: /data/data/ga.androidterm/bin/lpd: Permission denied
busybox: /data/data/ga.androidterm/bin/lpq: Permission denied
busybox: /data/data/ga.androidterm/bin/lpr: Permission denied
busybox: /data/data/ga.androidterm/bin/ls: Permission denied
busybox: /data/data/ga.androidterm/bin/lsattr: Permission denied
busybox: /data/data/ga.androidterm/bin/lsof: Permission denied
busybox: /data/data/ga.androidterm/bin/lspci: Permission denied
busybox: /data/data/ga.androidterm/bin/lsusb: Permission denied
busybox: /data/data/ga.androidterm/bin/lzcat: Permission denied
busybox: /data/data/ga.androidterm/bin/lzma: Permission denied
busybox: /data/data/ga.androidterm/bin/lzop: Permission denied
busybox: /data/data/ga.androidterm/bin/lzopcat: Permission denied
busybox: /data/data/ga.androidterm/bin/makedevs: Permission denied
busybox: /data/data/ga.androidterm/bin/makemime: Permission denied
busybox: /data/data/ga.androidterm/bin/man: Permission denied
busybox: /data/data/ga.androidterm/bin/md5sum: Permission denied
busybox: /data/data/ga.androidterm/bin/mkdir: Permission denied
busybox: /data/data/ga.androidterm/bin/mkfifo: Permission denied
busybox: /data/data/ga.androidterm/bin/mknod: Permission denied
busybox: /data/data/ga.androidterm/bin/mkswap: Permission denied
busybox: /data/data/ga.androidterm/bin/mktemp: Permission denied
busybox: /data/data/ga.androidterm/bin/more: Permission denied
busybox: /data/data/ga.androidterm/bin/mpstat: Permission denied
busybox: /data/data/ga.androidterm/bin/mv: Permission denied
busybox: /data/data/ga.androidterm/bin/nbd-client: Permission denied
busybox: /data/data/ga.androidterm/bin/nc: Permission denied
busybox: /data/data/ga.androidterm/bin/netstat: Permission denied
busybox: /data/data/ga.androidterm/bin/nice: Permission denied
busybox: /data/data/ga.androidterm/bin/nmeter: Permission denied
busybox: /data/data/ga.androidterm/bin/nohup: Permission denied
busybox: /data/data/ga.androidterm/bin/od: Permission denied
busybox: /data/data/ga.androidterm/bin/openvt: Permission denied
busybox: /data/data/ga.androidterm/bin/patch: Permission denied
busybox: /data/data/ga.androidterm/bin/pidof: Permission denied
busybox: /data/data/ga.androidterm/bin/pipe_progress: Permission denied
busybox: /data/data/ga.androidterm/bin/pmap: Permission denied
busybox: /data/data/ga.androidterm/bin/popmaildir: Permission denied
busybox: /data/data/ga.androidterm/bin/printenv: Permission denied
busybox: /data/data/ga.androidterm/bin/printf: Permission denied
busybox: /data/data/ga.androidterm/bin/pscan: Permission denied
busybox: /data/data/ga.androidterm/bin/pstree: Permission denied
busybox: /data/data/ga.androidterm/bin/pwd: Permission denied
busybox: /data/data/ga.androidterm/bin/pwdx: Permission denied
busybox: /data/data/ga.androidterm/bin/raidautorun: Permission denied
busybox: /data/data/ga.androidterm/bin/rdev: Permission denied
busybox: /data/data/ga.androidterm/bin/readlink: Permission denied
busybox: /data/data/ga.androidterm/bin/readprofile: Permission denied
busybox: /data/data/ga.androidterm/bin/realpath: Permission denied
busybox: /data/data/ga.androidterm/bin/reformime: Permission denied
busybox: /data/data/ga.androidterm/bin/renice: Permission denied
busybox: /data/data/ga.androidterm/bin/reset: Permission denied
busybox: /data/data/ga.androidterm/bin/resize: Permission denied
busybox: /data/data/ga.androidterm/bin/rev: Permission denied
busybox: /data/data/ga.androidterm/bin/rm: Permission denied
busybox: /data/data/ga.androidterm/bin/rmdir: Permission denied
busybox: /data/data/ga.androidterm/bin/route: Permission denied
busybox: /data/data/ga.androidterm/bin/rpm: Permission denied
busybox: /data/data/ga.androidterm/bin/rpm2cpio: Permission denied
busybox: /data/data/ga.androidterm/bin/rtcwake: Permission denied
busybox: /data/data/ga.androidterm/bin/run-parts: Permission denied
busybox: /data/data/ga.androidterm/bin/runsv: Permission denied
busybox: /data/data/ga.androidterm/bin/runsvdir: Permission denied
busybox: /data/data/ga.androidterm/bin/rx: Permission denied
busybox: /data/data/ga.androidterm/bin/script: Permission denied
busybox: /data/data/ga.androidterm/bin/scriptreplay: Permission denied
busybox: /data/data/ga.androidterm/bin/sed: Permission denied
busybox: /data/data/ga.androidterm/bin/sendmail: Permission denied
busybox: /data/data/ga.androidterm/bin/seq: Permission denied
busybox: /data/data/ga.androidterm/bin/setconsole: Permission denied
busybox: /data/data/ga.androidterm/bin/setkeycodes: Permission denied
busybox: /data/data/ga.androidterm/bin/setlogcons: Permission denied
busybox: /data/data/ga.androidterm/bin/setserial: Permission denied
busybox: /data/data/ga.androidterm/bin/setsid: Permission denied
busybox: /data/data/ga.androidterm/bin/setuidgid: Permission denied
busybox: /data/data/ga.androidterm/bin/sh: Permission denied
busybox: /data/data/ga.androidterm/bin/sha1sum: Permission denied
busybox: /data/data/ga.androidterm/bin/sha256sum: Permission denied
busybox: /data/data/ga.androidterm/bin/sha512sum: Permission denied
busybox: /data/data/ga.androidterm/bin/showkey: Permission denied
busybox: /data/data/ga.androidterm/bin/sleep: Permission denied
busybox: /data/data/ga.androidterm/bin/smemcap: Permission denied
busybox: /data/data/ga.androidterm/bin/softlimit: Permission denied
busybox: /data/data/ga.androidterm/bin/sort: Permission denied
busybox: /data/data/ga.androidterm/bin/split: Permission denied
busybox: /data/data/ga.androidterm/bin/start-stop-daemon: Permission denied
busybox: /data/data/ga.androidterm/bin/strings: Permission denied
busybox: /data/data/ga.androidterm/bin/stty: Permission denied
busybox: /data/data/ga.androidterm/bin/sum: Permission denied
busybox: /data/data/ga.androidterm/bin/sv: Permission denied
busybox: /data/data/ga.androidterm/bin/svlogd: Permission denied
busybox: /data/data/ga.androidterm/bin/sync: Permission denied
busybox: /data/data/ga.androidterm/bin/sysctl: Permission denied
busybox: /data/data/ga.androidterm/bin/tac: Permission denied
busybox: /data/data/ga.androidterm/bin/tail: Permission denied
busybox: /data/data/ga.androidterm/bin/tar: Permission denied
busybox: /data/data/ga.androidterm/bin/tcpsvd: Permission denied
busybox: /data/data/ga.androidterm/bin/tee: Permission denied
busybox: /data/data/ga.androidterm/bin/test: Permission denied
busybox: /data/data/ga.androidterm/bin/time: Permission denied
busybox: /data/data/ga.androidterm/bin/timeout: Permission denied
busybox: /data/data/ga.androidterm/bin/top: Permission denied
busybox: /data/data/ga.androidterm/bin/touch: Permission denied
busybox: /data/data/ga.androidterm/bin/tr: Permission denied
busybox: /data/data/ga.androidterm/bin/true: Permission denied
busybox: /data/data/ga.androidterm/bin/ttysize: Permission denied
busybox: /data/data/ga.androidterm/bin/tunctl: Permission denied
busybox: /data/data/ga.androidterm/bin/tune2fs: Permission denied
busybox: /data/data/ga.androidterm/bin/udhcpc: Permission denied
busybox: /data/data/ga.androidterm/bin/uname: Permission denied
busybox: /data/data/ga.androidterm/bin/uncompress: Permission denied
busybox: /data/data/ga.androidterm/bin/unexpand: Permission denied
busybox: /data/data/ga.androidterm/bin/uniq: Permission denied
busybox: /data/data/ga.androidterm/bin/unix2dos: Permission denied
busybox: /data/data/ga.androidterm/bin/unlzma: Permission denied
busybox: /data/data/ga.androidterm/bin/unlzop: Permission denied
busybox: /data/data/ga.androidterm/bin/unxz: Permission denied
busybox: /data/data/ga.androidterm/bin/unzip: Permission denied
busybox: /data/data/ga.androidterm/bin/uudecode: Permission denied
busybox: /data/data/ga.androidterm/bin/uuencode: Permission denied
busybox: /data/data/ga.androidterm/bin/vi: Permission denied
busybox: /data/data/ga.androidterm/bin/volname: Permission denied
busybox: /data/data/ga.androidterm/bin/watch: Permission denied
busybox: /data/data/ga.androidterm/bin/wc: Permission denied
busybox: /data/data/ga.androidterm/bin/wget: Permission denied
busybox: /data/data/ga.androidterm/bin/which: Permission denied
busybox: /data/data/ga.androidterm/bin/whoami: Permission denied
busybox: /data/data/ga.androidterm/bin/whois: Permission denied
busybox: /data/data/ga.androidterm/bin/xargs: Permission denied
busybox: /data/data/ga.androidterm/bin/xz: Permission denied
busybox: /data/data/ga.androidterm/bin/xzcat: Permission denied
busybox: /data/data/ga.androidterm/bin/yes: Permission denied
busybox: /data/data/ga.androidterm/bin/zcat: Permission denied
tar: can't remove old file ./links/git-shell: Permission denied
cat: can't open '/data/data/ga.androidterm/links/git': Permission denied
rm: can't stat '/data/data/ga.androidterm/links/git': Permission denied
cat: can't open '/data/data/ga.androidterm/links/git-shell': Permission denied
rm: can't stat '/data/data/ga.androidterm/links/git-shell': Permission denied
cat: can't open '/data/data/ga.androidterm/links/git-upload-pack': Permission denied
rm: can't stat '/data/data/ga.androidterm/links/git-upload-pack': Permission denied
lib/lib.runshell.so: line 133: can't create /data/data/ga.androidterm/runshell: Permission denied
lib/lib.runshell.so: line 133: can't create /data/data/ga.androidterm/runshell: Permission denied
chmod: runshell: Operation not permitted
lib/lib.runshell.so: line 133: can't create /data/data/ga.androidterm/bin/trustedkeys.gpg: Permission denied
lib/lib.runshell.so: line 133: can't create /data/data/ga.androidterm/installed-version: Permission denied
Installation complete
tar: write: Broken pipe
shell@hammerhead:/sdcard/git-annex.home $ ^D
shell@hammerhead:/ $
"""]]
Android is new to me, so it's possible I'm doing something utterly wrong.
> Closing as this was a bug in the deprecated Android app. [[done]] --[[Joey]]

15
doc/bugs/Android_4.4_install_fails_with_permission_denied_errors/comment_1_9b0ed646552e56b6b199761b3ff9eb85._comment
View file

@ -1,15 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-05-08T18:55:27Z"
content="""
I'm closing this bug report because the git-annex Android app that it
was reported on is now deprecated. Instead, we have
a way to run the regular git-annex build for linux on Android in termux:
<https://git-annex.branchable.com/tips/install_on_Android_in_Termux/>
There were a lot of problems with the way the git-annex Android app was
put together, and I hope this new approach avoids them. If you try it and
still have the bug you reported, please followup and I'll reopen it.
"""]]

35
doc/bugs/Android_6.0_compatibility.mdwn
View file

@ -1,35 +0,0 @@
### Please describe the problem.
Git-annex appears to be incompatible with Android 6. I downloaded the APK for Android 5 and tried installing it on a Nexus 5X running Android 6.0.1. The biggest issue is that pushing and pulling to SSH remotes fails with a "Permission denied" error from muxserver_listen() in OpenSSH. There are some other warnings and errors, listed below, would you like me to file separate bugs for each or track everything here?
- The full error from ssh is "muxserver_listen: link mux listener /data/data/ga.androidterm/tmp/ssh/annex-user@192.168.0.3.Jg42jDbmIRBdbjDZ => /data/data/ga.androidterm/tmp/ssh/annex-user@192.168.0.3: Permission denied". Immediately after that there is an error message, presumably from git, that reads "fatal: Could not read from remote repository." I am able to SSH to the server from the app's command line, and get an interactive shell. I can successfully run 'git fetch `git remote`', but `git annex sync` runs into this issue.
- When switching between two repositories in the webapp, the page never loads after clicking on a repository. After trying the link a few times, I can see "git-annex: Daemon is already running." through the webapp's log viewer. However, if I stop the daemon through the webapp and start it again, then the webapp will indicate that I successfully switched to the other repository.
- There is a warning message in the console that reads, "WARNING: linker: git-annex has text relocations. This is wasting memory and prevents security hardening. Please fix." It appears that apps targeting SDK version 23 are not allowed to use text relocations, while apps targeting lower versions just get this warning. See http://developer.android.com/about/versions/marshmallow/android-6.0-changes.html#behavior-runtime
- There is a warning message at the top of every new terminal that says "Falling back to hardcoded app location; cannot find expected files in /data/app/ga.androidterm-1/lib". This issue doesn't appear to affect anything, but I thought I'd mention it for completeness.
- At various times during syncing, "\_\_bionic_open_tzdata_path: ANDROID_DATA not set!" and "\_\_bionic_open_tzdata_path: ANDROID_ROOT not set!" show up in the log.
### What steps will reproduce the problem?
1. Install Android 5.0 APK on Android 6.0 phone
2. Create a repository
3. Add an SSH remote
### What version of git-annex are you using? On what operating system?
5.20151217-g7b73f34 on Android 6.0.1
### Please provide any additional information below.
[[!format sh """
muxserver_listen: link mux listener /data/data/ga.androidterm/tmp/ssh/annex-user@192.168.0.3.ZUzI2MBl8k0qt2pg => /data/data/ga.androidterm/tmp/ssh/annex-user@192.168.0.3: Permission denied
"""]]
If I look in this temporary directory after the fact, I see the following.
[[!format sh """
> ls -l /data/data/ga.androidterm/tmp/ssh
-rw------- 1 u0_a108 u0_a108 0 Dec 24 10:06 annex-user@192.168.0.3.lock
"""]]
I suppose since the socket is a Unix domain socket, it gets destroyed when the process stops, so it shouldn't be surprising there's nothing else in that directory.
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Not yet, but I'm excited to make it work!
> Closing as this was a bug in the deprecated Android app. [[done]] --[[Joey]]

8
doc/bugs/Android_6.0_compatibility/comment_1_06dcb3d7c5de5a831403e8e6c4c98dfd._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="divergentdave@5c17d06f6d67c6f157b76a4cc95ca764b7d2f899"
nickname="divergentdave"
subject="comment 1"
date="2015-12-24T22:44:16Z"
content="""
FWIW, it appears that SSH caching is already turned off in this repository. If I cd to the repository and run `git config annex.sshcaching` I get back \"false\".
"""]]

12
doc/bugs/Android_6.0_compatibility/comment_2_c7cabab122174867d7350a1eaa76151c._comment
View file

@ -1,12 +0,0 @@
[[!comment format=mdwn
username="divergentdave@5c17d06f6d67c6f157b76a4cc95ca764b7d2f899"
nickname="divergentdave"
subject="Logcat output -- SELinux"
date="2015-12-30T03:01:56Z"
content="""
I ran a sync again and captured output from logcat. It appears that an SELinux policy is preventing ssh from linking its socket file. (at [this line](https://github.com/openssh/openssh-portable/blob/master/mux.c#L1298)) There are several log messages similar to the one below, presumably one for each failed invocation of ssh.
```
12-29 20:49:07.308 29990 29990 W ssh : type=1400 audit(0.0:64711): avc: denied { link } for name=\"annex-user@192.168.0.3.cAGquyBx4Z10RTYL\" dev=\"dm-2\" ino=392849 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=sock_file permissive=0
```
"""]]

8
doc/bugs/Android_6.0_compatibility/comment_3_47f9cbde0385a4816ccec1b512dea2fd._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="divergentdave@5c17d06f6d67c6f157b76a4cc95ca764b7d2f899"
nickname="divergentdave"
subject="SELinux"
date="2015-12-30T03:40:02Z"
content="""
According to [this issue on Google Code](https://code.google.com/p/android-developer-preview/issues/detail?id=3150), hard linking files is not allowed on Android 6.0. It looks like the only recourse will be to reconfigure or patch OpenSSH, such that it doesn't need to create a hardlink.
"""]]

12
doc/bugs/Android_6.0_compatibility/comment_4_f1f3c98050247cbba4521311465513e2._comment
View file

@ -1,12 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 4"""
date="2016-01-20T19:03:37Z"
content="""
Unfortunately, I lack time, energy, or devices to do much work on the
Android port. Patches would be welcome for any or all of these issues.
(Although the relocations warning seems completely ignorable.)
(Wow, they broke hard links? What core unix feature is next to go? Sheesh.)
"""]]

29
doc/bugs/Android_6.0_compatibility/comment_5_0bcee221dd22b424f08720604a486c79._comment
View file

@ -1,29 +0,0 @@
[[!comment format=mdwn
username="divergentdave@5c17d06f6d67c6f157b76a4cc95ca764b7d2f899"
nickname="divergentdave"
subject="Disabling SSH connection caching"
date="2016-02-01T06:52:55Z"
content="""
I was looking into how SSH connection caching is handled, and it seems there's a bug in the sshCacheDir function in Annex/Ssh.hs. If I'm reading things right, `annex.sshcaching` is ignored when `annex.crippledfilesystem` is set. Thus, even though the configuration says SSH caching is disabled, this function still creates and passes out a temporary directory to be used for connection caching. Further up, this results in ControlPersist, ControlMaster, etc. being passed to OpenSSH, which runs into the SELinux rules. I think the `ifM` calls should be nested the other way around, (see below) which would allow me to turn off connection caching and hopefully get SSH working. I haven't tested this yet, though I plan to get a build environment set up within a month for further tinkering.
Revised sshCacheDir:
```
sshCacheDir :: Annex (Maybe FilePath)
sshCacheDir
| SysConfig.sshconnectioncaching = ifM
( fromMaybe True . annexSshCaching <$> Annex.getGitConfig )
( ifM crippledFileSystem
( maybe (return Nothing) usetmpdir =<< gettmpdir
, Just <$> fromRepo gitAnnexSshDir )
, return Nothing
)
| otherwise = return Nothing
where
gettmpdir = liftIO $ getEnv \"GIT_ANNEX_TMP_DIR\"
usetmpdir tmpdir = liftIO $ catchMaybeIO $ do
let socktmp = tmpdir </> \"ssh\"
createDirectoryIfMissing True socktmp
return socktmp
```
"""]]

10
doc/bugs/Android_6.0_compatibility/comment_6_a4ef9eb27285aa68d6edc14e30627ebf._comment
View file

@ -1,10 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 6"""
date="2016-04-20T18:40:57Z"
content="""
Thanks, divergentdave for spotting that and also for writing a fix.
I've finally noticed your comment and put the fix in. It would probably be
good to open a todo if you have a patch in the future, to make sure it
doesn't get forgotten about.
"""]]

15
doc/bugs/Android_6.0_compatibility/comment_7_a7110f92e8a90e95f494e3f917b610ea._comment
View file

@ -1,15 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 7"""
date="2018-05-08T18:51:44Z"
content="""
I'm closing this bug report because the git-annex Android app that it
was reported on is now deprecated. Instead, we have
a way to run the regular git-annex build for linux on Android in termux:
<https://git-annex.branchable.com/tips/install_on_Android_in_Termux/>
There were a lot of problems with the way the git-annex Android app was
put together, and I hope this new approach avoids them. If you try it and
still have the bug you reported, please followup and I'll reopen it.
"""]]

41
doc/bugs/Android_CM_5.1_ANDROID__95__ROOT_not_set.mdwn
View file

@ -1,41 +0,0 @@
### Please describe the problem.
Downloaded git-annex (version for android 5.0) from the website. Upon opening the app for the first time and setting up a repository at /sdcard/annex, the terminal gave out the error.
### What version of git-annex are you using? On what operating system?
Nexus 4 running Cyanogenmod 12.1 (Android 5.1) build 20151007 and 20150901
### Please provide any additional information below.
Output to the terminal window:
[[!format sh """
WARNING: linker: git-annex has text relocations. This is wating memory and prevents security hardening. Please fix.
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
Detected a filesystem without fifo support.
Disabling ssh connection caching.
Detected a crippled filesystem.
Enabling direct mode.
fatal: ../../../../sdcard/annex: '../../../../sdcard/annex' is outside of repository
(recording state in git...)
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
__bionic_open_tzdata_path: ANDROID_ROOT not set!
"""]]
I can add remote repositories and they show up nicely in the webapp, but no files are ever downloaded.
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
I have a couple of repositories atm, one with my music, another that backs up our family pictures for the family and uses Amazon S3 as a backup.
> Closing as this was a bug in the deprecated Android app. [[done]] --[[Joey]]

14
doc/bugs/Android_CM_5.1_ANDROID__95__ROOT_not_set/comment_1_5f480528fe855fcbdbf5b6950aa42a25._comment
View file

@ -1,14 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-05-08T18:52:02Z"
content="""
I'm closing this bug report because the git-annex Android app that it
was reported on is now deprecated. Instead, we have
a way to run the regular git-annex build for linux on Android in termux:
<https://git-annex.branchable.com/tips/install_on_Android_in_Termux/>
There were a lot of problems with the way the git-annex Android app was
put together, and I hope this new approach avoids them. If you try it and
still have the bug you reported, please followup and I'll reopen it.
"""]]

64
doc/bugs/Android__58___Cannot_create_repo_on_external_sd_card.mdwn
View file

@ -1,64 +0,0 @@
I am using the latest daily build for Android 5.0
My version is Android 5.0.1 Lollipop. And I'm using a Samsung Galaxy S4 unrooted.
Trying to create a repositpory in the folder /storage/extSdCard/Music gives me a webpage with a red error badge that says:
"Internal Server Error"
git init failed
Output:
/storage/extSdCard/Music/.git: Permission denied
I'm pretty sure this is because of Android's crappy permission system on sd cards. But when I install the app, it tells me it is asking for
read write access to the sd card. So this consideration must have happened.
### Please describe the problem.
I am using the latest daily build for Android 5.0
My version is Android 5.0.1 Lollipop. And I'm using a Samsung Galaxy S4 unrooted.
Trying to create a repositpory in the folder /storage/extSdCard/Music gives me a webpage with a red error badge that says:
"Internal Server Error"
git init failed
Output:
/storage/extSdCard/Music/.git: Permission denied
I'm pretty sure this is because of Android's crappy permission system on sd cards. But when I install the app, it tells me it is asking for
read write access to the sd card. So this consideration must have happened.
### What steps will reproduce the problem?
1. Install the Android 5.0 daily build on an Android 5.0.1 phone.
2. Try to create a repo on an external sd card.
### What version of git-annex are you using? On what operating system?
Latest daily build of Android 5.0 git annex on Android 5.0.1
### Please provide any additional information below.
When I run adb shell I see the following permissions on the file in question:
drwxrwx--- root sdcard_r 2016-04-02 14:11 Music
Additional info. The terminal emulator shows this output:
Falling back to hardcoded app location: cannot find expected files in /data/app/ga.androidterm-2/lib
git annex webapp
WARNING: linker: git-annex has text relocations. This is wasting memory and prevents security hardening. Please fix.
I have tried moving the app to the sd card, but it will not work if I do that.
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes! It's by far one of my favorite apps! it works very well on my laptop, on my home file server, and on my internal storage on my Android phone :)
> Closing as this was a bug in the deprecated Android app. [[done]] --[[Joey]]

14
doc/bugs/Android__58___Cannot_create_repo_on_external_sd_card/comment_1_7ac9adea8bf562d590133e83cbb12570._comment
View file

@ -1,14 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-05-08T18:49:14Z"
content="""
I'm closing this bug report because the git-annex Android app that it
was reported on is now deprecated. Instead, we have
a way to run the regular git-annex build for linux on Android in termux:
<https://git-annex.branchable.com/tips/install_on_Android_in_Termux/>
There were a lot of problems with the way the git-annex Android app was
put together, and I hope this new approach avoids them. If you try it and
still have the bug you reported, please followup and I'll reopen it.
"""]]

8
doc/bugs/Android__58___use___47__data__47____8230___for_git-annex.home__63__.mdwn
View file

@ -1,8 +0,0 @@
### Please describe the problem.
I’ve only just set up git-annex on my Android system, so I might be confused; but from what I could find on this site, the Android build only supports passwordless SSH key files, which must be deployed in /sdcard/git-annex.home/.ssh (I also found something about git-annex generating keys by itself, but the web app didn’t refer to something like that, so I take it this feature is gone now). What perplexed me about this is that /sdcard on Android is a VFAT file-system, and is set up so that any user or application may read it (with a permissions mask for the sdcard group), which isn’t ideal for a passwordless key. From what I could gather, there’s also a place in the virtual file-system under /data that is intended to house private, per-application data. Should git-annex use this location as its home instead?
### What version of git-annex are you using? On what operating system?
git-annex 5.20150522-g260b59e
Android 4.4.4
> Closing as this was a bug in the deprecated Android app. [[done]] --[[Joey]]

8
doc/bugs/Android__58___use___47__data__47____8230___for_git-annex.home__63__/comment_1_95481b150f43fd3db311fbcf6d1e48aa._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2015-07-06T18:23:57Z"
content="""
I think that /data is locked down such that apps generally cannot write to
it, but please correct me if I'm wrong.
"""]]

8
doc/bugs/Android__58___use___47__data__47____8230___for_git-annex.home__63__/comment_2_041fe2a545b48acd2c9d15eb2ac2b34f._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="divergentdave@5c17d06f6d67c6f157b76a4cc95ca764b7d2f899"
nickname="divergentdave"
subject="comment 2"
date="2016-03-21T04:13:15Z"
content="""
Each app has one subfolder inside /data that is private to that app (and user) alone. Generally, you can't read or enumerate /data itself. There is a function in the Java API to get the current app's internal storage folder, see https://developer.android.com/reference/android/content/Context.html#getFilesDir%28%29.
"""]]

14
doc/bugs/Android__58___use___47__data__47____8230___for_git-annex.home__63__/comment_3_c46091ade13865addb83c6e77f97f195._comment
View file

@ -1,14 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2018-05-08T18:50:00Z"
content="""
I'm closing this bug report because the git-annex Android app that it
was reported on is now deprecated. Instead, we have
a way to run the regular git-annex build for linux on Android in termux:
<https://git-annex.branchable.com/tips/install_on_Android_in_Termux/>
There were a lot of problems with the way the git-annex Android app was
put together, and I hope this new approach avoids them. If you try it and
still have the bug you reported, please followup and I'll reopen it.
"""]]

42
doc/bugs/Android_cannot_setup_gitlab_repo_due_to_ECDSA_key.mdwn
View file

@ -1,42 +0,0 @@
### Please describe the problem.
Cannot add gitlab repository on Android.
### What steps will reproduce the problem?
After attempting to add a gitlab repository on git-annex assistant, I am presented with a ssh key and prompted to add it to my gitlab account. After doing so and continuing, git-annex assistant returns to the same page and presents the ssh key again. Attempting to continue repeats the cycle as the ssh key is presented over and over.
### What version of git-annex are you using? On what operating system?
Stable version for Lollipop (I experienced this same error on Kit Kat ~6 months ago but could not resolve it at that point)
Android 5.0 git-annex.apk
### Please provide any additional information below.
In the git-annex assistant log I see:
No ECDSA host key is known for gitlab.com and you have requested strict checking.
Host key verification failed.
No ECDSA host key is known for gitlab.com and you have requested strict checking.
Host key verification failed.
fatal: Could not read from remote repository
Please make sure you have the correct access rights and the repository exists.
Host key verification failed.
Host key verification failed.
fatal: Could not read from remote repository.
I resolved the issue by opening a new terminal window, attempting to connect to gitlab (ssh git@gitlab.com), verifying the ECDSA key against the gitlab website (https://about.gitlab.com/gitlab-com/) and accepting the key. The file .ssh/known_hosts was created. The gitlab repository could then be added in git annex assistant.
The lack of information about the error presented to the user in git annex assistant was part of the problem.
[[!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.
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
> Closing as this was a bug in the deprecated Android app. [[done]] --[[Joey]]

14
doc/bugs/Android_cannot_setup_gitlab_repo_due_to_ECDSA_key/comment_1_d46469579e96df51ad045340f974f268._comment
View file

@ -1,14 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-05-08T18:50:33Z"
content="""
I'm closing this bug report because the git-annex Android app that it
was reported on is now deprecated. Instead, we have
a way to run the regular git-annex build for linux on Android in termux:
<https://git-annex.branchable.com/tips/install_on_Android_in_Termux/>
There were a lot of problems with the way the git-annex Android app was
put together, and I hope this new approach avoids them. If you try it and
still have the bug you reported, please followup and I'll reopen it.
"""]]

35
doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH.mdwn
View file

@ -1,35 +0,0 @@
### Please describe the problem.
The install script [[install/Android/git-annex-install]] only adds an entry to `$PATH` which lasts for as long as the shell used for the install. Subsequent launches of termux will not find `git-annex` on the `$PATH`.
I'm puzzled why this hasn't been reported before. Is everyone on Android manually running `./git-annex.linux/git-annex ...` each time, or have they manually set up `$PATH` in their Termux shell profile without reporting back to the community, or am I missing something else?
### What steps will reproduce the problem?
- Install `git-annex` on Android as per [[Android]]
- Quit the shell used during install
- Relaunch termux
- Try to run `git-annex`
### What version of git-annex are you using? On what operating system?
6.20180927-gc5b6c55af on Android P
I know this is probably old now but I can't see any evidence the installer fixed this issue since I last tried. Happy to be told I'm wrong.
### Please provide any additional information below.
[[!format sh """
% git annex
git: 'annex' is not a git command. See 'git --help'.
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes, been using it for many years and couldn't live without it.
[[!meta title="termux install adds git-annex only to bash path, not zsh etc"]]
> made it detect when the login shell is not bash, and rather than add to
> .profile, print out a message letting the user know what they need to
> add to their shell's path [[done]]

9
doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_1_7aad5d44591f456f2dfcbe5e2351b8bf._comment
View file

@ -1,9 +0,0 @@
[[!comment format=mdwn
username="anthony@ad39673d230d75cbfd19d2757d754030049c7673"
nickname="anthony"
avatar="http://cdn.libravatar.org/avatar/05b48b72766177b3b0a6ff4afdb70790"
subject="Should be in ~/.profile"
date="2019-05-14T19:15:07Z"
content="""
At least here (on two Android devices I've used the installer on), the installer sets up ~/.profile to add git-annex to PATH.
"""]]

16
doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_2_ca7a2b0d05a925e530b637b209f1af34._comment
View file

@ -1,16 +0,0 @@
[[!comment format=mdwn
username="branchable@bafd175a4b99afd6ed72501042e364ebd3e0c45e"
nickname="branchable"
avatar="http://cdn.libravatar.org/avatar/ae41dba34ee6000056f00793c695be75"
subject="Are we talking about a different installer?"
date="2019-05-14T19:57:41Z"
content="""
This is the one I used: <http://git-annex.branchable.com/install/Android/git-annex-install>
The comment near the top even explicitly admits that it doesn't permanently set up `$PATH`:
```
# This script needs to be sourced into the current termux shell, rather
# than run with a new shell, so it can set the PATH to include git-annex.
```
"""]]

16
doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_3_9949507f9222667645df6cb5b8aaaf44._comment
View file

@ -1,16 +0,0 @@
[[!comment format=mdwn
username="anthony@ad39673d230d75cbfd19d2757d754030049c7673"
nickname="anthony"
avatar="http://cdn.libravatar.org/avatar/05b48b72766177b3b0a6ff4afdb70790"
subject="comment 3"
date="2019-05-15T17:55:58Z"
content="""
Yep, that's the same installer. After running it on my phone, I have a `~/.profile`:
```
$ cat .profile
PATH=$PATH:/data/data/com.termux/files/home/git-annex.linux
```
The code that adds it is in `~/git-annex.linux/runshell` (which is a shell script). That'd be a good place to start debugging if your `~/.profile` doesn't have the path line.
"""]]

9
doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_4_d8cec7fae740e82c5da1da47037e2da6._comment
View file

@ -1,9 +0,0 @@
[[!comment format=mdwn
username="branchable@bafd175a4b99afd6ed72501042e364ebd3e0c45e"
nickname="branchable"
avatar="http://cdn.libravatar.org/avatar/ae41dba34ee6000056f00793c695be75"
subject=".profile doesn't take effect"
date="2019-05-18T19:46:09Z"
content="""
Ah, interesting. Very odd that the install script doesn't do that directly. I do have the same contents in my `~/.profile`, but Termux happily ignores it, so `$PATH` is unaltered. Does it really work for you? What version of Termux do you have?
"""]]

9
doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_5_3eafb2258ac0c8c4e18a3f4591728b32._comment
View file

@ -1,9 +0,0 @@
[[!comment format=mdwn
username="anthony@2b89f08c5c67f83d920fe464d7363db8f45cec20"
nickname="anthony"
avatar="http://cdn.libravatar.org/avatar/5d9fb1b0dd5ae1428c4c5b7df8d26bf2"
subject="comment 5"
date="2019-05-19T08:39:09Z"
content="""
I have the latest from the Play store on one device and the latest from F-Droid on the other. Is it possible you have a bash_profile or bash_login? If so, then I believe bash won't read profile.
"""]]

9
doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_6_dd74b3b5a15b6b9f21f3835da134cd5a._comment
View file

@ -1,9 +0,0 @@
[[!comment format=mdwn
username="branchable@bafd175a4b99afd6ed72501042e364ebd3e0c45e"
nickname="branchable"
avatar="http://cdn.libravatar.org/avatar/ae41dba34ee6000056f00793c695be75"
subject="it's zsh"
date="2019-05-19T10:05:27Z"
content="""
I figured it out - I changed my default shell to `zsh`, which doesn't read `.profile`. IMHO the installation should also set up `.zprofile` in the same way.
"""]]

12
doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_7_f9b09f1a720ab73f6a089e8c65f7c402._comment
View file

@ -1,12 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 7"""
date="2019-05-20T13:52:37Z"
content="""
There are a lot of shells, and AFAIK no single place an environment
variable can be put that works with all of them.
I'm inclined to say that working with termux's default shell is all this
needs to do, and if the user installs some other shell, it's up to them to
configure it.
"""]]

11
doc/bugs/Android_install_doesn__39__t_permanently_add_to___36__PATH/comment_8_c15caba920b49cebf88ebd36caa053b7._comment
View file

@ -1,11 +0,0 @@
[[!comment format=mdwn
username="branchable@bafd175a4b99afd6ed72501042e364ebd3e0c45e"
nickname="branchable"
avatar="http://cdn.libravatar.org/avatar/ae41dba34ee6000056f00793c695be75"
subject="comment 8"
date="2019-05-20T15:23:45Z"
content="""
I understand, and of course it's your prerogative to take that position. While there are many UNIX shells out there, I'm pretty sure that bash and zsh are the two which combined take the lion share of the market.
If you're worried about the impact of adding `cp .profile .zprofile` to the install, a reasonable alternative would be to document that the install relies on setting up `$PATH` via `.profile` - this confusion only arose in the first place because that mechanism is somewhat hidden rather than taking place directly in the install script.
"""]]

92
doc/bugs/Android_installation_is_missing___36__PATH_setup.mdwn
View file

@ -1,92 +0,0 @@
### Please describe the problem.
After following the (new) Android installation instructions, git-annex is not on `$PATH`, therefore literal `git annex` commands fail.
I'm sure this is trivially fixed by enhancing the install script so that it modifies `$PATH` in the termux profile, or similar.
### What steps will reproduce the problem?
1. Follow the instructions at https://git-annex.branchable.com/Android/ up to `sh git-annex-install`
2. Observe that the install succeeds
3. Try the next step: `git annex webapp`
4. Observe the error `git: 'annex' is not a git command. See 'git --help'.`
5. Observe that it works when using `./git-annex.linux/git-annex` instead
### What version of git-annex are you using? On what operating system?
6.20180927-gc5b6c55af on Android 8.1.0 (OxygenOS 5.1.5) on a OnePlus 5T (A5010).
### 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
% sh -x git-annex-install [20/4719]
+ set -e
+ uname -m
+ arch=arm64
+ url=https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-arm64.tar.gz
+ echo Installing dependencies with termux pkg manager...
Installing dependencies with termux pkg manager...
+ pkg install git wget tar coreutils proot
Hit:1 https://termux.net stable InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
19 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Building dependency tree
Reading state information... Done
coreutils is already the newest version (8.30-1).
git is already the newest version (2.19.1).
proot is already the newest version (5.1.107-18).
tar is already the newest version (1.30-1).
wget is already the newest version (1.19.5-1).
0 upgraded, 0 newly installed, 0 to remove and 19 not upgraded.
+ echo Downloading git-annex...
Downloading git-annex...
+ cd
+ wget -O- https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-arm64.tar.gz
+ tar zx
--2018-10-21 23:41:37-- https://downloads.kitenet.net/git-annex/linux/current/git-annex-standalone-arm64.tar.gz
Resolving downloads.kitenet.net... 66.228.36.95, 2600:3c03::f03c:91ff:fe73:b0d2
Connecting to downloads.kitenet.net|66.228.36.95|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 64590742 (62M) [application/x-gzip]
Saving to: ‘STDOUT’
- 100%[==================================================================>] 61.60M 2.51MB/s in 81s
2018-10-21 23:42:59 (778 KB/s) - written to stdout [64590742/64590742]
+ git-annex.linux/git-annex version
Running on Android.. Adding git-annex to PATH for you, and tuning for optimal behavior.
git-annex version: 6.20180927-gc5b6c55af
build flags: Assistant Webapp Pairing S3(multipartupload)(storageclasses) WebDAV Inotify DBus DesktopNotify ConcurrentOutput TorrentParser Mag$
cMime Feeds Testsuite
dependency versions: aws-0.19 bloomfilter-2.0.1.0 cryptonite-0.25 DAV-1.3.2 feed-1.0.0.0 ghc-8.2.2 http-client-0.5.12 persistent-sqlite-2.8.1.$
torrent-10000.1.1 uuid-1.3.13 yesod-1.6.0
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_$
84E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 BLAKE2B256E BLAKE2B256 BLAKE2B512E BLAKE2B512 BLAKE2B160E BLAKE2B160 BLAKE2B224E BLAKE2B224
BLAKE2B384E BLAKE2B384 BLAKE2S256E BLAKE2S256 BLAKE2S160E BLAKE2S160 BLAKE2S224E BLAKE2S224 BLAKE2SP256E BLAKE2SP256 BLAKE2SP224E BLAKE2SP224 $
HA1E SHA1 MD5E MD5 WORM URL
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav adb tahoe glacier ddar hook external
operating system: linux aarch64
supported repository versions: 3 5 6
upgrade supported from repository versions: 0 1 2 3 4 5
+ echo git-annex is successfully installed.
git-annex is successfully installed.
+ echo Now running termux-setup-storage, to let git-annex access system storage.
Now running termux-setup-storage, to let git-annex access system storage.
+ termux-setup-storage
+ echo Installation complete.
Installation complete.
% git annex webapp
git: 'annex' is not a git command. See 'git --help'.
# End of transcript or log.
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes, lots of luck over the years :-) This is the final little tweak required to get it working for me on Android.
> [[fixed|done]] --[[Joey]]

17
doc/bugs/Android_installation_is_missing___36__PATH_setup/comment_1_cf0e167e2da279a20c5b71f9962d05a0._comment
View file

@ -1,17 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-10-22T17:04:18Z"
content="""
Running on Android.. Adding git-annex to PATH for you, and tuning for optimal behavior.
That means it should have updated ~/.profile to set PATH appropriate.
The problem is the new git-annex-install script, when it exits, dumps the
user back into the shell they were in before, and that shell has not gotten
its path updated. And without sourcing the download script into the current
shell, it has no way to update the path.
I suppose the best thing is to ask the user to source the script, and then
the script can set PATH. Which I've now done.
""]]

53
doc/bugs/Assumes_OpenSSH_version_newer_than_debian_stable.mdwn
View file

@ -1,53 +0,0 @@
### Please describe the problem.
Git-annex is hanging for me on all operations if I have a customized OpenSSH host as a remote.
This is because git-annex uses a custom config file that uses directives introduced in OpenSSH 7.3p1 . I have OpenSSH 6.7p1 .
### What steps will reproduce the problem?
On Debian Jessie, specify a custom host in ~/.ssh/config such as
Host custom-host
HostName realhost.com
Add it as a remote and try to use git-annex
$ git remote add custom user@custom-host
$ git annex vicfg --debug
It just hangs.
### What version of git-annex are you using? On what operating system?
git-annex version: 6.20161211-gc3ab3c668
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
### 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
annex@host:~/annex$ git annex vicfg --debug
[2017-01-16 12:01:58.104071891] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","git-annex"]
[2017-01-16 12:01:58.110698965] process done ExitSuccess
[2017-01-16 12:01:58.11093666] read: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"]
[2017-01-16 12:01:58.116640973] process done ExitSuccess
[2017-01-16 12:01:58.123254411] chat: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","cat-file","--batch"]
[2017-01-16 12:01:58.125003224] chat: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","cat-file","--batch-check=%(objectname) %(objecttype) %(objectsize)"]
[2017-01-16 12:01:58.131239655] read: ssh ["-S",".git/annex/ssh/annex@annex-whonix-standalone","-o","ControlMaster=auto","-o","ControlPersist=yes","-F",".git/annex/ssh.config","-T","annex@annex-whonix-standalone","git-annex-shell 'configlist' '/~/annex' '--debug'"]
^C
annex@host:~/annex$ cat .git/annex/ssh.config
IgnoreUnknown Include
Include ~/.ssh/config
Include /etc/ssh/ssh_config
ServerAliveInterval 60
# End of transcript or log.
"""]]
The problem is the use of the `Include` directive which is not understood by my release of OpenSSH.
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Git-annex rocks !!!!
> [[done]]; this was already fixed --[[Joey]]

8
doc/bugs/Assumes_OpenSSH_version_newer_than_debian_stable/comment_1_5a1f9a2014501072188fb235f1b03726._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="xloem"
avatar="http://cdn.libravatar.org/avatar/b8c087f7c5e6a9358748f0727c077f3b"
subject="comment 1"
date="2017-01-16T12:47:03Z"
content="""
Fixed by upgrading to newer version ! Sorry for the re-bug.
"""]]

8
doc/bugs/Assumes_OpenSSH_version_newer_than_debian_stable/comment_2_0bc9c0e6d72d6b0d9173e55eca8b107a._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="xloem"
avatar="http://cdn.libravatar.org/avatar/b8c087f7c5e6a9358748f0727c077f3b"
subject="comment 2"
date="2017-01-16T12:48:36Z"
content="""
how do I move the bug to done?
"""]]

54
doc/bugs/Bash_completion_of_filenames_with_spaces.mdwn
View file

@ -1,54 +0,0 @@
### Please describe the problem.
When using tab-completion for git-annex subcommands, filenames with spaces (or other special characters) are not correctly handled.
### What steps will reproduce the problem?
[[!format sh """
$ touch 'foo bar.baz'
$ git annex 'foo<tab> # completes to 'foo bar.baz', as expected
$ git annex add 'foo<tab> # presents the following (incorrect) options
bar.baz foo
"""]]
### What version of git-annex are you using? On what operating system?
[[!format sh """
$ git annex version
git-annex version: 6.20180719
build flags: Assistant Webapp Pairing S3(multipartupload)(storageclasses) WebDAV Inotify ConcurrentOutput Feeds Testsuite
dependency versions: aws-0.20 bloomfilter-2.0.1.0 cryptonite-0.25 DAV-1.3.2 feed-1.0.0.0 ghc-8.4.3 http-client-0.5.13.1 persistent-sqlite-2.8.1.2 uuid-1.3.13 yesod-1.6.0
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384
SKEIN256E SKEIN256 SKEIN512E SKEIN512 BLAKE2B256E BLAKE2B256 BLAKE2B512E BLAKE2B512 BLAKE2B160E BLAKE2B160 BLAKE2B224E BLAKE2B224 BLAKE2B384E BLAKE2B384
BLAKE2S256E BLAKE2S256 BLAKE2S160E BLAKE2S160 BLAKE2S224E BLAKE2S224 BLAKE2SP256E BLAKE2SP256 BLAKE2SP224E BLAKE2SP224 SHA1E SHA1 MD5E MD5 WORM URL
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav adb tahoe glacier ddar hook external
operating system: linux x86_64
supported repository versions: 3 5 6
upgrade supported from repository versions: 0 1 2 3 4 5
"""]]
### Please provide any additional information below.
This is a one-line patch that *somewhat* fixes the issue:
[[!format sh """
--- a/bash-completion.bash
+++ b/bash-completion.bash
@@ -20,6 +20,7 @@ complete -o bashdefault -o default -o filenames -F _git-annex git-annex
_git_annex() {
local cmdline
CMDLINE=(--bash-completion-index $(($COMP_CWORD - 1)))
+ local IFS=$'\n'
local seen_g`
"""]]
I've certainly not tested this thoroughly, but the problem demonstrated above is fixed, and a cursory check of other commands seems to behave as expected.
However, it doesn't correctly handle escape characters. Typically, a filename completion escapes special characters as needed, taking into account quoting rules if necessary. This one line patch doesn't seem to do that and completes to names with raw spaces.
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Many times over! I use git-annex to manage my hundreds of pdfs, images, video files etc! It essentially enables *exactly* the work flow I like, since I live in the command line and appreciate fine-grained control over my tools. So, yes, thank you very much for this excellent too!
> [[fixed|done]] --[[Joey]]

28
doc/bugs/Bash_completion_of_filenames_with_spaces/comment_1_03146fdf32b16c9f3398c5a9c3ab32f6._comment
View file

@ -1,28 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-11-12T16:13:26Z"
content="""
I see this too. Note that it only affects tab
completing "git annex"; tab completing "git-annex"
works correctly for filenames with spaces and AFAICS
other problem characters.
It used to be that git-annex's tab completion for "git annex" was only used
after the user tab completed "git-annex" which loaded the function.
That has changed; git now loads the git-annex completion. Which is good;
I asked the git devs a long time ago to add that. But the change means this
problem is more visible. I don't think the problem is new though.
[[!commit 07c108e70e2df354d1478cbbec3630d2409d9d32]]
dealt with the same problem affecting "git-annex" tab completion.
The underlying problem is a bug in optparse-applicative, which
completes filenames without escaping them.
So that commit made the "git-annex" completion use "-o bashdefault -o default"
which bypasses the optparse-applicative completion for filenames and lets
bash handle them. It didn't seem to deal with "git annex" completion.
I see that git uses `__gitcomp_file_direct` when using eg `git ls-files`
to list filenames. It seems that "compopt -o filenames" along with
IFS=newline fixes it. I'll put the same approach into the git-annex script.
"""]]

41
doc/bugs/Build_failure__58___Utility__47__QuickCheck.hs__58__38__58__10__58___error__58___Duplicate_instance_declarations.mdwn
View file

@ -1,41 +0,0 @@
### Please describe the problem.
git-annex-6.20170520 no longer builds successfully. My last successful build of git-annex-6.20170520 was Jun 12, 2017, but something has probably changed in at least one of the dependencies on Hackage since then.
The build fails on all three Homebrew CI nodes (macOS 10.10, 10.11, and 10.12).
A full log is here: <https://jenkins.brew.sh/job/Homebrew%20Core%20Pull%20Requests/3175/version=sierra/consoleText>
Duplicate since that will eventually be deleted: <https://gist.github.com/ilovezfs/e93d135243d03567444eb10be8902a95>
### What steps will reproduce the problem?
Attempt to build git-annex in a cabal sandbox using cabal install.
### What version of git-annex are you using? On what operating system?
git-annex-6.20170520
### Please provide any additional information below.
The build error is
[[!format sh """
[ 8 of 559] Compiling Utility.QuickCheck ( Utility/QuickCheck.hs, dist/dist-sandbox-758c2984/build/git-annex/git-annex-tmp/Utility/QuickCheck.o )
Utility/QuickCheck.hs:38:10: error:
Duplicate instance declarations:
instance Arbitrary EpochTime
-- Defined at Utility/QuickCheck.hs:38:10
instance [safe] Arbitrary Foreign.C.Types.CTime
-- Defined in ‘Test.QuickCheck.Arbitrary’
cabal: Leaving directory '.'
cabal: Error: some packages failed to install:
git-annex-6.20170520 failed during the building phase. The exception was:
ExitFailure 1
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes, thanks!
> Fixed in [[!commit 75cecbbe3fdafdb6652e95ac17cd755c28e67f20]] [[done]]
> --[[Joey]]

181
doc/bugs/Build_failure_with_feed___62____61___1.0.0.0.mdwn
View file

@ -1,181 +0,0 @@
### Please describe the problem.
git-annex cannot build with feed 1.0.0.0, which was uploaded to Hackage on Sat Aug 26 23:56:18 UTC 2017 by AdamBergmark.
### What steps will reproduce the problem?
Try to build git-annex with cabal install in a cabal sandbox.
### What version of git-annex are you using? On what operating system?
6.20170818
### Please provide any additional information below.
[[!format sh """
[416 of 562] Compiling Command.ImportFeed ( Command/ImportFeed.hs, dist/dist-sandbox-b4eb11e/build/git-annex/git-annex-tmp/Command/ImportFeed.o )
Command/ImportFeed.hs:139:61: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: URLString
Actual type: Text.Atom.Feed.URI
• In the first argument of ‘Enclosure’, namely ‘enclosureurl’
In the second argument of ‘($)’, namely ‘Enclosure enclosureurl’
In the second argument of ‘($)’, namely
‘ToDownload f u i $ Enclosure enclosureurl’
Command/ImportFeed.hs:142:49: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: URLString
Actual type: Data.Text.Internal.Text
• In the first argument of ‘quviSupported’, namely ‘link’
In the first argument of ‘ifM’, namely ‘(quviSupported link)’
In the expression:
ifM
(quviSupported link)
(return $ Just $ ToDownload f u i $ QuviLink link, return Nothing)
Command/ImportFeed.hs:143:71: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: URLString
Actual type: Data.Text.Internal.Text
• In the first argument of ‘QuviLink’, namely ‘link’
In the second argument of ‘($)’, namely ‘QuviLink link’
In the second argument of ‘($)’, namely
‘ToDownload f u i $ QuviLink link’
Command/ImportFeed.hs:214:54: error:
• Couldn't match type ‘[Char]’ with ‘Data.Text.Internal.Text’
Expected type: S.Set Data.Text.Internal.Text
Actual type: S.Set ItemId
• In the second argument of ‘S.member’, namely ‘(knownitems cache)’
In the expression: S.member itemid (knownitems cache)
In a case alternative:
Just (_, itemid) -> S.member itemid (knownitems cache)
Command/ImportFeed.hs:279:42: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe [Char]
Actual type: Maybe Text.RSS.Syntax.DateString
• In the second argument of ‘(<$>)’, namely
‘getItemPublishDateString itm’
In the expression: replace "/" "-" <$> getItemPublishDateString itm
In a case alternative:
_ -> replace "/" "-" <$> getItemPublishDateString itm
Command/ImportFeed.hs:293:44: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: String
Actual type: Data.Text.Internal.Text
• In the first argument of ‘toMetaValue’, namely ‘itemid’
In the second argument of ‘($)’, namely ‘toMetaValue itemid’
In the second argument of ‘M.singleton’, namely
‘(S.singleton $ toMetaValue itemid)’
Command/ImportFeed.hs:299:26: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: feedtitle
In the expression: [feedtitle]
In the expression: ("feedtitle", [feedtitle])
Command/ImportFeed.hs:300:26: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: itemtitle
In the expression: [itemtitle]
In the expression: ("itemtitle", [itemtitle])
Command/ImportFeed.hs:301:27: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: feedauthor
In the expression: [feedauthor]
In the expression: ("feedauthor", [feedauthor])
Command/ImportFeed.hs:302:27: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: itemauthor
In the expression: [itemauthor]
In the expression: ("itemauthor", [itemauthor])
Command/ImportFeed.hs:303:28: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: getItemSummary $ item i
In the expression: [getItemSummary $ item i]
In the expression: ("itemsummary", [getItemSummary $ item i])
Command/ImportFeed.hs:304:32: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: getItemDescription $ item i
In the expression: [getItemDescription $ item i]
In the expression:
("itemdescription", [getItemDescription $ item i])
Command/ImportFeed.hs:305:27: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: getItemRights $ item i
In the expression: [getItemRights $ item i]
In the expression: ("itemrights", [getItemRights $ item i])
Command/ImportFeed.hs:306:23: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: snd <$> getItemId (item i)
In the expression: [snd <$> getItemId (item i)]
In the expression: ("itemid", [snd <$> getItemId (item i)])
Command/ImportFeed.hs:307:22: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: itemtitle
In the expression: [itemtitle, feedtitle]
In the expression: ("title", [itemtitle, feedtitle])
Command/ImportFeed.hs:307:33: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: feedtitle
In the expression: [itemtitle, feedtitle]
In the expression: ("title", [itemtitle, feedtitle])
Command/ImportFeed.hs:308:23: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: itemauthor
In the expression: [itemauthor, feedauthor]
In the expression: ("author", [itemauthor, feedauthor])
Command/ImportFeed.hs:308:35: error:
• Couldn't match type ‘Data.Text.Internal.Text’ with ‘[Char]’
Expected type: Maybe String
Actual type: Maybe Data.Text.Internal.Text
• In the expression: feedauthor
In the expression: [itemauthor, feedauthor]
In the expression: ("author", [itemauthor, feedauthor])
cabal: Leaving directory '.'
cabal: Error: some packages failed to install:
git-annex-6.20170818-ATXJn9dQzZj9avYQidLOBq failed during the building phase.
The exception was:
ExitFailure 1
"""]]
Full build log is here:
https://gist.githubusercontent.com/anonymous/dcc8d9823bd50b7fca10d5cf8961e75d/raw/c6500526bbad0a94e067816b1af2c9e8717a3419/08.cabal
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes!
> I fixed this last week, in [[!commit ee2f096e3ba3aea24445ff2093b426b68e000cc2]]. [[done]]

61
doc/bugs/CFBundleShortVersionString_is_not_incremented_with_git-annex.dmg_releases___40__downloads.kitenet.net__41__.mdwn
View file

@ -1,61 +0,0 @@
### Please describe the problem.
*Current:*
In the **git-annex.app** application bundle included on each [git-annex.dmg](https://downloads.kitenet.net/git-annex/OSX/current/10.11_El_Capitan/git-annex.dmg) the `CFBundleShortVersionString` and `CFBundleVersion` in the `/Content/PkgInfo.plist` are fixed at "0.0.1" over consecutive releases of `git-annex`.
<key>CFBundleShortVersionString</key>
<string>0.0.1</string>
...
<key>CFBundleVersion</key>
<string>0.0.1</string>
This is problematic for automated package deployment systems, such as [Munki](https://www.munki.org), which compare the `CFBundleShortVersionString` of an installed application on a given system with that of deployable packages in an administrator maintained repository to determine whether newer software will be deployed. As the `CFBundleShortVersionString` of `git-annex.app` is never incremented, the test always fails, and newer software is never deployed.
This is also potentially confusing for end-users whose systems invariably report `/Application/git-annex.app` as being at version "0.0.1" in the Finder and elsewhere in the system.
Compare to Firefox version 67.0.3:
<key>CFBundleShortVersionString</key>
<string>67.0.3</string>
...
<key>CFBundleVersion</key>
<string>6719.6.19</string>
Cf: [Apple Technical Note TN2420 Version Numbers and Build Numbers](https://developer.apple.com/library/archive/technotes/tn2420/_index.html)
*Expected:*
The `CFBundleShortVersionString` in the `git-annex.app/Content/PkgInfo.plist` matches the `distributionVersion` in [git-annex.app.info](https://downloads.kitenet.net/git-annex/OSX/current/10.11_El_Capitan/git-annex.dmg.info) for each release.
E.g.: The release of [version 7.20190507](http://git-annex.branchable.com/news/version_7.20190507/) where `git-annex.app/Contents/MacOS/git-annex version` reports
`git-annex version: 7.20190130-gfe9bfa815` and _downloads.kitenet.net_ hosts a `git-annex.dmg.info` containing`distributionVersion = 7.20190507`, the corresponding `git-annex.dmg`'s `/Content/PkgInfo.plist` would contain:
...
<key>CFBundleShortVersionString</key>
<string>7.20190507</string>
...
### What steps will reproduce the problem?
### What version of git-annex are you using? On what operating system?
### 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.
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes, loving git-annex, it's a great tool!
> [[fixed|done]] in the build scripts, when the OSX app will successfully
> build again I am not sure. Thanks for reporting this, I had no idea there
> was a significant version in there. --[[Joey]]

9
doc/bugs/CFBundleShortVersionString_is_not_incremented_with_git-annex.dmg_releases___40__downloads.kitenet.net__41__/comment_1_a97699ec3b18b9601a891d399a0f36e4._comment
View file

@ -1,9 +0,0 @@
[[!comment format=mdwn
username="leej"
avatar="http://cdn.libravatar.org/avatar/eb1c6bd57680f694fb4658388e6de4ed"
subject="Thank you, CFBundleShortVersionString is present and matches the internal git-annex version"
date="2019-08-02T15:57:10Z"
content="""
I can confirm that this works just fine with Munki tools version 3.6.2.3776.
Thank you again, Joey
"""]]

111
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant.mdwn
View file

@ -1,111 +0,0 @@
### Please describe the problem.
No matter what I do I can't
### What steps will reproduce the problem?
Create a repository, try to add a remote. An external disk in this case.
### What version of git-annex are you using? On what operating system?
Fedora 27
$ cat /etc/fedora-release
Fedora release 27 (Twenty Seven)
$ uname -a
Linux greger 4.14.14-300.fc27.x86_64 #1 SMP Fri Jan 19 13:19:54 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
$ git annex version
git-annex version: 6.20180130-g39d97867a
build flags: Assistant Webapp Pairing S3(multipartupload)(storageclasses) WebDAV Inotify DBus DesktopNotify ConcurrentOutput TorrentParser Feeds Testsuite
dependency versions: aws-0.17.1 bloomfilter-2.0.1.0 cryptonite-0.23 DAV-1.3.1 feed-0.3.12.0 ghc-8.0.2 http-client-0.5.7.0 persistent-sqlite-2.6.2 torrent-10000.1.1 uuid-1.3.13 yesod-1.4.5
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 SHA1E SHA1 MD5E MD5 WORM URL
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external
local repository version: 5
supported repository versions: 3 5 6
upgrade supported from repository versions: 0 1 2 3 4 5
operating system: linux x86_64
### Please provide any additional information below.
Debug log:
[2018-01-31 14:46:15.670775214] main: starting assistant version 6.20180130-g39d97867a
[2018-01-31 14:46:15.776042349] Cronner: You should enable consistency checking to protect your data.
(scanning...) [2018-01-31 14:46:15.988042623] Watcher: Performing startup scan
(started...)
[2018-01-31 14:47:48.236476657] read: gpg ["--quiet","--trust-model","always","--with-colons","--list-secret-keys","--fixed-list-mode"]
[2018-01-31 14:47:48.262055169] process done ExitSuccess
[2018-01-31 14:47:51.695935824] read: git ["init","--quiet","--bare","/run/media/dxtr/archive/annex"]
[2018-01-31 14:47:51.700278024] process done ExitSuccess
[2018-01-31 14:47:51.700424216] read: git ["config","--null","--list"]
[2018-01-31 14:47:51.707427206] process done ExitSuccess
[2018-01-31 14:47:51.70868726] call: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","config","core.fsyncobjectfiles","true"]
[2018-01-31 14:47:51.725766269] process done ExitSuccess
[2018-01-31 14:47:51.728215647] read: git ["config","--null","--list"]
[2018-01-31 14:47:51.740757992] process done ExitSuccess
[2018-01-31 14:47:51.741434499] read: git ["config","--null","--list"]
[2018-01-31 14:47:51.753548799] process done ExitSuccess
[2018-01-31 14:47:51.755149461] read: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","show-ref","git-annex"]
[2018-01-31 14:47:51.771911199] process done ExitFailure 1
[2018-01-31 14:47:51.772860937] read: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"]
[2018-01-31 14:47:51.789876829] process done ExitFailure 1
[2018-01-31 14:47:51.790600261] call: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","show-ref","--verify","-q","origin/git-annex"]
[2018-01-31 14:47:51.79719711] process done ExitFailure 1
[2018-01-31 14:47:51.799141741] read: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","write-tree"]
[2018-01-31 14:47:51.807820543] process done ExitSuccess
[2018-01-31 14:47:51.809126461] chat: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","commit-tree","4b825dc642cb6eb9a060e54bf8d69288fbee4904","--no-gpg-sign"]
[2018-01-31 14:47:51.836742843] process done ExitSuccess
[2018-01-31 14:47:51.837688371] call: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","update-ref","refs/heads/git-annex","c1bd62a595ce9cb811ad353ed0d9eaf8cfcb0b30"]
[2018-01-31 14:47:51.849598566] process done ExitSuccess
[2018-01-31 14:47:51.850762057] call: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","config","annex.uuid","da4c4bf3-5b3d-47f7-98d6-040cf8094360"]
[2018-01-31 14:47:51.855957091] process done ExitSuccess
[2018-01-31 14:47:51.85617243] read: git ["config","--null","--list"]
[2018-01-31 14:47:51.858450427] process done ExitSuccess
[2018-01-31 14:47:51.860771677] read: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","show-ref","git-annex"]
[2018-01-31 14:47:51.879636685] process done ExitSuccess
[2018-01-31 14:47:51.880463945] read: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"]
[2018-01-31 14:47:51.897305118] process done ExitSuccess
[2018-01-31 14:47:51.899214969] read: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","log","refs/heads/git-annex..c1bd62a595ce9cb811ad353ed0d9eaf8cfcb0b30","--pretty=%H","-n1"]
[2018-01-31 14:47:51.9105804] process done ExitSuccess
[2018-01-31 14:47:51.912107527] chat: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","cat-file","--batch"]
[2018-01-31 14:47:51.916244492] chat: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","cat-file","--batch-check=%(objectname) %(objecttype) %(objectsize)"]
[2018-01-31 14:47:51.926062822] call: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","config","annex.version","5"]
[2018-01-31 14:47:51.943412825] process done ExitSuccess
[2018-01-31 14:47:51.943804264] read: git ["config","--null","--list"]
[2018-01-31 14:47:51.949022318] process done ExitSuccess
[2018-01-31 14:47:51.952482534] chat: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","hash-object","-w","--stdin-paths","--no-filters"]
[2018-01-31 14:47:51.954175781] feed: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","update-index","-z","--index-info"]
[2018-01-31 14:47:51.968113275] process done ExitSuccess
[2018-01-31 14:47:51.969050491] read: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","show-ref","--hash","refs/heads/git-annex"]
[2018-01-31 14:47:51.979633335] process done ExitSuccess
(recording state in git...)
[2018-01-31 14:47:51.980277288] read: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","write-tree"]
[2018-01-31 14:47:51.989727059] process done ExitSuccess
[2018-01-31 14:47:51.98998106] chat: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","commit-tree","06548fa56acf18f9c1d74a29e248c4650df15e7e","--no-gpg-sign","-p","refs/heads/git-annex"]
[2018-01-31 14:47:52.011569157] process done ExitSuccess
[2018-01-31 14:47:52.012198525] call: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","update-ref","refs/heads/git-annex","26bcec3f33162a9c1c5b7a39c4828eedfdeae41b"]
[2018-01-31 14:47:52.030929599] process done ExitSuccess
[2018-01-31 14:47:52.037715315] process done ExitSuccess
[2018-01-31 14:47:52.038491764] process done ExitSuccess
[2018-01-31 14:47:52.039098682] process done ExitSuccess
[2018-01-31 14:47:52.039790346] read: uname ["-n"]
[2018-01-31 14:47:52.043271433] process done ExitSuccess
[2018-01-31 14:47:52.043523608] read: git ["config","--null","--list"]
[2018-01-31 14:47:52.057690629] process done ExitSuccess
[2018-01-31 14:47:52.058740927] call: git ["--git-dir=../../../../run/media/dxtr/archive/annex","--literal-pathspecs","remote","add","greger","../../../../../home/dxtr/temp/test"]
[2018-01-31 14:47:52.072184794] process done ExitSuccess
[2018-01-31 14:47:52.072509479] call: git ["--git-dir=.git","--work-tree=.","--literal-pathspecs","-c","core.bare=false","remote","add","archive","/run/media/dxtr/archive/annex"]
[2018-01-31 14:47:52.081339812] process done ExitSuccess
[2018-01-31 14:47:52.082154367] read: git ["config","--null","--list"]
[2018-01-31 14:47:52.093569488] process done ExitSuccess
31/Jan/2018:14:47:52 +0100 [Error#yesod-core] there is no available git remote named "archive" @(yesod-core-1.4.37-GCI7RasEcSMIU2vku0fHJ1:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:693:5)
The interesting part here is that if I try to run the failing git commands in the repository it works:
$ git --git-dir=../../../../run/media/dxtr/archive/annex --literal-pathspecs show-ref git-annex
26bcec3f33162a9c1c5b7a39c4828eedfdeae41b refs/heads/git-annex
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
I have been using it for years. Just not the webapp :)
> [[fixed|done]] --[[Joey]]

8
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_10_434c3a17d545b0d37aca55d129ddc66b._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 10"""
date="2018-11-05T18:29:07Z"
content="""
@andrew, take a look at the [[contribute]] page,
bug triage section.
"""]]

9
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_10_528d06a5299104cc17d0b1835fb74118._comment
View file

@ -1,9 +0,0 @@
[[!comment format=mdwn
username="marvin@3296bf3c446430c3b2ebc32b5c784ee976620847"
nickname="marvin"
avatar="http://cdn.libravatar.org/avatar/a07e2adf7ff40bdd4c3fe20ededc0a4e"
subject="comment 10"
date="2018-11-05T18:22:49Z"
content="""
thank you for fixing this bug. you do such a great job and we couldnt be more thankful for your code....
"""]]

35
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_1_a8a77df47eee0e15c25a89b68ec10e8f._comment
View file

@ -1,35 +0,0 @@
[[!comment format=mdwn
username="olaf"
avatar="http://cdn.libravatar.org/avatar/4ae498d3d6ee558d6b65caa658f72572"
subject="I can reproduce"
date="2018-02-19T01:05:06Z"
content="""
### Please describe the problem.
Creating or adding remotes to an _existing_ repository via the webapp results in
> Internal Server Error
>
> there is no available git remote named \"XYZ\"
**Creating a new repository** seems to create the repo and update the remotes (checked via `git` at command line) but does not update the repos in the webapp and results in the error:
19/Feb/2018:11:48:28 +1100 [Error#yesod-core] there is no available git remote named \"XYZ\" @(yesod-core-1.4.37.2-AqCgZCpSjdiDLzXFcWTxPQ:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:693:5)
**Adding an existing repo** to the current repo in the webapp results in the errors: (interesting as it first notes that the remote already exists and then complains that it's not available...)
fatal: remote XYZ already exists.
19/Feb/2018:11:52:24 +1100 [Error#yesod-core] there is no available git remote named \"XYZ\" @(yesod-core-1.4.37.2-AqCgZCpSjdiDLzXFcWTxPQ:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:693:5)
### Version
git-annex version: 6.20180112
build flags: Assistant Webapp Pairing S3(multipartupload)(storageclasses) WebDAV FsEvents ConcurrentOutput TorrentParser MagicMime Feeds Testsuite
dependency versions: aws-0.18 bloomfilter-2.0.1.0 cryptonite-0.24 DAV-1.3.1 feed-1.0.0.0 ghc-8.2.2 http-client-0.5.7.1 persistent-sqlite-2.6.4 torrent-10000.1.1 uuid-1.2.6 yesod-1.4.5
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 SHA1E SHA1 MD5E MD5 WORM URL
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external
local repository version: 5
supported repository versions: 3 5 6
upgrade supported from repository versions: 0 1 2 3 4 5
operating system: darwin x86_64
"""]]

10
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_2_81cdf91b7720cb0a36bdff2815210435._comment
View file

@ -1,10 +0,0 @@
[[!comment format=mdwn
username="jhnichol@cce81d2a480707652a3340ea2f24b3dc4b1f808c"
nickname="jhnichol"
avatar="http://cdn.libravatar.org/avatar/2d05fd7e681bf4838bba8bab538ac65d"
subject="I also have this problem"
date="2018-04-05T15:25:22Z"
content="""
I'm on OSX 10.11.6. I started with a homebrew install, and today I found the native .dmg app. Could there be a conflict between the homebrew install and the .app?
I'm a first time user trying to test this program and not getting very far. I have a minimal understanding of git, and therefore shy away from the CLI.
"""]]

206
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_3_c928d9f0ed85f61270922471c8037643._comment
View file

@ -1,206 +0,0 @@
[[!comment format=mdwn
username="andrew"
avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435"
subject="comment 3"
date="2018-05-04T15:00:18Z"
content="""
I am getting the same error messages as **olaf**. It does not seem to be related to brew vs dmg **jhnichol**.
Using the web-gui I can create one local repo. When I try to create a second local repo, by clicking `Add another repository` | `Add another repository` | `Make Repository` | `Combine the repositories` the webapp then fails with this error message:
Internal Server Error
there is no available git remote named \"a2\"
git-annex version 6.20180409-gfb0780266
Looking at the .git/config files for the repos, the names seem strange/incorrect. The second repo has the remote name listed as my hostname, “bumblebee.local”? Not sure if this is an issue.
Also from a git remote perspective I am a bit confused what I just did? Did I create two completely separate git repos then try to combine them, what does that mean? Shouldn't I have cloned the first repo instead of creating a new one?
When I created two repos on the commandline I didn't run into any issues, but, what I did was create a repo, then clone it into another directory, then added the new repo as a remote of the 1st repo. It seems the combine button in the webapp isn't doing that. Perhaps combine should only be enabled for special remotes, is that the problem?
—Andrew
========== full log below, first steps to make the error with webapp, followed by success on the commandline =============
<pre>
git-annex webapp
make repository:
/Users/Shared/a1
add a file:
image1.png
assistant detects and adds to git-annex
click add another repository
/Users/Shared/a2
assistant creates the directory
runs git init and git-annex init
click:
Combine repositories?
The repository at /Users/Shared/a2 is set up.
Do you want to combine it with your existing repository at /Users/Shared/a1?
The combined repositories will sync and share their files.
Internal Server Error
there is no available git remote named \"a2\"
git-annex version 6.20180409-gfb0780266
At this point /Users/Shared/a2/.git/config has
[core]
repositoryformatversion = 0
filemode = true
bare = true
logallrefupdates = true
ignorecase = true
precomposeunicode = true
[annex]
uuid = 8ee0b541-c429-45c5-aaa2-c4799843f809
version = 5
direct = true
[gc]
auto = 0
[remote \"bumblebee.local\"]
url = ../a1
fetch = +refs/heads/*:refs/remotes/bumblebee.local/*
And /Users/Shared/a1/.git/config has
[core]
repositoryformatversion = 0
filemode = true
bare = true
logallrefupdates = true
ignorecase = true
precomposeunicode = true
[annex]
uuid = 46290480-c956-42ac-9ada-36b2281dbec2
version = 5
direct = true
[gc]
auto = 0
[remote \"a2\"]
url = /Users/Shared/a2
fetch = +refs/heads/*:refs/remotes/a2/*
Perhaps
OK.
Now do this from the commandline:
andrew@bumblebee /Users/Shared$ mkdir a1
andrew@bumblebee /Users/Shared$ cd a1
andrew@bumblebee /Users/Shared/a1$ git init
Initialized empty Git repository in /Users/Shared/a1/.git/
andrew@bumblebee /Users/Shared/a1$ git annex init
init ok
(recording state in git...)
andrew@bumblebee /Users/Shared/a1$ git annex describe here a1
describe here ok
(recording state in git...)
andrew@bumblebee /Users/Shared/a1$ git annex direct
commit
On branch master
Initial commit
nothing to commit
ok
direct ok
andrew@bumblebee /Users/Shared/a1$ cp ~/Desktop/Screen\ Shot\ 2018-05-04\ at\ 10.10.55\ AM.png image1.png
andrew@bumblebee /Users/Shared/a1$ git add image1.png
fatal: This operation must be run in a work tree
andrew@bumblebee /Users/Shared/a1$ ls
image1.png
andrew@bumblebee /Users/Shared/a1$ git annex add image1.png
add image1.png ok
(recording state in git...)
andrew@bumblebee /Users/Shared/a1$
add /Users/Shared/a1 to ~/.config/git-annex/autostart
then:
andrew@bumblebee /Users/Shared/a1$ git-annex assistant --autostart
git-annex autostart in /Users/Shared/a1
ok
andrew@bumblebee /Users/Shared/a1$
launch webapp, see that a1 is listed, add a file, see that webapp detects it
Clone repo1 to another directory
andrew@bumblebee ~/.config/git-annex$ cd
andrew@bumblebee ~$ cd /Users/Shared/
andrew@bumblebee /Users/Shared$ git clone a1 a2
Cloning into 'a2'...
done.
andrew@bumblebee /Users/Shared$ cd a2
andrew@bumblebee /Users/Shared/a2$ git annex init \"a2\"
init a2 (merging origin/git-annex into git-annex...)
(recording state in git...)
ok
(recording state in git...)
andrew@bumblebee /Users/Shared/a2$
Add a2 as a remote from a1
andrew@bumblebee /Users/Shared/a1$ git remote add a2 /Users/Shared/a2
Add a2 to autostart file
Now repos are syncing
Both repos are listed in web-gui when I choose a2 as the repo, only one repo is listed in the web-gui when I choose a1 as the repo.
andrew@bumblebee /Users/Shared/a1$ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = true
logallrefupdates = true
ignorecase = true
precomposeunicode = true
[annex]
uuid = f65fd001-b6ea-4a86-9256-2387c830f933
version = 5
direct = true
[remote \"a2\"]
url = /Users/Shared/a2
fetch = +refs/heads/*:refs/remotes/a2/*
annex-uuid = f9e9f00a-ae70-4c2d-bac3-fe8d6d05a4ea
andrew@bumblebee /Users/Shared/a2$ cat .git/config
[core]
repositoryformatversion = 0
filemode = true
bare = false
logallrefupdates = true
ignorecase = true
precomposeunicode = true
[remote \"origin\"]
url = /Users/Shared/a1
fetch = +refs/heads/*:refs/remotes/origin/*
annex-uuid = f65fd001-b6ea-4a86-9256-2387c830f933
[annex]
uuid = f9e9f00a-ae70-4c2d-bac3-fe8d6d05a4ea
version = 5
</pre>
"""]]

13
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_4_52df3e78719c529987621b212588b785._comment
View file

@ -1,13 +0,0 @@
[[!comment format=mdwn
username="AlexP"
avatar="http://cdn.libravatar.org/avatar/a5756f1e491fa69cba8c2338ce459ed8"
subject="any update on this?"
date="2018-08-02T20:01:57Z"
content="""
does anyone have a solution to this? I can't seem to add remotes through the webapp. I consistantly get the following error:
Internal Server Error
there is no available git remote named \"blablabla\"
thanks
"""]]

8
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_5_0159868320e98ed614cefa4bb73f9ab0._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="torpidus"
avatar="http://cdn.libravatar.org/avatar/997fb77747b008a26383426ae6561368"
subject="comment 5"
date="2018-09-16T18:40:43Z"
content="""
This affects me also. git-annex in version of August 8th, 2018.
"""]]

37
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_6_bb6c572eb9b9d5d435bdb6eeb78a11f9._comment
View file

@ -1,37 +0,0 @@
[[!comment format=mdwn
username="stefankangas@2fc5a0baba35168e9f9b5b72d5204558fd964c32"
nickname="stefankangas"
avatar="http://cdn.libravatar.org/avatar/5bef54a6599375e6bfe9da041e04b588"
subject="Same issue on OSX / git-annex 6.20180807"
date="2018-10-01T12:49:27Z"
content="""
I'm seeing the same issue on OSX when adding a \"Remote server\", using git-annex version 6.20180807. This is on a completely new repository that I've created in \"~/annex\", with no files in it.
After clicking \"Combine repositories\", I get the following error:
Internal Server Error
there is no available git remote named \"mydomain.example.com_annex\"
Where mydomain.example.com is the address to my ssh server.
The logs say:
[2018-10-01 14:39:44.352157] main: starting assistant version 6.20180807
[2018-10-01 14:39:44.416265] Cronner: You should enable consistency checking to protect your data.
(scanning...) [2018-10-01 14:39:44.670591] Watcher: Performing startup scan
(started...)
01/Oct/2018:14:40:13 +0200 [Error#yesod-core] there is no available git remote named \"mydomain.example.com_annex\" @(yesod-core-1.4.37.3-2QxllzSqvdqJbUCjADwK0K:Yesod.Core.Class.Yesod ./Yesod/Core/Class/Yesod.hs:693:5)
It does not matter if the remote repository has been created or not - I still see the same error. Also, my local \"~/annex\" git repository has a remote named \"mydomain.example.com_annex\":
# git remote show mydomain.example.com_annex
mesg: ttyname failed: Inappropriate ioctl for device
* remote mydomain.example.com_annex
Fetch URL: ssh://skangas@mydomain.example.com/~/annex/
Push URL: ssh://skangas@mydomain.example.com/~/annex/
HEAD branch: (unknown)
Remote branch:
git-annex new (next fetch will store in remotes/mydomain.example.com_annex)
Local ref configured for 'git push':
git-annex pushes to git-annex (local out of date)
"""]]

9
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_7_cc0b93a23da7fb9e1b3044f17e9fc3d2._comment
View file

@ -1,9 +0,0 @@
[[!comment format=mdwn
username="marvin@3296bf3c446430c3b2ebc32b5c784ee976620847"
nickname="marvin"
avatar="http://cdn.libravatar.org/avatar/a07e2adf7ff40bdd4c3fe20ededc0a4e"
subject="comment 7"
date="2018-10-25T10:23:49Z"
content="""
i can reproduce this and struggle with it. i cant add any remote repo through the webapp.
"""]]

20
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_8_4415e7897cca54e004f3cb06031753ae._comment
View file

@ -1,20 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 8"""
date="2018-10-29T19:36:51Z"
content="""
Sorry for leaving such a bad bug unaddressed so long. (And in fact a
reversion since it used to work fine and I broke it about a month before
this bug was opened.)
It's fixed now.
Bear in mind that I have a backlog that is literally
over 400 items long and just can't get to everything promptly.
Unsure why I didn't notice one of the several followups in my
triage operations, other than the assistant being a ways down
my prority list and bug reports about it often being not detailed enough
and taking a lot of time to understand. If anyone would like to help
triage out important problems like this one that I may be missing,
that would be great.
"""]]

12
doc/bugs/Can__39__t_add_remotes_through_the_web_assistant/comment_9_4081e8a2fa3899942f27a6fa356f9c63._comment
View file

@ -1,12 +0,0 @@
[[!comment format=mdwn
username="andrew"
avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435"
subject="comment 9"
date="2018-11-01T12:15:34Z"
content="""
Thank you for fixing!
|| If anyone would like to help triage out important problems like this one that I may be missing, that would be great.
I can try. How would you like to receive this information?
"""]]

55
doc/bugs/Can__39__t_compile_on_FreeBSD__58____Issues_with_System.Posix.Files.mdwn
View file

@ -1,55 +0,0 @@
### Please describe the problem.
git-annex can't compile on FreeBSD; specifically, the build fails due to issues with System.Posix.Files.
### What steps will reproduce the problem?
1. git clone git://git-annex.branchable.com/ git-annex
2. cd git-annex
3. stack setup
4. stack install
### What version of git-annex are you using? On what operating system?
git-annex HEAD.
FreeBSD 11.1-RELEASE r321309 GENERIC amd64
### Please provide any additional information below.
Let me know if you'd like me to set up a FreeBSD development environment for you to SSH into - happy to do that if it helps you in any way.
Compilation failure is as follows:
Configuring git-annex-6.20180807...
git-annex-6.20180807: build (exe)
Preprocessing executable 'git-annex' for git-annex-6.20180807...
[124 of 586] Compiling Utility.DirWatcher.Kqueue ( Utility/DirWatcher/Kqueue.hs, .stack-work/dist/x86_64-freebsd/Cabal-1.24.2.0/build/git-annex/git-annex-tmp/Utility/Di
rWatcher/Kqueue.o )
/usr/home/duncan/code/git-annex/Utility/DirWatcher/Kqueue.hs:112:49: error:
Not in scope: ‘Files.openFd’
Module ‘System.Posix.Files’ does not export ‘openFd’.
/usr/home/duncan/code/git-annex/Utility/DirWatcher/Kqueue.hs:112:66: error:
Not in scope: data constructor ‘Files.ReadOnly’
Module ‘System.Posix.Files’ does not export ‘ReadOnly’.
/usr/home/duncan/code/git-annex/Utility/DirWatcher/Kqueue.hs:112:89: error:
Not in scope: ‘Files.defaultFileFlags’
Module ‘System.Posix.Files’ does not export ‘defaultFileFlags’.
/usr/home/duncan/code/git-annex/Utility/DirWatcher/Kqueue.hs:132:15: error:
Not in scope: ‘Files.closeFd’
Module ‘System.Posix.Files’ does not export ‘closeFd’.
/usr/home/duncan/code/git-annex/Utility/DirWatcher/Kqueue.hs:170:14: error:
Not in scope: ‘Files.closeFd’
Module ‘System.Posix.Files’ does not export ‘closeFd’.
-- While building custom Setup.hs for package git-annex-6.20180807 using:
/usr/home/duncan/code/git-annex/.stack-work/dist/x86_64-freebsd/Cabal-1.24.2.0/setup/setup --builddir=.stack-work/dist/x86_64-freebsd/Cabal-1.24.2.0 build exe:git
-annex --ghc-options " -ddump-hi -ddump-to-file"
Process exited with code: ExitFailure 1
> [[done]] --[[Joey]]

7
doc/bugs/Can__39__t_compile_on_FreeBSD__58____Issues_with_System.Posix.Files/comment_1_c8d41357ea9d0ac4601e066982058545._comment
View file

@ -1,7 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2018-09-24T15:24:30Z"
content="""
Seems it also needs to import System.Posix.IO, which I've now committed.
"""]]

72
doc/bugs/Can__39__t_compile_on_FreeBSD__58___alex__44___StateVar__44___SafeSemaphore__44___IfElse_fail.mdwn
View file

@ -1,72 +0,0 @@
### Please describe the problem.
git-annex won't compile on FreeBSD 12.0.
### What steps will reproduce the problem?
[[!format txt """
git clone git://git-annex.branchable.com/ /tmp/git-annex
cd /tmp/git-annex
stack setup
stack install
"""]]
### What version of git-annex are you using? On what operating system?
git-annex HEAD, on FreeBSD 12.0. stack Version 1.7.1 x86_64. The Glorious Glasgow Haskell Compilation System, version 8.4.3.
### Please provide any additional information below.
[[!format txt """
clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-nopie' [-Wunused-command-line-argument]
stack will use a sandboxed GHC it installed
For more information on paths, see 'stack path' and 'stack exec env'
To use this GHC and packages outside of a project, consider using:
stack ghc, stack ghci, stack runghc, or stack exec
IfElse-0.85: configure
SafeSemaphore-0.10.1: configure
StateVar-1.1.1.1: configure
alex-3.2.4: configure
-- While building custom Setup.hs for package alex-3.2.4 using:
/root/.stack/setup-exe-cache/x86_64-freebsd/Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.4 --builddir=.stack-work/dist/x86_64-freebsd/Cabal-2.2.0.1 configure --with-ghc=/root/.stack/programs/x86_64-freebsd/ghc-8.4.4/bin/ghc --with-ghc-pkg=/root/.stack/programs/x86_64-freebsd/ghc-8.4.4/bin/ghc-pkg --user --package-db=clear --package-db=global --package-db=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/pkgdb --libdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/lib --bindir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/bin --datadir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/share --libexecdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/libexec --sysconfdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/etc --docdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/doc/alex-3.2.4 --htmldir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/doc/alex-3.2.4 --haddockdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/doc/alex-3.2.4 --dependency=array=array-0.5.2.0 --dependency=base=base-4.11.1.0 --dependency=containers=containers-0.5.11.0 --dependency=directory=directory-1.3.1.5
Process exited with code: ExitFailure 1
Logs have been written to: /tmp/git-annex/.stack-work/logs/alex-3.2.4.log
Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.4: No cabal file found.
Please create a package description file <pkgname>.cabal
-- While building custom Setup.hs for package StateVar-1.1.1.1 using:
/root/.stack/setup-exe-cache/x86_64-freebsd/Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.4 --builddir=.stack-work/dist/x86_64-freebsd/Cabal-2.2.0.1 configure --with-ghc=/root/.stack/programs/x86_64-freebsd/ghc-8.4.4/bin/ghc --with-ghc-pkg=/root/.stack/programs/x86_64-freebsd/ghc-8.4.4/bin/ghc-pkg --user --package-db=clear --package-db=global --package-db=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/pkgdb --libdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/lib --bindir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/bin --datadir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/share --libexecdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/libexec --sysconfdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/etc --docdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/doc/StateVar-1.1.1.1 --htmldir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/doc/StateVar-1.1.1.1 --haddockdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/doc/StateVar-1.1.1.1 --dependency=base=base-4.11.1.0 --dependency=stm=stm-2.4.5.1 --dependency=transformers=transformers-0.5.5.0
Process exited with code: ExitFailure 1
Logs have been written to: /tmp/git-annex/.stack-work/logs/StateVar-1.1.1.1.log
Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.4: No cabal file found.
Please create a package description file <pkgname>.cabal
-- While building custom Setup.hs for package SafeSemaphore-0.10.1 using:
/root/.stack/setup-exe-cache/x86_64-freebsd/Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.4 --builddir=.stack-work/dist/x86_64-freebsd/Cabal-2.2.0.1 configure --with-ghc=/root/.stack/programs/x86_64-freebsd/ghc-8.4.4/bin/ghc --with-ghc-pkg=/root/.stack/programs/x86_64-freebsd/ghc-8.4.4/bin/ghc-pkg --user --package-db=clear --package-db=global --package-db=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/pkgdb --libdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/lib --bindir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/bin --datadir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/share --libexecdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/libexec --sysconfdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/etc --docdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/doc/SafeSemaphore-0.10.1 --htmldir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/doc/SafeSemaphore-0.10.1 --haddockdir=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/doc/SafeSemaphore-0.10.1 --dependency=base=base-4.11.1.0 --dependency=containers=containers-0.5.11.0 --dependency=stm=stm-2.4.5.1
Process exited with code: ExitFailure 1
Logs have been written to: /tmp/git-annex/.stack-work/logs/SafeSemaphore-0.10.1.log
Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.4: No cabal file found.
Please create a package description file <pkgname>.cabal
-- While building custom Setup.hs for package IfElse-0.85 using:
/root/.stack/setup-exe-cache/x86_64-freebsd/Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.4 --builddir=.stack-work/dist/x86_64-freebsd/Cabal-2.2.0.1 configure --with-ghc=/root/.stack/programs/x86_64-freebsd/ghc-8.4.4/bin/ghc --with-ghc-pkg=/root/.stack/programs/x86_64-freebsd/ghc-8.4.4/bin/ghc-pkg --user --package-db=clear --package-db=global --package-db=/root/.stack/snapshots/x86_64-freebsd/lts-12.19/8.4.4/pkgdb --package-db=/tmp/git-annex/.stack-work/install/x86_64-freebsd/lts-12.19/8.4.4/pkgdb --libdir=/tmp/git-annex/.stack-work/install/x86_64-freebsd/lts-12.19/8.4.4/lib --bindir=/tmp/git-annex/.stack-work/install/x86_64-freebsd/lts-12.19/8.4.4/bin --datadir=/tmp/git-annex/.stack-work/install/x86_64-freebsd/lts-12.19/8.4.4/share --libexecdir=/tmp/git-annex/.stack-work/install/x86_64-freebsd/lts-12.19/8.4.4/libexec --sysconfdir=/tmp/git-annex/.stack-work/install/x86_64-freebsd/lts-12.19/8.4.4/etc --docdir=/tmp/git-annex/.stack-work/install/x86_64-freebsd/lts-12.19/8.4.4/doc/IfElse-0.85 --htmldir=/tmp/git-annex/.stack-work/install/x86_64-freebsd/lts-12.19/8.4.4/doc/IfElse-0.85 --haddockdir=/tmp/git-annex/.stack-work/install/x86_64-freebsd/lts-12.19/8.4.4/doc/IfElse-0.85 --dependency=base=base-4.11.1.0 --dependency=mtl=mtl-2.2.2
Process exited with code: ExitFailure 1
Logs have been written to: /tmp/git-annex/.stack-work/logs/IfElse-0.85.log
Cabal-simple_mPHDZzAJ_2.2.0.1_ghc-8.4.4: No cabal file found.
Please create a package description file <pkgname>.cabal
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes! git-annex has been _very_ helpful for my personal website (see <https://duncan.bayne.id.au/blog/images-fixed.html>), and was working like a charm on FreeBSD 11.2.
> [[done]], not a bug in git-annex. --[[Joey]]

10
doc/bugs/Can__39__t_compile_on_FreeBSD__58___alex__44___StateVar__44___SafeSemaphore__44___IfElse_fail/comment_1_ec60a8b7fe91d62c60406315891c8811._comment
View file

@ -1,10 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2019-01-01T16:08:20Z"
content="""
This is a failure installing depedencies of git-annex, and it looks kind of
like your cabal or haskell toolchain is broken.
This is not a bug in git-annex.
"""]]

8
doc/bugs/Can__39__t_compile_on_FreeBSD__58___alex__44___StateVar__44___SafeSemaphore__44___IfElse_fail/comment_2_7159525b300cd606bf445d5204edd95b._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="duncan_bayne"
avatar="http://cdn.libravatar.org/avatar/2fc23e2009234ad965f9d5d796400417"
subject="Thanks"
date="2019-01-01T22:26:45Z"
content="""
Thanks joey; I'll follow up w/ the FreeBSD folks. Sounds like a problem with the port.
"""]]

8
doc/bugs/Can__39__t_compile_on_FreeBSD__58___alex__44___StateVar__44___SafeSemaphore__44___IfElse_fail/comment_3_d752f3bae244af1bb06741cfb31d46c2._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="duncan_bayne"
avatar="http://cdn.libravatar.org/avatar/2fc23e2009234ad965f9d5d796400417"
subject="Bug raised"
date="2019-01-08T21:13:38Z"
content="""
I've raised this with the maintainers of the Haskell toolchain on FreeBSD, and will post updates here.
"""]]

8
doc/bugs/Can__39__t_compile_on_FreeBSD__58___alex__44___StateVar__44___SafeSemaphore__44___IfElse_fail/comment_4_7030999ed483c680a80225a26a051b78._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="duncan_bayne"
avatar="http://cdn.libravatar.org/avatar/2fc23e2009234ad965f9d5d796400417"
subject="Known issue"
date="2019-01-09T09:17:20Z"
content="""
This is a known issue, and is being fixed: https://github.com/commercialhaskell/stack/issues/3515
"""]]

57
doc/bugs/Can__39__t_use_adjusted_branch_in_v6__44___if_submodule_already_is_using_this_feature.mdwn
View file

@ -1,57 +0,0 @@
### Please describe the problem.
If a v6 submodule is using an adjusted branch, `git annex adjust --unlock` fails in its superproject.
### What steps will reproduce the problem?
[[!format sh """
#!/bin/bash
set -ex
d=$(mktemp -d)
echo "directory: $d"
cd $d
git init
git annex init --version=6
echo whatever > file
git annex add file
git commit -m "file added"
mkdir sub
cd sub
git init
git annex init --version=6
echo something > subfile
git annex add subfile
git commit -m "subfile added."
cd ..
git submodule add ./sub sub
git commit -m "submodule added"
cd sub
git annex adjust --unlock
cd ..
git annex adjust --unlock
"""]]
### What version of git-annex are you using? On what operating system?
[[!format sh """
% git annex version
git-annex version: 6.20170209+gitg16be7b5cc-1~ndall+1
build flags: Assistant Webapp Pairing Testsuite S3(multipartupload)(storageclasses) WebDAV Inotify DBus DesktopNotify ConcurrentOutput TorrentParser MagicMime Feeds Quvi
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 SHA1E SHA1 MD5E MD5 WORM URL
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external
local repository version: unknown
supported repository versions: 3 5 6
upgrade supported from repository versions: 0 1 2 3 4 5
operating system: linux x86_64
"""]]
### 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.
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
> [[fixed|done]] --[[Joey]]

20
doc/bugs/Can__39__t_use_adjusted_branch_in_v6__44___if_submodule_already_is_using_this_feature/comment_1_176faba802ecd62b04c06c6dab77f5f3._comment
View file

@ -1,20 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2017-02-20T17:13:54Z"
content="""
Error message is:
git-annex: unexpected object type "comm"
What it's actually choking on is the "commit" object for the submodule,
in git-ls-tree output. Doesn't matter if the submodule uses
adjusted branches or not.
The parser for ls-tree output is buggy;
it's expecting only "blob" and "tree", so pulls out a fixed width 4
characters: "comm"
Also, the adjusted branch code needs to be made to skip over CommitObjects,
once the parser is fixed to generate them.
"""]]

51
doc/bugs/Cannot_build_with_GHC_8.2.1.mdwn
View file

@ -1,51 +0,0 @@
### Please describe the problem.
git-annex cannot build with GHC 8.2.1
### What steps will reproduce the problem?
cabal install --jobs=8 --max-backjumps=100000 --only-dependencies --flags=s3\ webapp
### What version of git-annex are you using? On what operating system?
Tested with 6.20170520 and HEAD at a983877279d5157d4e7a8c2397d9e541e3c41fa6
### Please provide any additional information below.
Discovered during https://github.com/Homebrew/homebrew-core/pull/15934
[[!format sh """
==> cabal install --jobs=8 --max-backjumps=100000 --only-dependencies --flags=s3 webapp
clang: warning: -Wl,-headerpad_max_install_names: 'linker' input unused
clang: warning: argument unused during compilation: '-L/usr/local/opt/gettext/lib'
clang: warning: argument unused during compilation: '-L/usr/local/opt/libffi/lib'
clang: warning: argument unused during compilation: '-L/usr/local/opt/readline/lib'
clang: warning: argument unused during compilation: '-L/usr/local/opt/sqlite/lib'
clang: warning: argument unused during compilation: '-L/usr/local/opt/openssl/lib'
clang: warning: argument unused during compilation: '-L/usr/local/opt/icu4c/lib'
clang: warning: argument unused during compilation: '-L/usr/local/lib'
clang: warning: argument unused during compilation: '-L/System/Library/Frameworks/OpenGL.framework/Versions/Current/Libraries'
Resolving dependencies...
cabal: Could not resolve dependencies:
trying: git-annex-6.20170520 (user goal)
trying: base-4.10.0.0/installed-4.1... (dependency of git-annex-6.20170520)
next goal: sandi (dependency of git-annex-6.20170520)
rejecting: sandi-0.4.0 (conflict: base==4.10.0.0/installed-4.1..., sandi =>
base>=4.7 && <4.10)
rejecting: sandi-0.3.6, sandi-0.3.5 (conflict:
base==4.10.0.0/installed-4.1..., sandi => base>=4.7 && <4.9)
rejecting: sandi-0.3.4 (conflict: base==4.10.0.0/installed-4.1..., sandi =>
base==4.8.*)
rejecting: sandi-0.3.3, sandi-0.3.2, sandi-0.3.1 (conflict:
base==4.10.0.0/installed-4.1..., sandi => base==4.7.*)
rejecting: sandi-0.3.0.1 (conflict: base==4.10.0.0/installed-4.1..., sandi =>
base==4.6.* || ==4.7.*)
rejecting: sandi-0.3.0 (conflict: base==4.10.0.0/installed-4.1..., sandi =>
base==4.7.*)
rejecting: sandi-0.2.3, sandi-0.2.2.1, sandi-0.2.2, sandi-0.2.1 (conflict:
base==4.10.0.0/installed-4.1..., sandi => base>=4.5 && <4.7)
rejecting: sandi-0.2, sandi-0.1.1, sandi-0.1 (conflict:
base==4.10.0.0/installed-4.1..., sandi => base==4.6.*)
Dependency tree exhaustively searched.
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes :)
> [[fixed|done]] --[[Joey]]

10
doc/bugs/Cannot_build_with_GHC_8.2.1/comment_1_ffd824d79ec303d35b83255f0417d23a._comment
View file

@ -1,10 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 1"""
date="2017-07-28T13:05:38Z"
content="""
I don't see any git-annex failure to build here. Cabal is failing to
install sandi, a dependency. That package needs to have its dependency on
base updated to allow building with the new ghc. Quite likely simply
adjusting the dependency version will work.
"""]]

67
doc/bugs/Cannot_build_with_GHC_8.2.1/comment_2_0796d1dfcf7116c38451febb9701c857._comment
View file

@ -1,67 +0,0 @@
[[!comment format=mdwn
username="ilovezfs"
avatar="http://cdn.libravatar.org/avatar/f2b3954cf2ed0a551de9a49d3b6a64d0"
subject="pipe: resource exhausted (Too many open files)"
date="2017-07-30T16:05:10Z"
content="""
Hi Joey,
Yes, I can work around that particular failure by tweaking constraints.
In particular,
--allow-newer=\"sandi:base\" --allow-newer=\"aws:time\"
I also first need to \"cabal install Cabal<1.25\" because git-annex seems
to have a compatibility problem with Cabal-2.0.0.2. The error with
Cabal-2.0.0.2 is
[[!format sh \"\"\"
Building executable 'git-annex' for git-annex-6.20170520..
Build/BuildVersion.hs:1:1: error:
File name does not match module name:
Saw: ‘Main’
Expected: ‘Build.BuildVersion’
|
1 | {- Outputs the version of git-annex that was built, for use by
| ^
cabal: Leaving directory '.'
cabal: Error: some packages failed to install:
git-annex-6.20170520-3mbb3kAWTlXI0EMervIo66 failed during the building phase.
The exception was:
ExitFailure 1
\"\"\"]]
But, once I've installed the lower version of Cabal, and tweaked the
constraints for sandi and for aws, git-annex does build successfully.
However, at that point a more serious issue comes up when I run \"git
annex test\" and here is the full log:
https://gist.github.com/ilovezfs/d430f589d87d7f7237591cd51b2b94cb
Here is a snippet:
[[!format sh \"\"\"
From ../../.t/tmprepo53
* [new branch] git-annex -> r2/git-annex
* [new branch] master -> r2/master
* [new branch] synced/master -> r2/synced/master
conflictor/subfile
conflictor.variant-cc12
conflictor/subfile
conflictor.variant-cc12
OK (3.27s)
conflict resolution symlink bit: OK
conflict resolution (uncommitted local file): FAIL (0.49s)
sync failed in r1
conflict resolution (removed file): FAIL
Exception: git: createProcess: runInteractiveProcess: pipe: resource exhausted (Too many open files)
conflict resolution (nonannexed file): FAIL
Exception: git: createProcess: runInteractiveProcess: pipe: resource exhausted (Too many open files)
conflict resolution (nonannexed symlink): FAIL (0.03s)
git annex init failed
conflict resolution (mixed locked and unlocked file): FAIL
Exception: git: createProcess: runInteractiveProcess: pipe: resource exhausted (Too many open files)
map: FAIL
Exception: git: createProcess: runInteractiveProcess: pipe: resource exhausted (Too many open files)
\"\"\"]]
"""]]

9
doc/bugs/Cannot_build_with_GHC_8.2.1/comment_3_c43f26b71cd7335951fb71f68b84ed10._comment
View file

@ -1,9 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2017-08-01T16:18:18Z"
content="""
The cabal bug is <https://github.com/haskell/cabal/issues/4655>,
and it seems like it would require *extensive* changes to git-annex's
source code to work around this cabal behavior.
"""]]

41
doc/bugs/Cannot_build_with_GHC_8.2.1/comment_4_f508b6db0513edcdc8600df405ce1913._comment
View file

@ -1,41 +0,0 @@
[[!comment format=mdwn
username="https://launchpad.net/~felixonmars"
nickname="felixonmars"
avatar="http://cdn.libravatar.org/avatar/17284a3bb2e4ad9d3be8fab31f49865be9c1dc22143c728de731fe800a335d38"
subject="comment 4"
date="2017-08-17T19:10:24Z"
content="""
I managed to build git-annex with GHC 8.2.1 on Linux by removing a bunch of Win32/OSX modules from the cabal file and another small fix. However, there are two test failures when running git-annex test. Do you think it's related to the GHC version?
Tests
QuickCheck
prop_isomorphic_deencode_git: FAIL
*** Failed! Falsifiable (after 6 tests and 1 shrink):
\"\1086483\"
Use --quickcheck-replay=615269 to reproduce.
prop_isomorphic_deencode: FAIL
*** Failed! Falsifiable (after 3 tests and 1 shrink):
\"\185545\"
Use --quickcheck-replay=915399 to reproduce.
...
2 out of 293 tests failed (486.80s)
(This could be due to a bug in git-annex, or an incompatibility
with utilities, such as git, installed on this system.)
All other tests are working, though.
Versions:
$ git --version
git version 2.14.1
$ git-annex version
git-annex version: 6.20170612-ge4100fd60
build flags: Assistant Webapp Pairing Testsuite S3(multipartupload)(storageclasses) WebDAV Inotify DBus DesktopNotify ConcurrentOutput TorrentParser MagicMime Feeds Quvi
dependency versions: aws-0.16 bloomfilter-2.0.1.0 cryptonite-0.24 DAV-1.3.1 feed-0.3.12.0 ghc-8.2.1 http-client-0.5.7.0 persistent-sqlite-2.6.2 torrent-10000.1.1 uuid-1.3.13 yesod-1.4.5
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 SHA1E SHA1 MD5E MD5 WORM URL
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external
The changes to build: https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/git-annex&id=e75ed0bdf9748df000aa584e0ebff3b7d56b76d6
"""]]

16
doc/bugs/Cannot_build_with_GHC_8.2.1/comment_5_a0663aeef21b09393600593409f1a7a9._comment
View file

@ -1,16 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 5"""
date="2017-08-17T19:12:09Z"
content="""
Thanks for working on this!
It's entirely possible that the quickcheck tests happen to generate
better test data under the new ghc, and have found an actual bug.
I doubt that it's related to your changes.
I do need git-annex to remain buildable on OSX and Windows. What basically
needs to be done is, instead of sed-ing those files out of the cabal file,
make the cabal file say "if os(windows)" to conditionally include the
modules that only work on one OS.
"""]]

14
doc/bugs/Cannot_build_with_GHC_8.2.1/comment_6_e948c8fcf34559808726aaa0d5f5f020._comment
View file

@ -1,14 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 6"""
date="2017-08-18T15:02:42Z"
content="""
I've updated the cabal file, it should build now. Although unfortunately
the breaking changes to cabal are such that it might still fail to build
with some OS's and some combinations of build flags, where it used to build
before. I only tested on Linux with stack (modified for resolver:
nightly-2017-08-17)
As to the quickcheck failures, I think that's the same problem I already
fixed in [[!commit da8e84efe997fcbfcf489bc4fa9cc835ed131d3a]].
"""]]

9
doc/bugs/Cannot_build_with_GHC_8.2.1/comment_7_bd5b764715a9a7c35921803d534a9989._comment
View file

@ -1,9 +0,0 @@
[[!comment format=mdwn
username="ilovezfs"
avatar="http://cdn.libravatar.org/avatar/f2b3954cf2ed0a551de9a49d3b6a64d0"
subject="Exception: getCurrentDirectory:getWorkingDirectory: resource exhausted (Too many open files)"
date="2017-08-18T18:28:01Z"
content="""
Thanks! 6.20170818 does build with Cabal 2.0.0. However, I'm still seeing the too many open files error.
The log is here: https://gist.github.com/ilovezfs/5dabc76086ba4b028b1eae7f301a5219
"""]]

7
doc/bugs/Cannot_build_with_GHC_8.2.1/comment_8_329e8eb873ca684dc3221b462827ecd5._comment
View file

@ -1,7 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 8"""
date="2017-10-02T16:36:40Z"
content="""
The git-annex test FD leak is now fixed.
"""]]

47
doc/bugs/Cannot_build_with_aws_0.17.1.mdwn
View file

@ -1,47 +0,0 @@
### Please describe the problem.
git-annex doesn't build if the aws dependency is version 0.17.1
This probably wasn't caught during your testing because the stack.yaml is currently set to use aws-0.16.
### What steps will reproduce the problem?
cabal install with --flags=s3\ webapp
### What version of git-annex are you using? On what operating system?
6.20171003 on macOS
### Please provide any additional information below.
The error is
[[!format sh """
[327 of 580] Compiling Remote.Helper.Http ( Remote/Helper/Http.hs, dist/dist-sandbox-69bd6735/build/git-annex/git-annex-tmp/Remote/Helper/Http.o )
[328 of 580] Compiling Remote.WebDAV ( Remote/WebDAV.hs, dist/dist-sandbox-69bd6735/build/git-annex/git-annex-tmp/Remote/WebDAV.o )
[329 of 580] Compiling Remote.S3 ( Remote/S3.hs, dist/dist-sandbox-69bd6735/build/git-annex/git-annex-tmp/Remote/S3.o )
Remote/S3.hs:501:57: error:
• Couldn't match expected type ‘AWS.Configuration’
with actual type ‘Maybe
http-client-0.5.7.0:Network.HTTP.Client.Types.Proxy
-> AWS.Configuration’
• Probable cause: ‘awscfg’ is applied to too few arguments
In the second argument of ‘S3Handle’, namely ‘awscfg’
In the second argument of ‘($)’, namely ‘S3Handle mgr awscfg s3cfg’
In the second argument of ‘($)’, namely
‘Just $ S3Handle mgr awscfg s3cfg’
|
501 | a $ Just $ S3Handle mgr awscfg s3cfg
| ^^^^^^
cabal: Leaving directory '.'
cabal: Error: some packages failed to install:
git-annex-6.20171003-5GFRliFOEl0KqDuhwYRTdH failed during the building phase.
The exception was:
ExitFailure 1
"""]]
Full build log is here: https://gist.github.com/ilovezfs/661a158dbe8aac33802f9b43eb150539
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes! :)
> [[fixed|done]] --[[Joey]]

11
doc/bugs/Cannot_build_with_aws_0.17.1/comment_1_937238ba11540f1ee9ba8de621277b2f._comment
View file

@ -1,11 +0,0 @@
[[!comment format=mdwn
username="https://launchpad.net/~felixonmars"
nickname="felixonmars"
avatar="http://cdn.libravatar.org/avatar/17284a3bb2e4ad9d3be8fab31f49865be9c1dc22143c728de731fe800a335d38"
subject="comment 1"
date="2017-10-05T14:02:03Z"
content="""
My humble workaround:
sed -i 's/let awscfg = AWS.Configuration AWS.Timestamp awscreds debugMapper$/let awscfg = AWS.Configuration AWS.Timestamp awscreds debugMapper Nothing/ ' Remote/S3.hs
"""]]

31
doc/bugs/DBG__58___running___96____47__Users__47__joey__47__homebrew__47__opt__47__gpg-agent__47__bin__47__gpg-agent__39___for_testing_failed.mdwn
View file

@ -1,31 +0,0 @@
### Please describe the problem.
Issue uploading to S3 remote (Dreamhost)
### What steps will reproduce the problem?
git-annex copy massart/f16_Web1/screencaptures/IMG_5159.MOV --to=cloud
on my repo
### What version of git-annex are you using? On what operating system?
6.20161031-g0a58e94
OS-X 10.11.6
### Please provide any additional information below.
I am using a different WIFI I haven't used before. Maybe it is blocking something…
[[!format sh """
git-annex copy massart/f16_Web1/screencaptures/IMG_5159.MOV --to=cloud
copy massart/f16_Web1/screencaptures/IMG_5159.MOV (checking cloud...) (to cloud...)
17% 0.0 B/s 0sgpg: error running `/Users/joey/homebrew/opt/gpg-agent/bin/gpg-agent': probably not installed
gpg: DBG: running `/Users/joey/homebrew/opt/gpg-agent/bin/gpg-agent' for testing failed: Configuration error
gpg: can't connect to the agent: IPC connect call failed
gpg: problem with the agent: No agent running
35% 1021.8KB/s 30s
user error (gpg ["--quiet","--trust-model","always","--batch","--passphrase-fd","26","--symmetric","--force-mdc","--no-textmode"] exited 2)
failed
git-annex: copy: 1 failed
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
Yes.
[[done]]

14
doc/bugs/DBG__58___running___96____47__Users__47__joey__47__homebrew__47__opt__47__gpg-agent__47__bin__47__gpg-agent__39___for_testing_failed/comment_1_39718e8a35e42421a8aaf3316ae1d76a._comment
View file

@ -1,14 +0,0 @@
[[!comment format=mdwn
username="andrew"
avatar="http://cdn.libravatar.org/avatar/acc0ece1eedf07dd9631e7d7d343c435"
subject="RESOLVED"
date="2016-11-17T14:59:15Z"
content="""
Ooops. I am on OS-X. I use brew for my gnupg installation. It appears I had removed gpg from the path when installing something. I just needed to run to fix:
brew link gnupg2
Thanks,
Andrew
"""]]

31
doc/bugs/Default_startup_command.mdwn
View file

@ -1,31 +0,0 @@
[[!meta title="Android Default startup command"]]
### Please describe the problem.
On a CM11 4.4.4 install, the startup will fail with the default startup command "git annex webapp".
The error message shown is:
```
Falling back to hardcoded app location; cannot find expected files in /data/app-lib
git annex webapp
```
However, using "git-annex webapp", git-annex will run fine.
### What steps will reproduce the problem?
Launch the beta or nightly build for 4.3 and 4.4, wait for error message
### What version of git-annex are you using? On what operating system?
Version "current" as of 2014-11-15 and also version "nightly build" as of 2014-11-15 on Android 4.4.4 CM11, device: Oppo Find 7a
### 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.
"""]]
> Closing as this was a bug in the deprecated Android app. [[done]] --[[Joey]]

29
doc/bugs/Default_startup_command/comment_1_2d63fb301586c9a97ceff1d1b9fafbee._comment
View file

@ -1,29 +0,0 @@
[[!comment format=mdwn
username="git-annex@53a027ebda399714df9272a135f22ac774f3c9f1"
nickname="git-annex"
subject="i can second this"
date="2015-07-26T10:29:32Z"
content="""
I have the same behaviour on CM11 4.4.4 on a Moto G as well.
When i installed git annex i would be greeted by the same message, but then could start the webapp from the menu successfully.
i then proceeded to setup my repo, which synced flawlessly, if i had started the webapp as stated above.
however my files were never automatically synced when just starting the app (terminal window).
Therefore i resorted to \"cd\" to my repo and \"git annex add *\" and \"git annex sync --content\" every time i wanted to sync.
i tried changing the startup command to \"git annex assistant --autostart\", \"git annex assistant --autostart --foreground\", \"cd ../DCIM;git annex sync --content\", \"echo test\" but nothing seems to start (not quite sure how to check for that).
for my shell i had the default/data/data/ga.androidterm/lib/lib.start.so and /data/data/ga.androidterm/runshell if that makes any difference?
not sure if that's related
when trying to manually invoke \"git annex --assistant [--foreground]\" i get:
git annex autostart in /sdcard/DCIM
usage: ionice <pid> [none|rt|be|idle] [prio]
failed
and back to prompt. Not sure if this is CM(11) only?
my git annex version is: 5.20150527-gfc92f13 for android 4.3 and 4.4. if you need more information i'll be happy to provide it, to get this out of the way :D
"""]]

8
doc/bugs/Default_startup_command/comment_2_296de7f38161ebc21da954d46c924c98._comment
View file

@ -1,8 +0,0 @@
[[!comment format=mdwn
username="git-annex@53a027ebda399714df9272a135f22ac774f3c9f1"
nickname="git-annex"
subject="small correction to the above"
date="2015-07-26T10:33:28Z"
content="""
i can not start the webapp via the menu (firefox opens but cant connect to the webapp) but if i do git annex webapp manually in the terminal it works as expected
"""]]

14
doc/bugs/Default_startup_command/comment_3_f388be6121f3449f28aa3d6ca53fa88d._comment
View file

@ -1,14 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 3"""
date="2018-05-08T18:54:32Z"
content="""
I'm closing this bug report because the git-annex Android app that it
was reported on is now deprecated. Instead, we have
a way to run the regular git-annex build for linux on Android in termux:
<https://git-annex.branchable.com/tips/install_on_Android_in_Termux/>
There were a lot of problems with the way the git-annex Android app was
put together, and I hope this new approach avoids them. If you try it and
still have the bug you reported, please followup and I'll reopen it.
"""]]

29
doc/bugs/Error_running_git-annex.app_on_OS_X_10.13.1___40__17B1003__41__.mdwn
View file

@ -1,29 +0,0 @@
### Please describe the problem.
git-annex doesn't start.
### What steps will reproduce the problem?
launch git-annex from terminal (if it is ran from GUI it doesn't open without notifying any error)
### What version of git-annex are you using? On what operating system?
Version: 6.20171128-g58b04cd2e on OS X 10.13.1 (17B1003)
### Please provide any additional information below.
I solved the issue by manually changing the file /Applications/git-annex.app/Contents/MacOS/bundle/B which is an alias pointing to the file /Applications/git-annex.app/Contents/MacOS/bundle/usr/lib/libz.1.dylib with a new alias having the same name 'B' which link to /usr/lib/libz.1.dylb.
I'm pretty sure this is not an optimal and general solution, but it is useful in order to prove what's the problem. Further, for it worked.
[[!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
dyld: Symbol not found: _inflateValidate
Referenced from: /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
Expected in: /Applications/git-annex.app/Contents/MacOS/bundle/B
in /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib
Abort trap: 6
# End of transcript or log.
"""]]
### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders)
> OSX autobuild is updated and no longer contains the copy of libz.
> [[done]]

12
doc/bugs/Error_running_git-annex.app_on_OS_X_10.13.1___40__17B1003__41__/comment_1_0f013027500f03b52e021716e493fbff._comment
View file

@ -1,12 +0,0 @@
[[!comment format=mdwn
username="rameshvenk"
avatar="http://cdn.libravatar.org/avatar/185911818a3eb3795072b1aa1256449c"
subject="dyld: Symbol not found: _inflateValidate"
date="2018-03-04T03:59:42Z"
content="""
Can confirm that this fix did resolve the issue. My version of git annex is as follows
git-annex version: 6.20180226-g15a11fedf
running on 10.13.3
"""]]

20
doc/bugs/Error_running_git-annex.app_on_OS_X_10.13.1___40__17B1003__41__/comment_2_e15b265d67cad6fb914f626e646c2fe7._comment
View file

@ -1,20 +0,0 @@
[[!comment format=mdwn
username="joey"
subject="""comment 2"""
date="2018-03-05T14:40:08Z"
content="""
This is a bit puzzling, since git-annex does not link to libpng.
I think what must be going on os that Cocoa, which git-annex does link to,
links to libpng.
The dmg contains its own copy of zlib, not for git-annex,
which does not directly link to it, but for the embedded copy of curl.
But the linker is told to prefer the bundled libraries, so it tries to use
the bundled zlib with Cocoa.
Upgrading the OSX autobuilder to 10.13 would be the cleanest fix, but
installing a newer zlib on there with homebrew should also work.
Hmm, but I tried homebrew and their zlib does not contain the
`_inflateValidate` symbol.
"""]]

Some files were not shown because too many files have changed in this diff Show more