Recent comments posted to this site:

comment 23 70dcb7e7ffdd14351adaf4c40ee7fdd0
[[!comment Error: unsupported page format hs]]
Mon Jul 27 16:25:03 2015

The effective way to install git-annex and resolve dependencies:

$ sudo pacman -S gsasl git rsync curl wget gnupg openssh cabal-install
$ cabal update
$ cabal install c2hs
$ cabal install git-annex --bindir=$HOME/bin
$ sudo cp ~/bin/git-annex /usr/lib/git-core
Comment by dropped Mon Jul 27 12:01:34 2015
Hi, Thanks for the help :) I didn't exlude any files. Therefore "$BUP_REPO/objects/pack/bup.bloom" gets added by git-annex. This file has to be unlocked beforehand for bup to be running correctly. Best regards
Comment by sfowijowa Fri Jul 17 17:45:24 2015

Yes, Debian has a by now very outdated version of git-annex.

You can clone git-annex's git repo and build a debian package from there; it's been updated for these changes.

Comment by joey Wed Jul 15 15:54:15 2015
hobbes@namagiri:~/src$ sudo apt-get build-dep git-annex
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Build-Depends dependency for git-annex cannot be satisfied because the package libghc-hamlet-dev cannot be found

Hmm, deprecated in favor of libghc-shakespear-dev, according to http://hackage.haskell.org/package/hamlet ...

hobbes@namagiri:~/src/apt-get-source-git-annex$ grep -iR build-depends.*hamlet|tr , \\n
git-annex_5.20141125.dsc:Build-Depends: debhelper (>= 9)
 ghc (>= 7.4)
 cabal-install
 libghc-mtl-dev (>= 2.1.1)
 libghc-missingh-dev
 libghc-data-default-dev
 libghc-hslogger-dev
 libghc-pcre-light-dev
 libghc-sha-dev
 libghc-cryptohash-dev
 libghc-dataenc-dev
 libghc-utf8-string-dev
 libghc-hs3-dev (>= 0.5.6)
 libghc-dav-dev (>= 1.0) [amd64 i386 kfreebsd-amd64 kfreebsd-i386 powerpc]
 libghc-quickcheck2-dev
 libghc-monad-control-dev (>= 0.3)
 libghc-exceptions-dev (>= 0.6)
 libghc-transformers-dev
 libghc-unix-compat-dev
 libghc-dlist-dev
 libghc-uuid-dev
 libghc-json-dev
 libghc-aeson-dev
 libghc-ifelse-dev
 libghc-bloomfilter-dev
 libghc-edit-distance-dev
 libghc-hinotify-dev [linux-any]
 libghc-stm-dev (>= 2.3)
 libghc-dbus-dev (>= 0.10.3) [linux-any]
 libghc-fdo-notify-dev (>= 0.3) [linux-any]
 libghc-yesod-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc]
 libghc-yesod-static-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc]
 libghc-yesod-default-dev [i386 amd64 kfreebsd-amd64 powerpc]
 libghc-hamlet-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc]
 libghc-shakespeare-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc]
 libghc-clientsession-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc]
 libghc-warp-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc]
 libghc-warp-tls-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc]
 libghc-wai-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc]
 libghc-wai-extra-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc]
 libghc-securemem-dev
 libghc-byteable-dev
 libghc-dns-dev
 libghc-case-insensitive-dev
 libghc-http-types-dev
 libghc-http-conduit-dev
 libghc-blaze-builder-dev
 libghc-crypto-api-dev
 libghc-network-multicast-dev
 libghc-network-info-dev [linux-any kfreebsd-any]
 libghc-safesemaphore-dev
 libghc-network-protocol-xmpp-dev (>= 0.4.3-1+b1)
 libghc-gnutls-dev (>= 0.1.4)
 libghc-xml-types-dev
 libghc-async-dev
 libghc-feed-dev (>= 0.3.9.2)
 libghc-regex-tdfa-dev [!mipsel !s390]
 libghc-regex-compat-dev [mipsel s390]
 libghc-tasty-dev (>= 0.7) [!sparc]
 libghc-tasty-hunit-dev [!sparc]
 libghc-tasty-quickcheck-dev [!sparc]
 libghc-tasty-rerun-dev [!sparc]
 libghc-optparse-applicative-dev [!sparc]
 lsof [!kfreebsd-i386 !kfreebsd-amd64 !hurd-any]
 ikiwiki
 perlmagick
 git (>= 1:2.0)
 rsync
 wget
 curl
 openssh-client
 git-remote-gcrypt (>= 0.20130908-6)
 llvm-3.4 [armel armhf]

I think that's the bug, right there: git-annex_5.20141125.dsc.

I hope this helps.

Comment by dave Thu Jul 9 00:07:32 2015

Hey there, i am using Ubuntu 14.04 I have disabled all my repositories and now i cannot open the webapp any more. Any suggestions ?

Comment by dirk.schmidt Wed Jul 8 12:49:01 2015
This is some excellent information. Thank you.
Comment by ghen1 Wed Jul 8 04:08:28 2015

@Giovanni, git is complaining that there is already a remote named "myremote" enabled in the current repository. Perhaps you have reused this name for a different remote.

(This seems to have nothing to do with the page the comment was posted to, which is a bit annoying. Please post questions in the forum and not attached to random other pages.)

Comment by joey Mon Jul 6 19:57:12 2015

@dmitry, it just so happens that directory special remotes honor the annex.diskreserve configuration setting. This normally only applies to the local git repository, and not to remotes, but since directory special remotes are local annex.diskreserve is also checked for them.

There's no currently a way to have a different diskreserve setting for a directory special remote than is used for the local git repository.

Comment by joey Mon Jul 6 19:00:43 2015

@james, since your keyring apparenty contains your secret key, the problem may be in the configuration of your gpg agent or pinentry program. If the agent is unable to use pinentry for some reason, gpg will complain that the secret key is unavailable since it is unable to get the passphrase to unlock it.

I had a similar problem with gpg2 the other day: http://bugs.debian.org/791379

Comment by joey Mon Jul 6 17:42:28 2015