code:
Source: git-annex
Section: utils
Priority: optional
Build-Depends:
	debhelper (>= 9),
	ghc (>= 7.4),
	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 (>= 0.6.1) [amd64 i386 kfreebsd-amd64 kfreebsd-i386 powerpc],
	libghc-quickcheck2-dev,
	libghc-monad-control-dev (>= 0.3),
	libghc-exceptions-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-extensible-exceptions-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 sparc],
	libghc-yesod-static-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc sparc],
	libghc-yesod-default-dev [i386 amd64 kfreebsd-amd64 powerpc sparc],
	libghc-hamlet-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc sparc],
	libghc-shakespeare-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc sparc],
	libghc-clientsession-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc sparc],
	libghc-warp-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc sparc],
	libghc-warp-tls-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc sparc],
	libghc-wai-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc sparc],
	libghc-wai-extra-dev [i386 amd64 kfreebsd-i386 kfreebsd-amd64 powerpc sparc],
	libghc-securemem-dev,
	libghc-byteable-dev,
	libghc-dns-dev,
	libghc-case-insensitive-dev,
	libghc-http-types-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-http-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) [!mipsel !sparc],
	libghc-tasty-hunit-dev [!mipsel !sparc],
	libghc-tasty-quickcheck-dev [!mipsel !sparc],
	libghc-tasty-rerun-dev [!mipsel !sparc],
	libghc-optparse-applicative-dev [!sparc],
	lsof [!kfreebsd-i386 !kfreebsd-amd64],
	ikiwiki,
	perlmagick,
	git (>= 1:1.8.4),
	rsync,
	wget,
	curl,
	openssh-client,
	git-remote-gcrypt (>= 0.20130908-6),
Maintainer: Joey Hess <joeyh@debian.org>
Standards-Version: 3.9.5
Vcs-Git: git://git.kitenet.net/git-annex
Homepage: http://git-annex.branchable.com/
XS-Testsuite: autopkgtest

Package: git-annex
Architecture: any
Section: utils
Depends: ${misc:Depends}, ${shlibs:Depends},
	git (>= 1:1.8.4),
	rsync,
	wget,
	curl,
	openssh-client (>= 1:5.6p1)
Recommends:
	lsof,
	gnupg,
	bind9-host,
	quvi,
	git-remote-gcrypt (>= 0.20130908-6),
	nocache,
Suggests:
	graphviz,
	bup,
	tahoe-lafs,
	libnss-mdns,
Description: manage files with git, without checking their contents into git
 git-annex allows managing files with git, without checking the file
 contents into git. While that may seem paradoxical, it is useful when
 dealing with files larger than git can currently easily handle, whether due
 to limitations in memory, time, or disk space.
 .
 Even without file content tracking, being able to manage files with git,
 move files around and delete files with versioned directory trees, and use
 branches and distributed clones, are all very handy reasons to use git. And
 annexed files can co-exist in the same git repository with regularly
 versioned files, which is convenient for maintaining documents, Makefiles,
 etc that are associated with annexed files but that benefit from full
 revision control.

repo_name: kakafarm/git

path: debian/control

license: unknown


code:
Format: http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
Source: native package

Files: *
Copyright: © 2010-2014 Joey Hess <joey@kitenet.net>
License: GPL-3+

Files: Assistant/WebApp.hs Assistant/WebApp/* templates/* static/*
Copyright: © 2012-2014 Joey Hess <joey@kitenet.net>
           © 2014 Sören Brunk
License: AGPL-3+

Files: Remote/Ddar.hs
Copyright: © 2011 Joey Hess <joey@kitenet.net>
           © 2014 Robie Basak <robie@justgohome.co.uk>
License: GPL-3+

Files: Utility/ThreadScheduler.hs
Copyright: 2011 Bas van Dijk & Roel van Dijk
           2012, 2013 Joey Hess <joey@kitenet.net>
License: BSD-2-clause

Files: Utility/*
Copyright: 2012-2014 Joey Hess <joey@kitenet.net>
License: BSD-2-clause

Files: Utility/Gpg.hs Utility/DirWatcher*
Copyright: © 2010-2014 Joey Hess <joey@kitenet.net>
License: GPL-3+

Files: doc/logo* */favicon.ico standalone/osx/git-annex.app/Contents/Resources/git-annex.icns standalone/android/icons/*
Copyright: 2007 Henrik Nyh <http://henrik.nyh.se/>
           2010 Joey Hess <joey@kitenet.net>
	   2013 John Lawrence
License: other
  Free to modify and redistribute with due credit, and obviously free to use.

Files: Utility/Mounts.hsc
Copyright: Volker Wysk <hsss@volker-wysk.de>
License: LGPL-2.1+

Files: Utility/libmounts.c
Copyright: 1980, 1989, 1993, 1994 The Regents of the University of California
           2001 David Rufino <daverufino@btinternet.com>
           2012 Joey Hess <joey@kitenet.net>
License: BSD-3-clause
 * Copyright (c) 1980, 1989, 1993, 1994
 *      The Regents of the University of California.  All rights reserved.
 * Copyright (c) 2001
 *      David Rufino <daverufino@btinternet.com>
 * Copyright 2012
 *      Joey Hess <joey@kitenet.net>
 *
 * Redistribution and use in source and binary forms, with or without
 * modification, are permitted provided that the following conditions
 * are met:
 * 1. Redistributions of source code must retain the above copyright
 *    notice, this list of conditions and the following disclaimer.
 * 2. Redistributions in binary form must reproduce the above copyright
 *    notice, this list of conditions and the following disclaimer in the
 *    documentation and/or other materials provided with the distribution.
 * 3. Neither the name of the University nor the names of its contributors
 *    may be used to endorse or promote products derived from this software
 *    without specific prior written permission.
 *
 * THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
 * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 * ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
 * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 * SUCH DAMAGE.

Files: static/jquery*
Copyright: © 2005-2011 by John Resig, Branden Aaron & Jörn Zaefferer
           © 2011 The Dojo Foundation
License: MIT or GPL-2
 The full text of version 2 of the GPL is distributed in
 /usr/share/common-licenses/GPL-2 on Debian systems. The text of the MIT
 license follows:
 .
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the
 "Software"), to deal in the Software without restriction, including
 without limitation the rights to use, copy, modify, merge, publish,
 distribute, sublicense, and/or sell copies of the Software, and to
 permit persons to whom the Software is furnished to do so, subject to
 the following conditions:
 .
 The above copyright notice and this permission notice shall be
 included in all copies or substantial portions of the Software.
 .
 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
 MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
 NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
 LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
 OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
 WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Files: static/*/bootstrap* static/*/glyphicons-halflings*
Copyright: 2012-2014 Twitter, Inc.
License: MIT
  Copyright (c) 2011-2014 Twitter, Inc
  .
  Permission is hereby granted, free of charge, to any person obtaining a copy
  of this software and associated documentation files (the "Software"), to deal
  in the Software without restriction, including without limitation the rights
  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
  copies of the Software, and to permit persons to whom the Software is
  furnished to do so, subject to the following conditions:
  .
  The above copyright notice and this permission notice shall be included in
  all copies or substantial portions of the Software.
  .
  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
  THE SOFTWARE.

License: GPL-3+
 The full text of version 3 of the GPL is distributed as doc/license/GPL in
 this package's source, or in /usr/share/common-licenses/GPL-3 on
 Debian systems.

License: LGPL-2.1+
 The full text of version 2.1 of the LGPL is distributed as doc/license/LGPL
 in this package's source, or in /usr/share/common-licenses/LGPL-2.1
 on Debian systems.

License: BSD-2-clause
 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions
 are met:
 1. Redistributions of source code must retain the above copyright
    notice, this list of conditions and the following disclaimer.
 2. Redistributions in binary form must reproduce the above copyright
    notice, this list of conditions and the following disclaimer in the
    documentation and/or other materials provided with the distribution.
 .
 THIS SOFTWARE IS PROVIDED BY AUTHORS AND CONTRIBUTORS ``AS IS'' AND
 ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
 IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
 ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE
 FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
 OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
 HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
 LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
 OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
 SUCH DAMAGE.

License: AGPL-3+
                      GNU AFFERO GENERAL PUBLIC LICENSE
                         Version 3, 19 November 2007
 .
   Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
   Everyone is permitted to copy and distribute verbatim copies
   of this license document, but changing it is not allowed.
 .
                              Preamble
 .
    The GNU Affero General Public License is a free, copyleft license for
  software and other kinds of works, specifically designed to ensure
  cooperation with the community in the case of network server software.
 .
    The licenses for most software and other practical works are designed
  to take away your freedom to share and change the works.  By contrast,
  our General Public Licenses are intended to guarantee your freedom to
  share and change all versions of a program--to make sure it remains free
  software for all its users.
 .
    When we speak of free software, we are referring to freedom, not
  price.  Our General Public Licenses are designed to make sure that you
  have the freedom to distribute copies of free software (and charge for
  them if you wish), that you receive source code or can get it if you
  want it, that you can change the software or use pieces of it in new
  free programs, and that you know you can do these things.
 .
    Developers that use our General Public Licenses protect your rights
  with two steps: (1) assert copyright on the software, and (2) offer
  you this License which gives you legal permission to copy, distribute
  and/or modify the software.
 .
    A secondary benefit of defending all users' freedom is that
  improvements made in alternate versions of the program, if they
  receive widespread use, become available for other developers to
  incorporate.  Many developers of free software are heartened and
  encouraged by the resulting cooperation.  However, in the case of
  software used on network servers, this result may fail to come about.
  The GNU General Public License permits making a modified version and
  letting the public access it on a server without ever releasing its
  source code to the public.
 .
    The GNU Affero General Public License is designed specifically to
  ensure that, in such cases, the modified source code becomes available
  to the community.  It requires the operator of a network server to
  provide the source code of the modified version running there to the
  users of that server.  Therefore, public use of a modified version, on
  a publicly accessible server, gives the public access to the source
  code of the modified version.
 .
    An older license, called the Affero General Public License and
  published by Affero, was designed to accomplish similar goals.  This is
  a different license, not a version of the Affero GPL, but Affero has
  released a new version of the Affero GPL which permits relicensing under
  this license.
 .
    The precise terms and conditions for copying, distribution and
  modification follow.
 .
                         TERMS AND CONDITIONS
 .
    0. Definitions.
 .
    "This License" refers to version 3 of the GNU Affero General Public License.
 .
    "Copyright" also means copyright-like laws that apply to other kinds of
  works, such as semiconductor masks.
 .
    "The Program" refers to any copyrightable work licensed under this
  License.  Each licensee is addressed as "you".  "Licensees" and
  "recipients" may be individuals or organizations.
 .
    To "modify" a work means to copy from or adapt all or part of the work
  in a fashion requiring copyright permission, other than the making of an
  exact copy.  The resulting work is called a "modified version" of the
  earlier work or a work "based on" the earlier work.
 .
    A "covered work" means either the unmodified Program or a work based
  on the Program.
 .
    To "propagate" a work means to do anything with it that, without
  permission, would make you directly or secondarily liable for
  infringement under applicable copyright law, except executing it on a
  computer or modifying a private copy.  Propagation includes copying,
  distribution (with or without modification), making available to the
  public, and in some countries other activities as well.
 .
    To "convey" a work means any kind of propagation that enables other
  parties to make or receive copies.  Mere interaction with a user through
  a computer network, with no transfer of a copy, is not conveying.
 .
    An interactive user interface displays "Appropriate Legal Notices"
  to the extent that it includes a convenient and prominently visible
  feature that (1) displays an appropriate copyright notice, and (2)
  tells the user that there is no warranty for the work (except to the
  extent that warranties are provided), that licensees may convey the
  work under this License, and how to view a copy of this License.  If
  the interface presents a list of user commands or options, such as a
  menu, a prominent item in the list meets this criterion.
 .
    1. Source Code.
 .
    The "source code" for a work means the preferred form of the work
  for making modifications to it.  "Object code" means any non-source
  form of a work.
 .
    A "Standard Interface" means an interface that either is an official
  standard defined by a recognized standards body, or, in the case of
  interfaces specified for a particular programming language, one that
  is widely used among developers working in that language.
 .
    The "System Libraries" of an executable work include anything, other
  than the work as a whole, that (a) is included in the normal form of
  packaging a Major Component, but which is not part of that Major
  Component, and (b) serves only to enable use of the work with that
  Major Component, or to implement a Standard Interface for which an
  implementation is available to the public in source code form.  A
  "Major Component", in this context, means a major essential component
  (kernel, window system, and so on) of the specific operating system
  (if any) on which the executable work runs, or a compiler used to
  produce the work, or an object code interpreter used to run it.
 .
    The "Corresponding Source" for a work in object code form means all
  the source code needed to generate, install, and (for an executable
  work) run the object code and to modify the work, including scripts to
  control those activities.  However, it does not include the work's
  System Libraries, or general-purpose tools or generally available free
  programs which are used unmodified in performing those activities but
  which are not part of the work.  For example, Corresponding Source
  includes interface definition files associated with source files for
  the work, and the source code for shared libraries and dynamically
  linked subprograms that the work is specifically designed to require,
  such as by intimate data communication or control flow between those
  subprograms and other parts of the work.
 .
    The Corresponding Source need not include anything that users
  can regenerate automatically from other parts of the Corresponding
  Source.
 .
    The Corresponding Source for a work in source code form is that
  same work.
 .
    2. Basic Permissions.
 .
    All rights granted under this License are granted for the term of
  copyright on the Program, and are irrevocable provided the stated
  conditions are met.  This License explicitly affirms your unlimited
  permission to run the unmodified Program.  The output from running a
  covered work is covered by this License only if the output, given its
  content, constitutes a covered work.  This License acknowledges your
  rights of fair use or other equivalent, as provided by copyright law.
 .
    You may make, run and propagate covered works that you do not
  convey, without conditions so long as your license otherwise remains
  in force.  You may convey covered works to others for the sole purpose
  of having them make modifications exclusively for you, or provide you
  with facilities for running those works, provided that you comply with
  the terms of this License in conveying all material for which you do
  not control copyright.  Those thus making or running the covered works
  for you must do so exclusively on your behalf, under your direction
  and control, on terms that prohibit them from making any copies of
  your copyrighted material outside their relationship with you.
 .
    Conveying under any other circumstances is permitted solely under
  the conditions stated below.  Sublicensing is not allowed; section 10
  makes it unnecessary.
 .
    3. Protecting Users' Legal Rights From Anti-Circumvention Law.
 .
    No covered work shall be deemed part of an effective technological
  measure under any applicable law fulfilling obligations under article
  11 of the WIPO copyright treaty adopted on 20 December 1996, or
  similar laws prohibiting or restricting circumvention of such
  measures.
 .
    When you convey a covered work, you waive any legal power to forbid
  circumvention of technological measures to the extent such circumvention
  is effected by exercising rights under this License with respect to
  the covered work, and you disclaim any intention to limit operation or
  modification of the work as a means of enforcing, against the work's
  users, your or third parties' legal rights to forbid circumvention of
  technological measures.
 .
    4. Conveying Verbatim Copies.
 .
    You may convey verbatim copies of the Program's source code as you
  receive it, in any medium, provided that you conspicuously and
  appropriately publish on each copy an appropriate copyright notice;
  keep intact all notices stating that this License and any
  non-permissive terms added in accord with section 7 apply to the code;
  keep intact all notices of the absence of any warranty; and give all
  recipients a copy of this License along with the Program.
 .
    You may charge any price or no price for each copy that you convey,
  and you may offer support or warranty protection for a fee.
 .
    5. Conveying Modified Source Versions.
 .
    You may convey a work based on the Program, or the modifications to
  produce it from the Program, in the form of source code under the
  terms of section 4, provided that you also meet all of these conditions:
 .
      a) The work must carry prominent notices stating that you modified
      it, and giving a relevant date.
 .
      b) The work must carry prominent notices stating that it is
      released under this License and any conditions added under section
      7.  This requirement modifies the requirement in section 4 to
      "keep intact all notices".
 .
      c) You must license the entire work, as a whole, under this
      License to anyone who comes into possession of a copy.  This
      License will therefore apply, along with any applicable section 7
      additional terms, to the whole of the work, and all its parts,
      regardless of how they are packaged.  This License gives no
      permission to license the work in any other way, but it does not
      invalidate such permission if you have separately received it.
 .
      d) If the work has interactive user interfaces, each must display
      Appropriate Legal Notices; however, if the Program has interactive
      interfaces that do not display Appropriate Legal Notices, your
      work need not make them do so.
 .
    A compilation of a covered work with other separate and independent
  works, which are not by their nature extensions of the covered work,
  and which are not combined with it such as to form a larger program,
  in or on a volume of a storage or distribution medium, is called an
  "aggregate" if the compilation and its resulting copyright are not
  used to limit the access or legal rights of the compilation's users
  beyond what the individual works permit.  Inclusion of a covered work
  in an aggregate does not cause this License to apply to the other
  parts of the aggregate.
 .
    6. Conveying Non-Source Forms.
 .
    You may convey a covered work in object code form under the terms
  of sections 4 and 5, provided that you also convey the
  machine-readable Corresponding Source under the terms of this License,
  in one of these ways:
 .
      a) Convey the object code in, or embodied in, a physical product
      (including a physical distribution medium), accompanied by the
      Corresponding Source fixed on a durable physical medium
      customarily used for software interchange.
 .
      b) Convey the object code in, or embodied in, a physical product
      (including a physical distribution medium), accompanied by a
      written offer, valid for at least three years and valid for as
      long as you offer spare parts or customer support for that product
      model, to give anyone who possesses the object code either (1) a
      copy of the Corresponding Source for all the software in the
      product that is covered by this License, on a durable physical
      medium customarily used for software interchange, for a price no
      more than your reasonable cost of physically performing this
      conveying of source, or (2) access to copy the
      Corresponding Source from a network server at no charge.
 .
      c) Convey individual copies of the object code with a copy of the
      written offer to provide the Corresponding Source.  This
      alternative is allowed only occasionally and noncommercially, and
      only if you received the object code with such an offer, in accord
      with subsection 6b.
 .
      d) Convey the object code by offering access from a designated
      place (gratis or for a charge), and offer equivalent access to the
      Corresponding Source in the same way through the same place at no
      further charge.  You need not require recipients to copy the
      Corresponding Source along with the object code.  If the place to
      copy the object code is a network server, the Corresponding Source
      may be on a different server (operated by you or a third party)
      that supports equivalent copying facilities, provided you maintain
      clear directions next to the object code saying where to find the
      Corresponding Source.  Regardless of what server hosts the
      Corresponding Source, you remain obligated to ensure that it is
      available for as long as needed to satisfy these requirements.
 .
      e) Convey the object code using peer-to-peer transmission, provided
      you inform other peers where the object code and Corresponding
      Source of the work are being offered to the general public at no
      charge under subsection 6d.
 .
    A separable portion of the object code, whose source code is excluded
  from the Corresponding Source as a System Library, need not be
  included in conveying the object code work.
 .
    A "User Product" is either (1) a "consumer product", which means any
  tangible personal property which is normally used for personal, family,
  or household purposes, or (2) anything designed or sold for incorporation
  into a dwelling.  In determining whether a product is a consumer product,
  doubtful cases shall be resolved in favor of coverage.  For a particular
  product received by a particular user, "normally used" refers to a
  typical or common use of that class of product, regardless of the status
  of the particular user or of the way in which the particular user
  actually uses, or expects or is expected to use, the product.  A product
  is a consumer product regardless of whether the product has substantial
  commercial, industrial or non-consumer uses, unless such uses represent
  the only significant mode of use of the product.
 .
    "Installation Information" for a User Product means any methods,
  procedures, authorization keys, or other information required to install
  and execute modified versions of a covered work in that User Product from
  a modified version of its Corresponding Source.  The information must
  suffice to ensure that the continued functioning of the modified object
  code is in no case prevented or interfered with solely because
  modification has been made.
 .
    If you convey an object code work under this section in, or with, or
  specifically for use in, a User Product, and the conveying occurs as
  part of a transaction in which the right of possession and use of the
  User Product is transferred to the recipient in perpetuity or for a
  fixed term (regardless of how the transaction is characterized), the
  Corresponding Source conveyed under this section must be accompanied
  by the Installation Information.  But this requirement does not apply
  if neither you nor any third party retains the ability to install
  modified object code on the User Product (for example, the work has
  been installed in ROM).
 .
    The requirement to provide Installation Information does not include a
  requirement to continue to provide support service, warranty, or updates
  for a work that has been modified or installed by the recipient, or for
  the User Product in which it has been modified or installed.  Access to a
  network may be denied when the modification itself materially and
  adversely affects the operation of the network or violates the rules and
  protocols for communication across the network.
 .
    Corresponding Source conveyed, and Installation Information provided,
  in accord with this section must be in a format that is publicly
  documented (and with an implementation available to the public in
  source code form), and must require no special password or key for
  unpacking, reading or copying.
 .
    7. Additional Terms.
 .
    "Additional permissions" are terms that supplement the terms of this
  License by making exceptions from one or more of its conditions.
  Additional permissions that are applicable to the entire Program shall
  be treated as though they were included in this License, to the extent
  that they are valid under applicable law.  If additional permissions
  apply only to part of the Program, that part may be used separately
  under those permissions, but the entire Program remains governed by
  this License without regard to the additional permissions.
 .
    When you convey a copy of a covered work, you may at your option
  remove any additional permissions from that copy, or from any part of
  it.  (Additional permissions may be written to require their own
  removal in certain cases when you modify the work.)  You may place
  additional permissions on material, added by you to a covered work,
  for which you have or can give appropriate copyright permission.
 .
    Notwithstanding any other provision of this License, for material you
  add to a covered work, you may (if authorized by the copyright holders of
  that material) supplement the terms of this License with terms:
 .
      a) Disclaiming warranty or limiting liability differently from the
      terms of sections 15 and 16 of this License; or
 .
      b) Requiring preservation of specified reasonable legal notices or
      author attributions in that material or in the Appropriate Legal
      Notices displayed by works containing it; or
 .
      c) Prohibiting misrepresentation of the origin of that material, or
      requiring that modified versions of such material be marked in
      reasonable ways as different from the original version; or
 .
      d) Limiting the use for publicity purposes of names of licensors or
      authors of the material; or
 .
      e) Declining to grant rights under trademark law for use of some
      trade names, trademarks, or service marks; or
 .
      f) Requiring indemnification of licensors and authors of that
      material by anyone who conveys the material (or modified versions of
      it) with contractual assumptions of liability to the recipient, for
      any liability that these contractual assumptions directly impose on
      those licensors and authors.
 .
    All other non-permissive additional terms are considered "further
  restrictions" within the meaning of section 10.  If the Program as you
  received it, or any part of it, contains a notice stating that it is
  governed by this License along with a term that is a further
  restriction, you may remove that term.  If a license document contains
  a further restriction but permits relicensing or conveying under this
  License, you may add to a covered work material governed by the terms
  of that license document, provided that the further restriction does
  not survive such relicensing or conveying.
 .
    If you add terms to a covered work in accord with this section, you
  must place, in the relevant source files, a statement of the
  additional terms that apply to those files, or a notice indicating
  where to find the applicable terms.
 .
    Additional terms, permissive or non-permissive, may be stated in the
  form of a separately written license, or stated as exceptions;
  the above requirements apply either way.
 .
    8. Termination.
 .
    You may not propagate or modify a covered work except as expressly
  provided under this License.  Any attempt otherwise to propagate or
  modify it is void, and will automatically terminate your rights under
  this License (including any patent licenses granted under the third
  paragraph of section 11).
 .
    However, if you cease all violation of this License, then your
  license from a particular copyright holder is reinstated (a)
  provisionally, unless and until the copyright holder explicitly and
  finally terminates your license, and (b) permanently, if the copyright
  holder fails to notify you of the violation by some reasonable means
  prior to 60 days after the cessation.
 .
    Moreover, your license from a particular copyright holder is
  reinstated permanently if the copyright holder notifies you of the
  violation by some reasonable means, this is the first time you have
  received notice of violation of this License (for any work) from that
  copyright holder, and you cure the violation prior to 30 days after
  your receipt of the notice.
 .
    Termination of your rights under this section does not terminate the
  licenses of parties who have received copies or rights from you under
  this License.  If your rights have been terminated and not permanently
  reinstated, you do not qualify to receive new licenses for the same
  material under section 10.
 .
    9. Acceptance Not Required for Having Copies.
 .
    You are not required to accept this License in order to receive or
  run a copy of the Program.  Ancillary propagation of a covered work
  occurring solely as a consequence of using peer-to-peer transmission
  to receive a copy likewise does not require acceptance.  However,
  nothing other than this License grants you permission to propagate or
  modify any covered work.  These actions infringe copyright if you do
  not accept this License.  Therefore, by modifying or propagating a
  covered work, you indicate your acceptance of this License to do so.
 .
    10. Automatic Licensing of Downstream Recipients.
 .
    Each time you convey a covered work, the recipient automatically
  receives a license from the original licensors, to run, modify and
  propagate that work, subject to this License.  You are not responsible
  for enforcing compliance by third parties with this License.
 .
    An "entity transaction" is a transaction transferring control of an
  organization, or substantially all assets of one, or subdividing an
  organization, or merging organizations.  If propagation of a covered
  work results from an entity transaction, each party to that
  transaction who receives a copy of the work also receives whatever
  licenses to the work the party's predecessor in interest had or could
  give under the previous paragraph, plus a right to possession of the
  Corresponding Source of the work from the predecessor in interest, if
  the predecessor has it or can get it with reasonable efforts.
 .
    You may not impose any further restrictions on the exercise of the
  rights granted or affirmed under this License.  For example, you may
  not impose a license fee, royalty, or other charge for exercise of
  rights granted under this License, and you may not initiate litigation
  (including a cross-claim or counterclaim in a lawsuit) alleging that
  any patent claim is infringed by making, using, selling, offering for
  sale, or importing the Program or any portion of it.
 .
    11. Patents.
 .
    A "contributor" is a copyright holder who authorizes use under this
  License of the Program or a work on which the Program is based.  The
  work thus licensed is called the contributor's "contributor version".
 .
    A contributor's "essential patent claims" are all patent claims
  owned or controlled by the contributor, whether already acquired or
  hereafter acquired, that would be infringed by some manner, permitted
  by this License, of making, using, or selling its contributor version,
  but do not include claims that would be infringed only as a
  consequence of further modification of the contributor version.  For
  purposes of this definition, "control" includes the right to grant
  patent sublicenses in a manner consistent with the requirements of
  this License.
 .
    Each contributor grants you a non-exclusive, worldwide, royalty-free
  patent license under the contributor's essential patent claims, to
  make, use, sell, offer for sale, import and otherwise run, modify and
  propagate the contents of its contributor version.
 .
    In the following three paragraphs, a "patent license" is any express
  agreement or commitment, however denominated, not to enforce a patent
  (such as an express permission to practice a patent or covenant not to
  sue for patent infringement).  To "grant" such a patent license to a
  party means to make such an agreement or commitment not to enforce a
  patent against the party.
 .
    If you convey a covered work, knowingly relying on a patent license,
  and the Corresponding Source of the work is not available for anyone
  to copy, free of charge and under the terms of this License, through a
  publicly available network server or other readily accessible means,
  then you must either (1) cause the Corresponding Source to be so
  available, or (2) arrange to deprive yourself of the benefit of the
  patent license for this particular work, or (3) arrange, in a manner
  consistent with the requirements of this License, to extend the patent
  license to downstream recipients.  "Knowingly relying" means you have
  actual knowledge that, but for the patent license, your conveying the
  covered work in a country, or your recipient's use of the covered work
  in a country, would infringe one or more identifiable patents in that
  country that you have reason to believe are valid.
 .
    If, pursuant to or in connection with a single transaction or
  arrangement, you convey, or propagate by procuring conveyance of, a
  covered work, and grant a patent license to some of the parties
  receiving the covered work authorizing them to use, propagate, modify
  or convey a specific copy of the covered work, then the patent license
  you grant is automatically extended to all recipients of the covered
  work and works based on it.
 .
    A patent license is "discriminatory" if it does not include within
  the scope of its coverage, prohibits the exercise of, or is
  conditioned on the non-exercise of one or more of the rights that are
  specifically granted under this License.  You may not convey a covered
  work if you are a party to an arrangement with a third party that is
  in the business of distributing software, under which you make payment
  to the third party based on the extent of your activity of conveying
  the work, and under which the third party grants, to any of the
  parties who would receive the covered work from you, a discriminatory
  patent license (a) in connection with copies of the covered work
  conveyed by you (or copies made from those copies), or (b) primarily
  for and in connection with specific products or compilations that
  contain the covered work, unless you entered into that arrangement,
  or that patent license was granted, prior to 28 March 2007.
 .
    Nothing in this License shall be construed as excluding or limiting
  any implied license or other defenses to infringement that may
  otherwise be available to you under applicable patent law.
 .
    12. No Surrender of Others' Freedom.
 .
    If conditions are imposed on you (whether by court order, agreement or
  otherwise) that contradict the conditions of this License, they do not
  excuse you from the conditions of this License.  If you cannot convey a
  covered work so as to satisfy simultaneously your obligations under this
  License and any other pertinent obligations, then as a consequence you may
  not convey it at all.  For example, if you agree to terms that obligate you
  to collect a royalty for further conveying from those to whom you convey
  the Program, the only way you could satisfy both those terms and this
  License would be to refrain entirely from conveying the Program.
 .
    13. Remote Network Interaction; Use with the GNU General Public License.
 .
    Notwithstanding any other provision of this License, if you modify the
  Program, your modified version must prominently offer all users
  interacting with it remotely through a computer network (if your version
  supports such interaction) an opportunity to receive the Corresponding
  Source of your version by providing access to the Corresponding Source
  from a network server at no charge, through some standard or customary
  means of facilitating copying of software.  This Corresponding Source
  shall include the Corresponding Source for any work covered by version 3
  of the GNU General Public License that is incorporated pursuant to the
  following paragraph.
 .
    Notwithstanding any other provision of this License, you have
  permission to link or combine any covered work with a work licensed
  under version 3 of the GNU General Public License into a single
  combined work, and to convey the resulting work.  The terms of this
  License will continue to apply to the part which is the covered work,
  but the work with which it is combined will remain governed by version
  3 of the GNU General Public License.
 .
    14. Revised Versions of this License.
 .
    The Free Software Foundation may publish revised and/or new versions of
  the GNU Affero General Public License from time to time.  Such new versions
  will be similar in spirit to the present version, but may differ in detail to
  address new problems or concerns.
 .
    Each version is given a distinguishing version number.  If the
  Program specifies that a certain numbered version of the GNU Affero General
  Public License "or any later version" applies to it, you have the
  option of following the terms and conditions either of that numbered
  version or of any later version published by the Free Software
  Foundation.  If the Program does not specify a version number of the
  GNU Affero General Public License, you may choose any version ever published
  by the Free Software Foundation.
 .
    If the Program specifies that a proxy can decide which future
  versions of the GNU Affero General Public License can be used, that proxy's
  public statement of acceptance of a version permanently authorizes you
  to choose that version for the Program.
 .
    Later license versions may give you additional or different
  permissions.  However, no additional obligations are imposed on any
  author or copyright holder as a result of your choosing to follow a
  later version.
 .
    15. Disclaimer of Warranty.
 .
    THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
  APPLICABLE LAW.  EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
  HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
  OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
  THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
  PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
  IS WITH YOU.  SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
  ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
 .
    16. Limitation of Liability.
 .
    IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
  WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
  THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
  GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
  USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
  DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
  PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
  EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
  SUCH DAMAGES.
 .
    17. Interpretation of Sections 15 and 16.
 .
    If the disclaimer of warranty and limitation of liability provided
  above cannot be given local legal effect according to their terms,
  reviewing courts shall apply local law that most closely approximates
  an absolute waiver of all civil liability in connection with the
  Program, unless a warranty or assumption of liability accompanies a
  copy of the Program in return for a fee.
 .
                       END OF TERMS AND CONDITIONS
 .
              How to Apply These Terms to Your New Programs
 .
    If you develop a new program, and you want it to be of the greatest
  possible use to the public, the best way to achieve this is to make it
  free software which everyone can redistribute and change under these terms.
 .
    To do so, attach the following notices to the program.  It is safest
  to attach them to the start of each source file to most effectively
  state the exclusion of warranty; and each file should have at least
  the "copyright" line and a pointer to where the full notice is found.
 .
      <one line to give the program's name and a brief idea of what it does.>
      Copyright (C) <year>  <name of author>
 .
      This program is free software: you can redistribute it and/or modify
      it under the terms of the GNU Affero General Public License as published by
      the Free Software Foundation, either version 3 of the License, or
      (at your option) any later version.
 .
      This program is distributed in the hope that it will be useful,
      but WITHOUT ANY WARRANTY; without even the implied warranty of
      MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
      GNU Affero General Public License for more details.
 .
      You should have received a copy of the GNU Affero General Public License
      along with this program.  If not, see <http://www.gnu.org/licenses/>.
 .
  Also add information on how to contact you by electronic and paper mail.
 .
    If your software can interact with users remotely through a computer
  network, you should also make sure that it provides a way for users to
  get its source.  For example, if your program is a web application, its
  interface could display a "Source" link that leads users to an archive
  of the code.  There are many ways you could offer source, and different
  solutions will be better for different programs; see section 13 for the
  specific requirements.
 .
    You should also get your employer (if you work as a programmer) or school,
  if any, to sign a "copyright disclaimer" for the program, if necessary.
  For more information on this, and how to apply and follow the GNU AGPL, see
  <http://www.gnu.org/licenses/>.

path: debian/copyright


code:
Document: git-annex
Title: git-annex documentation
Author: Joey Hess
Abstract: All the documentation from git-annex's website.
Section: File Management

Format: HTML
Index: /usr/share/doc/git-annex/html/index.html
Files: /usr/share/doc/git-annex/html/*.html

path: debian/doc-base


code:
?package(git-annex):needs="X11" section="Applications/Network/File Transfer" \
	title="git-annex assistant" command="git-annex webapp"

path: debian/menu


code:
#!/usr/bin/make -f

# Avoid using cabal, as it writes to $HOME
export CABAL=./Setup

# Do use the changelog's version number, rather than making one up.
export RELEASE_BUILD=1

%:
	dh $@

# Not intended for use by anyone except the author.
announcedir:
	@echo ${HOME}/src/git-annex/doc/news

path: debian/rules


code:
#!/bin/sh
testdir="$(mktemp -d)"
cd "$testdir"
exec git-annex test

path: debian/tests/basics


code:
Tests: basics
Depends: @, git, rsync, gnupg
Restrictions: allow-stderr

path: debian/tests/control


code:
git-annex is now available for Android. This includes the
[[git-annex assistant|/assistant]], for easy syncing between your Android
and other devices. You do not need to root your Android to use git-annex.

[[Android installation instructions|/install/android]]

When you run the git-annex Android app, two windows will open. The first is
a terminal window, and the second is a web browser showing the git-annex
webapp.

[[!img apps.png alt="two windows"]]

[[!toc ]]

## closing and reopening the webapp

The webapp does not need to be left open after you've set up your
repository. As long as the terminal window is left open, git-annex will
remain running and sync your files. To re-open the webapp after closing it,
use the [[!img newwindow.png alt="New Window"]] icon in the terminal window.

## starting git-annex

The app is not currently automatically started on boot, so you will need to
manually open it to keep your files in sync. You do not need to leave the
app running all the time, though. It will sync back up automatically when
started.

## stopping git-annex

Simply close the terminal window to stop git-annex from running.

## using the command line

[[!img terminal.png alt="Android terminal"]]

If you prefer to use `git-annex` at the command line, you can do so using the
terminal. A fairly full set of tools is provided, including `git`, `ssh`,
`rsync`, and `gpg`.

To prevent the webapp from being automatically started
when a terminal window opens, go into the terminal preferences, to "Inital
Command", and clear out the default `git annex webapp` setting.

Or, if you'd like to run the assistant automatically, but not open the
webapp, change the "Initial Command" to: `git annex assistant --autostart`

## using from adb shell

To set up the git-annex environment from within `adb shell`, run:
`/data/data/ga.androidterm/runshell`

This will launch a shell that has git-annex, git, etc in PATH.


code:
[[!comment format=mdwn
 username="http://afoolishmanifesto.com/"
 nickname="frioux"
 subject="SSH Keys?"
 date="2013-07-17T16:50:46Z"
 content="""
Is there a way I can use an SSH Key to connect to a remote server?  What would be really cool, though maybe not feasible, would be to use connectbot as an ssh-agent.
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 ip="4.154.4.90"
 subject="comment 20"
 date="2013-07-17T19:06:31Z"
 content="""
@frioux the webapp has a \"ssh server\" option that will set up a ssh key and use it for passwordless data transfer to a ssh server.

The openssh included in the git-annex app fully supports everything you can usually do with ssh keys, so you can also set this up by hand.
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 ip="4.154.0.21"
 subject="comment 29"
 date="2013-07-30T17:45:27Z"
 content="""
If you are experiencing a problem using git-annex on Android, please examine the list of [[bugs]] and add a new, detailed bug report if no-one has reported the problem. If you are not sure if you have a bug, or need help in filing a good bug report, ask for help in the [[forum]].

I have moved to [[oldcomments]] a lot of old comments about problems that may be fixed or
not (hard to tell without a bug report!) " This page cannot
scale to handle every bug report that someone wants to paste into it.
"""]]


code:
[[!comment format=mdwn
 username="http://mebus.myopenid.com/"
 ip="2a01:198:3eb:0:4a5b:39ff:fea4:55b3"
 subject="comment 5"
 date="2013-10-19T18:05:52Z"
 content="""
Hallo,

how can I use the app with public/private keys for SSH. Where can I add them?

Thanks

Mebus

"""]]


code:
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawk2BFMjJW081uX4aJdhStmSFPBUGzL92ZU"
 nickname="Frédéric"
 subject="where do I put the SSH keys on Android"
 date="2014-02-26T20:26:38Z"
 content="""
@mebus :
You can put your SSH keys here :

/sdcard/git-annex.home/.ssh/id_rsa

/sdcard/git-annex.home/.ssh/id_rsa.pub
"""]]


code:
If one of these comments is yours, and you are still experiencing the
problem, please file a proper [[bug_report|bugs]]. --[[Joey]]


code:
[[!comment format=mdwn
 username="http://yarikoptic.myopenid.com/"
 nickname="site-myopenid"
 subject="comment 10"
 date="2013-05-24T03:11:50Z"
 content="""
>you said before the error was \"Read-only file system\". Now you're saying it's \"Cross-device link\". I'm slightly confused.

;-)  Sorry for confusion, here are the details:

\"Read-only file system\" -- that error appeared when I started \"stock git annex\", i.e. from running /data/data/ga.androidterm/lib/lib.start.so .
Since you have suggested that it might be coming from hard linking command, I have ran that one manually, and that is when I got \"Cross-device link\" error, which suggests that hard linking is not the one at fault here.

I will try fresh build now
Cheers,
"""]]


code:
[[!comment format=mdwn
 username="http://yarikoptic.myopenid.com/"
 nickname="site-myopenid"
 subject="fresh build"
 date="2013-05-24T03:21:29Z"
 content="""
With fresh build got:

u0_a39@android:/ $ git annex webapp
/system/bin/sh: git: not found

the PATH is /sbin:/system/bin:/system/xbin

where should git (and ga) reside now ? (/data somehow is not accessible now to u0_a39)
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 nickname="joey"
 subject="comment 12"
 date="2013-05-24T03:26:33Z"
 content="""
You should be able to run /data/data/ga.androidterm/runshell even if you cannot ls /data. This adds /data/data/ga.androidterm/bin to PATH

However, the shell that the app starts is started by runshell anyway, so I don't understand how this could happen.
"""]]


code:
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawkwjBDXkP9HAQKhjTgThGOxUa1B99y_WRA"
 nickname="Franck"
 subject="Still problems with my old N1/CM7"
 date="2013-05-24T06:01:18Z"
 content="""
Hi, thank you for addressing this issue! I installed the new release but now it fails in another way: the message is just \"In mgmain NJI_OnLoad\" then the terminal says that the session is closed.
"""]]


code:
[[!comment format=mdwn
 username="http://yarikoptic.myopenid.com/"
 nickname="site-myopenid"
 subject="It starts after uninstall/install"
 date="2013-05-24T23:29:52Z"
 content="""
Hi Joey -- there is success here... previous installation was \"updated\" by installing the new package without uninstalling previous one, and that apparently didn't work correctly (I didn't even have bin/ directory you mentioned).  So I have removed previous installation and reinstalled it again -- it starts now!  Thanks ;)
"""]]


code:
[[!comment format=mdwn
 username="http://yarikoptic.myopenid.com/"
 nickname="site-myopenid"
 subject="asking for ssh password in the terminal (not in web ui)"
 date="2013-05-24T23:49:40Z"
 content="""
not sure if that is a known issue:  whenever \"remote server\" is added, password needs to be typed back in the original terminal... is a bit challenging to do on android and not straightforward user-wise
"""]]


code:
[[!comment format=mdwn
 username="http://yarikoptic.myopenid.com/"
 nickname="site-myopenid"
 subject="Few other issues"
 date="2013-05-25T15:35:46Z"
 content="""
Hi again.

talking about 4.20130523-gcfe07a2 version:

- because working in the terminal to interact with git-annex probably should not be a common case on Android, may be it is worth making default type of new added repository to become a full backup?  I have initiated a new one, attached a remote one, it said \"synced\" but all the files were just containing symlinks and were not usable.  I had to switch to \"full backup\" (or whatever that name) to finally get directory synced

- log file might grow too large simply because of containing numerous entries for attempting connect remote repository while offline, e.g.

Please make sure you have the correct access rights
and the repository exists.
ssh: Could not resolve hostname onerussian.com: No address associated with hostname
fatal: Could not read from remote repository.

IMHO those should not be there at all, e.g. if it is known that ATM there is no network connectivity

- In addition to two existing repositories (1 local /sdcard/annex, which is also avail at/storage/sdcard0/annex + 1 remote) I have added one more local (and said to keep it in sync with original local).  But it didn't work -- it \"Synced with onerussian.com_annex but not with Annex\" and claimed that the /external/extSdCard/Annex doesn't exist, although it is there (and with .git generated etc).  When I restarted the deamon I got into a \"new\" Repository: /storage/extSdCard/Annex which also listed the 1st local but with \"Failed to sync with localhost\" message -- no remote one listed.  Whenever I try to \"Switch repository\" to /sdcard/annex (the original local) -- it starts loading a new page but gets stuck right there.  The only way to revive webui is to go back to Dashboard.  Log there says (retyping from the screen so typos might be there):

error: cannot run git-receive-pack '/storage/sdcard0/annex': No such file or directory
fatal: unable to fork

"""]]


code:
[[!comment format=mdwn
 username="http://yarikoptic.myopenid.com/"
 nickname="site-myopenid"
 subject="comment 17"
 date="2013-05-29T02:43:29Z"
 content="""
joey -- any additional information could I provide to troubleshoot the issue?  original repository seems to sync ok, but I can't \"administer\" it if I can't even switch to it...
"""]]


code:
[[!comment format=mdwn
 username="http://aap.liquidid.net/"
 nickname="AAP"
 subject="comment 18"
 date="2013-05-30T11:23:58Z"
 content="""
I too get the 'link busybox: Read-only file system' message. Here is my phone info:

Phone: Samsung Galaxy Y GT-S5360 (rooted)
Android: 2.3.6 Gingerbread
BusyBox path: /system/xbin/

Androids own terminal seems not to understand the d argument (-ld: No such file or directory) but over ssh 'ls -ld /data/data/ga.androidterm' returns

         drwxr-x--x    1 app_97   app_97           0 May 30 12:57 /data/data/ga.androidterm/
"""]]


code:
[[!comment format=mdwn
 username="http://yarikoptic.myopenid.com/"
 nickname="site-myopenid"
 subject="Does it require the device to be rooted?"
 date="2013-05-16T20:55:45Z"
 content="""
Following your news on kickstarter downloaded the .apk, and installed it.  Upn start I just got a terminal window with

  link busybox: Read-only file system

  [Terminal session finished]

That is on Galaxy Note

"""]]


code:
[[!comment format=mdwn
 username="http://afoolishmanifesto.com/"
 nickname="frioux"
 subject="SSH Keys - 2"
 date="2013-07-17T22:56:37Z"
 content="""
@joey should I be using the nightlies to see that?  Under \"Adding a remote server using ssh\" I only see  Host name, user name, directory, and port.  Will it only be an option after I type in a password?
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 ip="4.154.6.48"
 subject="comment 22"
 date="2013-07-17T23:25:21Z"
 content="""
@frioux it will automatically generate a new ssh key and configure the server to use it, once you submit the form and enter the password to let it into the server.
"""]]


code:
[[!comment format=mdwn
 username="http://afoolishmanifesto.com/"
 nickname="frioux"
 subject="comment 23"
 date="2013-07-18T02:01:28Z"
 content="""
@joey: ok, I got it to connect and it indeed sent over a key etc.  For some reason now though git-annex (on android) \"crashes\" shortly after starting.  To be clear, the web app says that the program crashed, the console is still there.  I suspect that it may have something to do with my largish remote repo and the time required to sync just the metadata, but I can't tell.  Any ideas what I should do next?  (Note that I *did* change it to manual mode because my phone doesn't have 30G of storage :)
"""]]


code:
[[!comment format=mdwn
 username="http://afoolishmanifesto.com/"
 nickname="frioux"
 subject="comment 24"
 date="2013-07-18T11:35:06Z"
 content="""
ok, it eventually got the details from the remote server, but now I'm getting some other oddities.  here is some of my log that shows what I am running into

Watcher crashed: addWatch: does not exist (No such file or directory) [2013-07-18 06:22:46 CDT] Watcher: warning Watcher crashed: addWatch: does not exist (No such file or directory) (scanning...) [2013-07-18 06:23:19 CDT] Watcher: Performing startup scan Watcher crashed: addWatch: does not exist (No such file or directory) [2013-07-18 06:24:28 CDT] Watcher: warning Watcher crashed: addWatch: does not exist (No such file or directory) (scanning...) [2013-07-18 06:24:31 CDT] Watcher: Performing startup scan Watcher crashed: addWatch: does not exist (No such file or directory) [2013-07-18 06:25:44 CDT] Watcher: warning Watcher crashed: addWatch: does not exist (No such file or directory)
"""]]


code:
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawnRfQArYOmDd7r2DC7DkIJFOQgqXCVcAeU"
 nickname="Frew"
 subject="comment 25"
 date="2013-07-18T13:14:46Z"
 content="""
frioux here (something messed up with myopenid or something)

So I deleted the repo on my phone (via the CLI since the web app seemed hung) and recreated it; this time making sure that I set things to manual mode ASAP.  It didn't have the problem it was having before, but now what seems to have happened is that it fetches from the remote, commits to the local repo, and then immediately fetches and commits again.  It looks like it's about a 4s repeat loop.  Any ideas what I should do next?
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 ip="4.154.0.140"
 subject="comment 26"
 date="2013-07-18T17:07:27Z"
 content="""
@Frew, you should file bug reports when you have a bug.

One problem you mentioned had already had a bug report filed by someone
else:
<http://git-annex.branchable.com/bugs/Watcher_crashed:_addWatch:_does_not_exist/> So you can post your details there.
"""]]


code:
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawnaH44G3QbxBAYyDwy0PbvL0ls60XoaR3Y"
 nickname="Nigel"
 subject="Watcher crashed in Android on /storage/sdcard1 - bug?"
 date="2013-07-29T11:50:46Z"
 content="""
In webapp UI, added on first install, the location for repository: /storage/sdcard1

!warning

Watcher crashed: addWatch:

permission denied (Permission denied)

[Restart Thread]

:Performing startup scan

In terminal Window 1:

nex webapp                                         <

  Detected a crippled filesystem.

  Enabling direct mode.

  Detected a filesystem without fifo support.

  Disabling ssh connection caching.

Android 4.1.1 Huawei Y300 Annex.apk v1.0.52 version 4.20130723
"""]]


code:
[[!comment format=mdwn
 username="Jonathan"
 ip="63.131.117.194"
 subject="link busybox: Read-only file system"
 date="2013-07-29T20:08:12Z"
 content="""
Phone: HTC EVO 3d 4g
Model Number: pg86100
Android Version: 4.0.3
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 nickname="joey"
 subject="comment 2"
 date="2013-05-17T22:28:34Z"
 content="""
The Android app works on many non-rooted Android systems.

The \"link busybox: Read-only file system\" means that `/data/data/ga.androidterm/lib/lib.busybox.so` cannot be hard linked to `/data/data/ga.androidterm/busybox`. That's not normal. I'd appreciate if you could provide more information on your Android device, like Android version and model number.
"""]]


code:
[[!comment format=mdwn
 username="http://yarikoptic.myopenid.com/"
 nickname="site-myopenid"
 subject="Follow-up information on my system"
 date="2013-05-18T01:23:28Z"
 content="""
Sorry for the delay:  my android is stock Samsung-tuned Jelly beans.
Android 4.1.2
Baseband version N7000XXLSO

not sure if that would be of any use :-/  nothing in the logs (aLogcat) if I filter by annex -- should there any debug output? what should be a key to search by?

"""]]


code:
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawnu1NYw8UF-NoDbKu8YKVGxi8FoZLH7JPs"
 nickname="Chris"
 subject="Not starting browser on Nexus 7, Android 4.2.2"
 date="2013-05-19T14:04:28Z"
 content="""
I just tried to run this on my Nexus 7 which has Android 4.2.2, and I received the following: <http://hodapple.com/files/Screenshot_2013-05-19-09-49-53.png> <http://hodapple.com/files/git-annex-error.txt>

In spite of that, though, the URL provided still worked.
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 nickname="joey"
 subject="comment 5"
 date="2013-05-19T19:46:14Z"
 content="""
@Chris, that is a known bug: [[bugs/Android_app_permission_denial_on_startup]]
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 nickname="joey"
 subject="comment 6"
 date="2013-05-19T20:06:56Z"
 content="""
@yarikoptic, there is a process you can perform that will help me determine what's going on.

You should be able to get the git-annex app to let you into a shell. You can do this by starting the app, and then going into its configuration menu, to Preferences, selecting \"Command Line\", and changing it to run \"/system/bin/sh\"

Then when you open a new window in the git-annex app, you'll be at a shell prompt. From there, you can run:

ls -ld /data/data/ga.androidterm

I'm interested to know a) whether the directory exists and b) what permissions and owner it has. On my tablet, I get back \"drwxr-x--x app_39 app_39\" .. and if I run `id` in the shell, it tells me it's running as `app_39`.

My guess is the directory probably does exist, but cannot be written to by the app. If you're able to verify that, the next step will be to investigate if there is some other directory that the app can write to. It needs to be able to write to someplace that is not on the `/sdcard` to install itself.
"""]]


code:
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawkwjBDXkP9HAQKhjTgThGOxUa1B99y_WRA"
 nickname="Franck"
 subject="Link issue"
 date="2013-05-22T12:01:38Z"
 content="""
Hi, I have exactly the same problem with the link that fails on my phone. However, I checked the permissions and they are as you describe on your tablet (except for the app number). At the same time, everything is fine on my tablet... The phone runs an old Cyanogenmod 7.2.0 (Android 2.3.7) while the tablet is a more recent Asus TF700T (Android 4.1.1). Let me know if you want me to run tests.
"""]]


code:
[[!comment format=mdwn
 username="http://yarikoptic.myopenid.com/"
 nickname="site-myopenid"
 subject="why ln failed"
 date="2013-05-23T13:27:39Z"
 content="""
Finally got to check it out:  so indeed hardlinking fails but not because of permissions but \"link failed Cross-device link\"  that lib is -> /mnt/asec/ga.androidterm-1/lib  which resides on a different partition (vfat, /dev/block/dm-2, ro) from /data (ext4, /dev/block/mmcblk0p10)
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 nickname="joey"
 subject="comment 9"
 date="2013-05-23T18:44:46Z"
 content="""
@yarikoptic you said before the error was \"Read-only file system\". Now you're saying it's \"Cross-device link\". I'm slightly confused.

I've reworked the android app to not need any hard links. Try the current autobuild: <http://downloads.kitenet.net/git-annex/autobuild/android/git-annex.apk>
"""]]


code:
The git-annex assistant creates a synchronised folder on each of your
OSX and Linux computers, Android devices, removable drives, NAS appliances,
and cloud services. The contents of the folder are the same everywhere.
It's very easy to use, and has all the power of git and git-annex.

## installation

The git-annex assistant comes as part of git-annex.
See [[install]] to get it installed.

See the [[release_notes]] for an overview of the status, and upgrade
instructions.

## intro screencast

[[!inline feeds=no template=bare pages=videos/git-annex_assistant_lan]]

## documentation

* [[Basic usage|quickstart]]
* [[Android documentation|/Android]]
* Want to make two nearby computers share the same synchronised folder?
  Follow the [[local_pairing_walkthrough]].
* Or perhaps you want to share files between computers in different
  locations, like home and work?
  Follow the [[remote_sharing_walkthrough]].
* Want to share a synchronised folder with a friend?
  Follow the [[share_with_a_friend_walkthrough]].
* Want to archive data to a drive or the cloud?
  Follow the [[archival_walkthrough]].

## colophon

The git-annex assistant was [crowd funded on
Kickstarter](http://www.kickstarter.com/projects/joeyh/git-annex-assistant-like-dropbox-but-with-your-own/).
[[/Thanks]] to all my backers.

I blog about my work on git-annex and the assistant on a daily basis
in [[this_blog|/devblog]]. Follow along!

See also: The [[design|/design/assistant]] pages.


code:
Normally, the git-annex assistant makes your files be available
wherever you use it, and so a copy of each file is stored in each repository.
That's perfect for files you're using right now, but what about files you're
not using any more?

You could just delete those files, but it's better to archive them, so
you can access them later. All you need to get started archiving your old
files is a USB drive, or an [Amazon Glacier](http://aws.amazon.com/glacier/)
account.

The webapp makes it easy to make a repository on either a USB drive,
or on Amazon Glacier. Once the repository is created, be sure to
put it in either the small archive, or full archive repository group.

[[!img repogroups.png]]

Now when you're done with a file, just move it into a directory named
"archive". The assistant will notice you put it there, and next time it
has the opportunity (when you plug in the USB drive, or when it can
talk to Amazon Glacier over the network), will move the file's
content to your archive repository.

You'll no longer be able to open the file once it's been archived.
If you later want to access it, you can just copy or move it out
of the archive directory, and the assistant will retrieve its
content from the archive.

Note that retrieving data from Amazon Glacier takes 4 to 5 hours.

### screencast

[[!inline feeds=no template=bare pages=videos/git-annex_assistant_archiving]]


code:
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawkYrMBMTCEFUKskhWGD-1pzcw2ITshsi_8"
 nickname="Robert"
 subject="Annex on OS X 10.6"
 date="2013-06-04T23:10:03Z"
 content="""
I really hope they can get annex working on os x 10.6.  This is a great effort.  Thanks
"""]]


code:
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawl9smfyJFgp3f2WjqqZWY6b7vo5eZv7GGQ"
 nickname="Bryan"
 subject="Ooh.  Do want on Windows"
 date="2013-07-03T20:44:05Z"
 content="""
Sadly, I didn't know about this when the Kickstarter was underway - I'd be happy to chip in $100 if it means I can get annex assistant on Windows earlier.

"""]]


code:
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawnov5q9_Cl4Ps5NoYE08yE01NLSvBANnY8"
 nickname="Eric"
 subject="Does it not work in Direct Mode?"
 date="2014-04-26T09:41:20Z"
 content="""
Looks great, but I got the impression that Assistant would mirror the files from my computer to my external hard drive, and I can't seem to get it to do that.
"""]]


code:
[[!comment format=mdwn
 username="https://www.google.com/accounts/o8/id?id=AItOawlr2Bj0Mzqwzl28cbrotcQUbOFoaPB3B_Y"
 nickname="Tomasz"
 subject="how to disable assistant"
 date="2014-04-28T10:21:59Z"
 content="""
assistant daemon now starts at boot and pushes all annexed files to other repos... I'd like to do it on my own. I can stop daemon from webapp, but it starts again on boot -  how Do I disable it from autostarting ?
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 ip="108.236.230.124"
 subject="comment 5"
 date="2014-05-16T18:55:22Z"
 content="""
If you have a question about using the assistant, please ask it in the [[forum]], not here.
"""]]


code:
So you have two computers in the same building, and you want them to share
the same synchronised folder, communicating directly with each other.

This is incredibly easy to set up with the git annex assistant.

Let's say the two computers are your computer and your friend's computer.
We'll start on your computer, where you open up your git annex dashboard.

[[!img addrepository.png alt="Add another repository button"]]

`*click*`

[[!img pairing.png alt="Pair with another computer"]]

`*click*`

Now the hard bit. You have to think up a secret phrase, and type it in,
(and perhaps get the spelling correct).

[[!img secret.png alt="Enter secret phrase"]]

Now your computer is in pairing mode. When your friend looks at her git
annex dashboard, she sees something like this.

[[!img pairrequest.png alt="Pair request"]]

`*click*`

[[!img secretempty.png alt="Enter same secret phrase"]]

Now it's up to you to let her know what the secret is. As soon as she
enters it, both your computers will be paired, and will begin to sync their
git-annex folders. Just like that you can share files.

----

## Requirements

For local pairing to work, you must have sshd (ssh server daemon) installed and working on all machines involved. That means you must allow at least local connections to sshd. On most Linux distributions, sshd is packaged in either openssh (openSUSE) or openssh-server (Debian).

It is highly recommended that you disable root login, disable password login to sshd and just enable key based authentication instead. No one will be able to login without your key.

To disable root, after installing sshd, edit the sshd config (usually /etc/ssh/sshd_config file) and disable root login by adding:

    PermitRootLogin no

Restart sshd. See man sshd_config for details.

To disable password login and enable key based authentication, edit the sshd config (just like above) by uncommenting and changing the following options:

    ChallengeResponseAuthentication no
    PasswordAuthentication no
    UsePAM no

    PubkeyAuthentication yes

Restart sshd. See man sshd_config for details.

You can also restrict login to your local network only (not allow internet users from trying to log into your computer). Edit the hosts.deny file (usually /etc/hosts.deny) by adding the following:

    sshd : ALL EXCEPT LOCAL

Do note that restricting login to your local network may or may not block git-annex. Also note that this will not work on Mac OSX because Apple decided to disable this feature and replace it with a crippled version made by Apple.

## Tips

Something to keep in mind, especially if pairing doesn't seem to be
working, is that the two computers need to be on the same network for this
pairing process to work. Sometimes a building will have more than one
network inside it, and you'll need to connect them both to the same one.
Make sure the wireless network name is the same, or that they're both
plugged into the same router.

Also, the file sharing set up by this pairing only works when both
computers are on the same network. If you go on a trip, any files you
edit will not be visible to your friend until you get back.

To get around this, you'll often also want to set up
[[jabber_pairing|share_with_a_friend_walkthrough]], and a server
in the cloud, which they can use to exchange files while away.

And also, you can pair with as many other computers as you like, not just
one!

## What does pairing actually do behind the scenes?

It ensures that both repositories have correctly configured
[[remotes|walkthrough/adding_a_remote]] pointing to each other.
If you have already configured this manually, you do not need to
perform pairing.


code:
[[!comment format=mdwn
 username="https://launchpad.net/~mattharrison"
 ip="69.193.72.98"
 subject="Pairing"
 date="2012-10-29T17:56:06Z"
 content="""
Is there a way to do this pairing with one machine being a desktop machine and one a headless machine?
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 ip="4.152.108.194"
 subject="easy peasy"
 date="2012-10-29T19:09:43Z"
 content="""
A headless machine is probably a server. On the same page that has the \"local computer\" link, there's a \"remote server\" link that'll get you set up.
"""]]


code:
[[!comment format=mdwn
 username="https://openid.fmarier.org/"
 nickname="fmarier"
 subject="Ports to open on the firewall?"
 date="2013-05-04T03:56:55Z"
 content="""
I'm trying to get local pairing working between two local machines (same switch, both connected via cat5 cables) and they're not seeing each other, though I can happily ssh from one box to the other.

In order to eliminate possible sources of problems, I tried these insecure settings:

* add a `-A INPUT -j ACCEPT` to the top of my firewall rules
* use `password` as the shared secret

but I still can't get past \"pairing in progress\" when pairing with a \"Local computer\".

Is there any way to get information as to where the two machines are failing to see one another?
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 nickname="joey"
 subject="comment 4"
 date="2013-05-04T16:39:23Z"
 content="""
Local pairing uses UDP port 55556. This is sent to multicast address 224.0.0.251 (same used by Avahi).

(You also need TCP port 22 open for ssh.)
"""]]


code:
[[!comment format=mdwn
 username="https://openid.fmarier.org/"
 nickname="fmarier"
 subject="Still stuck at "pairing in progress""
 date="2013-05-05T00:26:16Z"
 content="""
I hadn't thought of ssh. So here's what I've got now:

* both laptop and desktop have `-A INPUT -d 224.0.0.251/32 -p udp --dport 55556 -j ACCEPT`
* `git annex webapp` is running as user `francois` on both machines
* laptop has `openssh-server` running on port 22 and its firewall allows desktop to connect
* desktop has `openssh-server` running on port 22 and its firewall allows the whole internal network to connect
* laptop's ssh pubkey is in francois' `~/.ssh/authorized_keys` on desktop and ssh'ing works
* deskop's ssh pubkey is **not** in francois' `~/.ssh/authorized_keys` on laptop (is that required?)
* (as mentioned before) both desktop and laptop are on the same switch and connected over CAT5
* I'm using `password` as a pairing key just to rule out any typos there

I don't see anything in the git-annex log on both of these machines. There's just a bunch of key generation stuff and then the last line is \"Pairing in progress\".
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 nickname="joey"
 subject="comment 6"
 date="2013-05-06T15:14:06Z"
 content="""
It's quite possible that your router doesn't handle multicast traffic to 224.0.0.251. The best way to check is to a) see if avahi/zeroconf works, since it's sending similar traffic and b) run tcpdump on both machines and see if the packets being sent on port 55556 by one are seen by the other.
"""]]


code:
[[!comment format=mdwn
 username="https://openid.fmarier.org/"
 nickname="fmarier"
 subject="Make sure your network is correctly set up in the first place!"
 date="2013-05-12T08:37:38Z"
 content="""
It turns out that my internal network had badly broken IPv6 configs between the boxes. That was interfering with the multicast packets but not with anything else since all of my other internal traffic is over IPv4.

Getting rid of these static IPv6 addresses has solved my problem. Local pairing is now working as advertised :)
"""]]


code:
[[!comment format=mdwn
 username="http://joeyh.name/"
 nickname="joey"
 subject="comment 8"
 date="2013-05-13T17:22:17Z"
 content="""
I don't understand how IPv6 could affect local pairing. The assistant does not currently do pairing over ipv6 due to a limitation in the multicast library it's using.
"""]]


code:
## first run

To get started with the git-annex assistant, just pick it from
your system's list of applications.

[[!img assistant/menu.png]]
[[!img assistant/osx-app.png]]

It'll prompt you to set up a folder:

[[!img assistant/makerepo.png]]

Then any changes you make to its folder will automatically be committed to
git, and synced to repositories on other computers. You can use the
interface to add repositories and control the git-annex assistant.

[[!img assistant/running.png]]

## starting on boot

The git-annex assistant will automatically be started when you log in to
desktop environments like Mac OS X, Gnome, XFCE, and KDE, and the menu item
shown above can be used to open the webapp. On other systems, you may need
to start it by hand.

To start the webapp, run `git annex webapp` at the command line.

To start the assistant without opening the webapp,
you can run the command "git annex assistant --autostart". This is a
good thing to configure your system to run automatically when you log in.


code:
## version 5.20140421

This release begins to deprecate XMPP support. In particular, if you use
the assistant with a ssh remote that has this version of git-annex
installed, you don't need XMPP any longer to get immediate syncing of
changes.

## version 5.20140411

This release fixes a bug that could cause the assistant to use a *lot* of
CPU, when monthly fscking was set up.

Automatic upgrading was broken on OSX for previous versions. This has been
fixed, but you'll need to manually upgrade to this version to get it going
again. Workaround: Remove the wget bundled inside the git-annex dmg.

## version 5.20140221

The Windows port of the assistant and webapp is now considered to be beta
quality. There are important missing features (notably Jabber), documented
on [[todo/windows_support]], but the webapp is broadly usable on Windows
now.

## version 5.20131221

There is now a arm [[install/linux_standalone]] build of git-annex,
including the assistant and webapp,
which can be installed on a variety of systems including Raspberry Pi,
Synology NAS, and Google Chromebooks. Details in
[[this forum thread|forum/new_linux_arm_tarball_build]].

## version 5.20131213

The assistant can now be used on Windows! However, it has known problems,
described in [[todo/windows_support]], and should be considered an
alpha-level preview.

## version 5.20131127

Starting with this version, when git-annex is installed from a build on
this website, it will detect when new versions are available, and allow
easily upgrading. Automatic upgrades can also be configured if desired,
or automatic upgrade checking can be disabled in the preferences page.

git-annex builds from distributions, like Debian will not automatically
upgrade; use the distribution's package manager for that. However, the
git-annex webapp will also detect when a distribution has upgraded
git-annex and offer to restart the assistant.

## version 4.20131024

This version fixes several different bugs that could cause the webapp to
refuse to create a repository. Several other bugs are also fixed, including
a bug that caused it to not add files on Android.

New in this release is the ability to use the webapp to set up scheduled
consistency checks of your repositories. Many problems with repositories
are now automatically corrected, and it can even repair damaged git
repositories.

This is a recommended upgrade.

## version 4.20131002

Now you can use the webapp to set up an encrypted git repository on a
remote ssh server, or on rsync.net, and use it as a live cloud backup. Or,
use the webapp to make an encrypted git repository on a removable drive,
and store it offsite as a secure backup.

## version 4.20130920

This release is the first to support fully encrypted git repositories
stored on removable drives. This can be set up easily using the webapp.

## version 4.20130909

This release fixes a crash that could occur when using XMPP with the
assitant. It has only been seen on OS X so far. The bug is not believed to
be explitable, but upgrading is still recommended.

## version 4.20130802

This release fixes several bugs, including a reversion introduced in the last
version that broke direct mode on Windows, Android, and other crippled
filesystems. It contains a workaround for a bug in recent git pre-releases
that broke handling of filenames containing spaces.
It is a highly recommended upgrade.

The webapp can now detect repositories that did not finish getting properly set
up, and can recover from one common bug that broke local pairing and remote
ssh server setups on systems using `ssh-agent`.

## version 4.20130723

This release fixes some bugs. Notably it fixes a bug that could result in data
loss when adding a tarball of a git-annex repository to your git-annex
repository.

Rsync.net have committed to support git-annex and offer a special
discounted rate for git-annex users.
<http://www.rsync.net/products/git-annex-pricing.html>

## version 4.20130709

This release is mostly bug fixes.

One of the bugs involved setting up rsync remotes on servers other than
rsync.net. The wrong `.ssh/authorized_keys` line was deployed to the
remote server. If you set up a rsync remote with a past release, and it does
not work, you will need to manually edit the `.ssh/authorized_keys` file,
and remove the `command=` forced command.

## version 4.20130621, 4.20130627

These releases mostly consist of bug fixes.

## version 4.20130601

This is a bugfix release, featuring significant XMPP improvements and
more robustness thanks to automated fuzz testing. Recommended upgrade.

This version changes its XMPP protocol, so it will fail to sync with older
git-annex versions over XMPP.

## version 4.20130521

This is a bugfix release. Recommended upgrade.

## version 4.20130516

This version contains numerous bug fixes, and improvements.

This is the first release with a fully usable Android app. No command-line
typing needed to set up syncing to your Android phone or tablet!
A few of the more advanced features may not work (or not work reliably)
on Android. The Android app is still beta quality.

This is also the first release with a Windows port! The Windows port
is in an alpha quality state, and is missing many features.
It does not yet include the assistant.

## version 4.20130501

This version contains numerous bug fixes, and improvements.

## version 4.20130417

This version contains numerous bug fixes, and improvements.

One bug that was fixed can affect users of gnome-keyring who
have set up remote repositories on ssh servers using the webapp.
The gnome-keyring may load the restricted key that is set up
for that, and make it be used for regular logins to the server;
with the result that you'll get an error message about "git-annex-shell"
when sshing to the server.

If you experience this problem you can fix it by
moving `.ssh/key.git-annex*` to `.ssh/git-annex/` (creating
that directory first), and edit `.ssh/config` to reflect the new
location of the key. You will also need to restart gnome-keyring.

Another change relates to files in `archive/` directories. Client repositories
now sync these files between themselves like any other files, until
the files reach an archive repository. Only then are they removed from
the client repositories. So you need to ensure you have at least one
archive repository if you want to use the `archive/` directory feature.

## version 4.20130323, 4.20130405

These versions continue fixing bugs and adding features.

## version 4.20130314

This version makes a great many improvements and bugfixes, and is
a recommended upgrade.

If you have already used the webapp to locally pair two computers,
a bug caused the paired repository to not be given an appropriate cost.
To fix this, go into the Repositories page in the webapp, and drag the
repository for the locally paired computer to come before any repositories
that it's more expensive to transfer data to.

## version 4.20130227

This release fixes a bug with globbing that broke preferred content expressions.
So, it is a recommended upgrade from the previous release, which introduced
that bug.

In this release, the assistant is fully working on Android, although
it must be set up using the command line.

Repositories can now be placed on filesystems that lack support for symbolic
links; FAT support is complete.

## version 3.20130216

This adds a port to Android. Only usable at the command line so far;
beta qualitty.

Also a bugfix release, and improves support for FAT.

The following are known limitations of this release of the git-annex
assistant:

* No Android app yet.
* On BSD operating systems (but not on OS X), the assistant uses kqueue to
  watch files. Kqueue has to open every directory it watches, so too many
  directories will run it out of the max number of open files (typically
  1024), and fail. See [[this_bug|bugs/Issue_on_OSX_with_some_system_limits]]
  for a workaround.
* Also on systems with kqueue, modifications to existing files in direct
  mode will not be noticed.

## version 3.20130107, 3.20130114, 3.20130124, 3.20130207

These are bugfix releases.

## version 3.20130102

This release makes several significant improvements to the git-annex
assistant, which is still in beta.

The main improvement is direct mode. This allows you to directly edit files
in the repository, and the assistant will automatically commit and sync
your changes. Direct mode is the default for new repositories created
by the assistant. To convert your existing repository to use direct mode,
manually run `git annex direct` inside the repository.

## version 3.20121211

This release of the git-annex assistant (which is still in beta)
consists of mostly bugfixes, user interface improvements, and improvements
to existing features.

In general, anything you can configure with the assistant's web app
will work. Some examples of use cases supported by this release include:

* Using Box.com's 5 gigabytes of free storage space as a cloud transfer
  point between between repositories that cannot directly contact
  one-another. (Many other cloud providers are also supported, from Rsync.net
  to Amazon S3, to your own ssh server.)
* Archiving or backing up files to Amazon Glacier. See [[archival_walkthrough]].
* [[Sharing repositories with friends|share_with_a_friend_walkthrough]]
  contacted through a Jabber server (such as Google Talk).
* [[Pairing|local_pairing_walkthrough]] two computers that are on the same local
  network (or VPN) and automatically keeping the files in the annex in
  sync as changes are made to them.
* Cloning your repository to removable drives, USB keys, etc. The assistant
  will notice when the drive is mounted and keep it in sync.
  Such a drive can be stored as an offline backup, or transported between
  computers to keep them in sync.

The following are known limitations of this release of the git-annex
assistant:

* The Max OSX standalone app may not work on all versions of Max OSX.
  Please test!
* On Mac OSX and BSD operating systems, the assistant uses kqueue to watch
  files. Kqueue has to open every directory it watches, so too many
  directories will run it out of the max number of open files (typically
  1024), and fail. See [[bugs/Issue_on_OSX_with_some_system_limits]]
  for a workaround.

## version 3.20121126

This adds several features to the git-annex assistant, which is still in beta.

In general, anything you can configure with the assistant's web app
will work. Some examples of use cases supported by this release include:

* Using Box.com's 5 gigabytes of free storage space as a cloud transfer
  point between between repositories that cannot directly contact
  one-another. (Many other cloud providers are also supported, from Rsync.net
  to Amazon S3, to your own ssh server.)
* Archiving or backing up files to Amazon Glacier.
* [[Sharing repositories with friends|share_with_a_friend_walkthrough]]
  contacted through a Jabber server (such as Google Talk).
* [[Pairing|local_pairing_walkthrough]] two computers that are on the same local
  network (or VPN) and automatically keeping the files in the annex in
  sync as changes are made to them.
* Cloning your repository to removable drives, USB keys, etc. The assistant
  will notice when the drive is mounted and keep it in sync.
  Such a drive can be stored as an offline backup, or transported between
  computers to keep them in sync.

The following are known limitations of this release of the git-annex
assistant:

* The Max OSX standalone app does not work on all versions of Max OSX.
* On Mac OSX and BSD operating systems, the assistant uses kqueue to watch
  files. Kqueue has to open every directory it watches, so too many
  directories will run it out of the max number of open files (typically
  1024), and fail. See [[bugs/Issue_on_OSX_with_some_system_limits]]
  for a workaround.
* Retrieval of files from Amazon Glacier is not fully automated; the
  assistant does not automatically retry in the 4 to 5 hours period
  when Glacier makes the files available.

## version 3.20121112

This is a major upgrade of the git-annex assistant, which is still in beta.

In general, anything you can configure with the assistant's web app
will work. Some examples of use cases supported by this release include:

* [[Sharing repositories with friends|share_with_a_friend_walkthrough]]
  contacted through a Jabber server (such as Google Talk).
* Setting up cloud repositories, that are used as backups, archives,
  or transfer points between repositories that cannot directly contact
  one-another.
* [[Pairing|local_pairing_walkthrough]] two computers that are on the same local
  network (or VPN) and automatically keeping the files in the annex in
  sync as changes are made to them.
* Cloning your repository to removable drives, USB keys, etc. The assistant
  will notice when the drive is mounted and keep it in sync.
  Such a drive can be stored as an offline backup, or transported between
  computers to keep them in sync.

The following upgrade notes apply if you're upgrading from a previous version:

* For best results, edit the configuration of repositories you set
  up with older versions, and place them in a repository group.
  This lets the assistant know how you want to use the repository; for backup,
  archival, as a transfer point for clients, etc. Go to Configuration ->
  Manage Repositories, and click in the "configure" link to edit a repository's
  configuration.
* If you set up a cloud repository with an older version, and have multiple
  clients using it, you are recommended to configure an Jabber account,
  so that clients can use it to communicate when sending data to the
  cloud repository. Configure Jabber by opening the webapp, and going to
  Configuration -> Configure jabber account
* When setting up local pairing, the assistant did not limit the paired
  computer to accessing a single git repository. This new version does,
  by setting GIT_ANNEX_SHELL_DIRECTORY in `~/.ssh/authorized_keys`.

The following are known limitations of this release of the git-annex
assistant:

* On Mac OSX and BSD operating systems, the assistant uses kqueue to watch
  files. Kqueue has to open every directory it watches, so too many
  directories will run it out of the max number of open files (typically
  1024), and fail. See [[bugs/Issue_on_OSX_with_some_system_limits]]
  for a workaround.

## version 3.20121009

This is a maintenance release of the git-annex assistant, which is still in
beta.

In general, anything you can configure with the assistant's web app
will work. Some examples of use cases supported by this release include:

* [[Pairing|local_pairing_walkthrough]] two computers that are on the same local
  network (or VPN) and automatically keeping the files in the annex in
  sync as changes are made to them.
* Cloning your repository to removable drives, USB keys, etc. The assistant
  will notice when the drive is mounted and keep it in sync.
  Such a drive can be stored as an offline backup, or transported between
  computers to keep them in sync.
* Cloning your repository to a remote server, running ssh, and uploading
  changes made to your files to the server. There is special support
  for using the rsync.net cloud provider this way, or any shell account
  on a typical unix server, such as a Linode VPS can be used.

The following are known limitations of this release of the git-annex
assistant:

* On Mac OSX and BSD operating systems, the assistant uses kqueue to watch
  files. Kqueue has to open every directory it watches, so too many
  directories will run it out of the max number of open files (typically
  1024), and fail. See [[bugs/Issue_on_OSX_with_some_system_limits]]
  for a workaround.
* In order to ensure that all multiple repositories are kept in sync,
  each computer with a repository must be running the git-annex assistant.
* The assistant does not yet always manage to keep repositories in sync
  when some are hidden from others behind firewalls.

## version 3.20120924

This is the first beta release of the git-annex assistant.

In general, anything you can configure with the assistant's web app
will work. Some examples of use cases supported by this release include:

* [[Pairing|local_pairing_walkthrough]] two computers that are on the same local
  network (or VPN) and automatically keeping the files in the annex in
  sync as changes are made to them.
* Cloning your repository to removable drives, USB keys, etc. The assistant
  will notice when the drive is mounted and keep it in sync.
  Such a drive can be stored as an offline backup, or transported between
  computers to keep them in sync.
* Cloning your repository to a remote server, running ssh, and uploading
  changes made to your files to the server. There is special support
  for using the rsync.net cloud provider this way, or any shell account
  on a typical unix server, such as a Linode VPS can be used.

The following are known limitations of this release of the git-annex
assistant:

* On Mac OSX and BSD operating systems, the assistant uses kqueue to watch
  files. Kqueue has to open every directory it watches, so too many
  directories will run it out of the max number of open files (typically
  1024), and fail. See [[bugs/Issue_on_OSX_with_some_system_limits]]
  for a workaround.
* In order to ensure that all multiple repositories are kept in sync,
  each computer with a repository must be running the git-annex assistant.
* The assistant does not yet always manage to keep repositories in sync
  when some are hidden from others behind firewalls.
* If a file is checked into git as a normal file and gets modified
  (or merged, etc), it will be converted into an annexed file. So you
  should not mix use of the assistant with normal git files in the same
  repository yet.
* If you `git annex unlock` a file, it will immediately be re-locked.
  See [[bugs/watcher_commits_unlocked_files]].


code:
[[!comment format=mdwn
 username="http://wiggy.net/"
 nickname="Wichert"
 subject="OSX 10.8's gatekeeper does not like git-annex"
 date="2012-11-13T14:47:52Z"
 content="""
Trying to run this release on OSX results in an error message from Gatekeeper:

> \"git-annex\" can't be opened because it is from an unidentified developer.
>
> Your security preferences allow installation of only apps from the Mac App Store and identified developers.

It would be nice if the binary could be signed to make Gatekeeper happy. Until then a note in the installation instructions might be useful.
"""]]


code:
[[!comment format=mdwn
 username="http://wiggy.net/"
 nickname="Wichert"
 subject="git-annex not runnable on OSX 10.8"
 date="2012-11-13T14:49:35Z"
 content="""
After telling Gatekeeper that I really want to run git-annex it still fails:

[fog;~]-131> open Applications/git-annex.app
LSOpenURLsWithRole() failed with error -10810 for the file /Users/wichert/Applications/git-annex.app.

"""]]