Lintian Fixes - git-annex

Ready changes

Summary

Failed fixers:

See the worker log for details.

Diff

diff --git a/debian/changelog b/debian/changelog
index 0f473cc1b6..3f899d26bd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -431,7 +431,7 @@ git-annex (6.20171109) unstable; urgency=medium
     in the web when some urls don't work, as long as at least one url does
     work.
   * Makefile improvement for sudo make install.
-    Thanks, Eric Siegerman 
+    Thanks, Eric Siegerman
   * Makefile improvement for BUILDER=stack, use stack to run ghc.
   * testremote: Test exporttree.
   * Fix directory special remote's cleanup of empty export directories.
@@ -451,7 +451,7 @@ git-annex (6.20171026) unstable; urgency=medium
   * Add day to metadata when annex.genmetadata is enabled.
     Thanks, Sean T Parsons
   * stack.yaml: Added nix packages section.
-    Thanks, Sean T Parsons 
+    Thanks, Sean T Parsons
 
  -- Joey Hess <id@joeyh.name>  Thu, 26 Oct 2017 13:56:18 -0400
 
@@ -562,7 +562,7 @@ git-annex (6.20170818) unstable; urgency=high
     the filename parameter to the TRANSFER command could not contain
     spaces. It can in fact contain spaces. Special remotes implementors
     that relied on that may need to fix bugs in their special remotes.
-  * Fix the external special remotes git-annex-remote-ipfs, 
+  * Fix the external special remotes git-annex-remote-ipfs,
     git-annex-remote-torrent and the example.sh template to correctly
     support filenames with spaces.
   * Windows: Win32 package has subsumed Win32-extras; update dependency.
@@ -583,7 +583,7 @@ git-annex (6.20170520) unstable; urgency=medium
   * metadata: When setting metadata of a file that did not exist,
     no error message was displayed, unlike getting metadata and most other
     git-annex commands. Fixed this oversight.
-  * Added annex.resolvemerge configuration, which can be set to false to 
+  * Added annex.resolvemerge configuration, which can be set to false to
     disable the usual automatic merge conflict resolution done by git-annex
     sync and the assistant.
   * sync: Added --no-resolvemerge option.
@@ -731,7 +731,7 @@ git-annex (6.20170228) unstable; urgency=medium
     filesystem, run the post-receive hook there, since it wouldn't get run
     otherwise. This makes pushing to repos on FAT-formatted removable
     drives update them when receive.denyCurrentBranch=updateInstead.
-  * config group groupwanted numcopies schedule wanted required: 
+  * config group groupwanted numcopies schedule wanted required:
     Avoid displaying extraneous messages about repository auto-init,
     git-annex branch merging, etc, when being used to get information.
   * adjust: Fix behavior when used in a repository that contains
@@ -858,7 +858,7 @@ git-annex (6.20170818) unstable; urgency=high
     the filename parameter to the TRANSFER command could not contain
     spaces. It can in fact contain spaces. Special remotes implementors
     that relied on that may need to fix bugs in their special remotes.
-  * Fix the external special remotes git-annex-remote-ipfs, 
+  * Fix the external special remotes git-annex-remote-ipfs,
     git-annex-remote-torrent and the example.sh template to correctly
     support filenames with spaces.
   * Windows: Win32 package has subsumed Win32-extras; update dependency.
@@ -879,7 +879,7 @@ git-annex (6.20170520) unstable; urgency=medium
   * metadata: When setting metadata of a file that did not exist,
     no error message was displayed, unlike getting metadata and most other
     git-annex commands. Fixed this oversight.
-  * Added annex.resolvemerge configuration, which can be set to false to 
+  * Added annex.resolvemerge configuration, which can be set to false to
     disable the usual automatic merge conflict resolution done by git-annex
     sync and the assistant.
   * sync: Added --no-resolvemerge option.
@@ -1027,7 +1027,7 @@ git-annex (6.20170228) unstable; urgency=medium
     filesystem, run the post-receive hook there, since it wouldn't get run
     otherwise. This makes pushing to repos on FAT-formatted removable
     drives update them when receive.denyCurrentBranch=updateInstead.
-  * config group groupwanted numcopies schedule wanted required: 
+  * config group groupwanted numcopies schedule wanted required:
     Avoid displaying extraneous messages about repository auto-init,
     git-annex branch merging, etc, when being used to get information.
   * adjust: Fix behavior when used in a repository that contains
@@ -1147,7 +1147,7 @@ git-annex (6.20170101) unstable; urgency=medium
   * enable-tor: Put tor sockets in /var/lib/tor-annex/, rather
     than in /etc/tor/hidden_service/.
   * enable-tor: No longer needs to be run as root.
-  * enable-tor: When run as a regular user, also tests a connection back to 
+  * enable-tor: When run as a regular user, also tests a connection back to
     the hidden service over tor.
   * Support all common locations of the torrc file.
   * Always use filesystem encoding for all file and handle reads and
@@ -1187,7 +1187,7 @@ git-annex (6.20161210) unstable; urgency=medium
   * fromkey: Accept multiple pairs of files and keys.
     Thanks, Daniel Brooks.
   * rekey: Added --batch mode.
-  * add: Stage modified non-large files when running in indirect mode. 
+  * add: Stage modified non-large files when running in indirect mode.
     (This was already done in v6 mode and direct mode.)
   * git-annex-shell, remotedaemon, git remote: Fix some memory DOS attacks.
   * Fix build with http-client 0.5.
@@ -1206,7 +1206,7 @@ git-annex (6.20161118) unstable; urgency=medium
   * git-annex.cabal: Loosen bounds on persistent to allow 2.5, which
     on Debian has been patched to work with esqueleto.
     This may break cabal's resolver on non-Debian systems;
-    if so, either use stack to build, or run cabal with 
+    if so, either use stack to build, or run cabal with
     --constraint='persistent ==2.2.4.1'
     Hopefully this mess with esqueleto will be resolved soon.
   * sync: Pass --allow-unrelated-histories to git merge when used with git
@@ -1291,7 +1291,7 @@ git-annex (6.20161027) unstable; urgency=medium
     the transfer will be retried. (The assistant already did this.)
   * Run ssh with ServerAliveInterval 60, so that stalled transfers will
     be noticed within about 3 minutes.
-    (Any setting in your ~/.ssh/config or /etc/ssh/ssh_config 
+    (Any setting in your ~/.ssh/config or /etc/ssh/ssh_config
     overrides this.)
 
  -- Joey Hess <id@joeyh.name>  Thu, 27 Oct 2016 15:21:58 -0400
@@ -1307,7 +1307,7 @@ git-annex (6.20161012) unstable; urgency=medium
   * Optimisations to time it takes git-annex to walk working tree and find
     files to work on. Sped up by around 18%.
   * Optimisations to git-annex branch query and setting, avoiding repeated
-    copies of the environment. Speeds up commands like 
+    copies of the environment. Speeds up commands like
     "git-annex find --in remote" by over 50%.
   * Optimised git-annex branch log file timestamp parsing.
   * Add "total-size" field to --json-progress output.
@@ -1444,7 +1444,7 @@ git-annex (6.20160619) unstable; urgency=medium
   * get, drop: Add --batch and --json options.
   * testremote: Fix crash when testing a freshly made external special remote.
   * Remove unnecessary rpaths in the git-annex binary, but only when
-    it's built using make, not cabal. 
+    it's built using make, not cabal.
     This speeds up git-annex startup time by around 50%.
   * Speed up startup time by caching the refs that have been merged into
     the git-annex branch.
@@ -1466,7 +1466,7 @@ git-annex (6.20160619) unstable; urgency=medium
   * webapp: Escape unusual characters in ssh hostnames when generating
     mangled hostnames. This allows IPv6 addresses to be used on filesystems
     not supporting : in filenames.
-  * Avoid any access to keys database in v5 mode repositories, which 
+  * Avoid any access to keys database in v5 mode repositories, which
     are not supposed to use that database.
   * Remove the EKG build flag, since Gentoo for some reason decided to
     enable this flag, depsite it not being intended for production use and
@@ -1487,7 +1487,7 @@ git-annex (6.20160613) unstable; urgency=medium
     union merging and performing transitions.
   * Remove Makefile from cabal tarball; man page building is now handled by
     a small haskell program.
-  * sync --content: Fix bug that caused transfers of files to be made 
+  * sync --content: Fix bug that caused transfers of files to be made
     to a git remote that does not have a UUID. This particularly impacted
     clones from gcrypt repositories.
   * Pass -S to git commit-tree when commit.gpgsign is set and when
@@ -1508,7 +1508,7 @@ git-annex (6.20160613) unstable; urgency=medium
     and a directory with the same name when in an adjusted branch.
   * v6: Fix bad merge in an adjusted branch that resulted in an empty tree.
   * v6: Fix bug in initialization of clone from a repo with an adjusted branch
-    that had not been synced back to master. 
+    that had not been synced back to master.
     (This bug caused broken tree objects to get built by a later git annex
     sync.)
   * v6: Make lock and unlock work on files whose content is not present.
@@ -1893,7 +1893,7 @@ git-annex (5.20151208) unstable; urgency=medium
     to a local git repo, and from a remote git repo.
   * Display progress meter in -J mode when downloading from the web.
   * map: Improve display of git remotes with non-ssh urls, including http
-    and gcrypt. 
+    and gcrypt.
   * When core.sharedRepository is set, annex object files are not made mode
     444, since that prevents a user other than the file owner from locking
     them. Instead, a mode such as 664 is used in this case.
@@ -1903,7 +1903,7 @@ git-annex (5.20151208) unstable; urgency=medium
     when the content of the url is downloaded. (Not when using --fast or
     --relaxed.)
   * webapp: Fix bugs that could result in a relative path such as "."
-    being written to ~/.config/git-annex/autostart, and ignore any such 
+    being written to ~/.config/git-annex/autostart, and ignore any such
     relative paths in the file.
     This was a reversion caused by the relative path changes in 5.20150113.
   * dropunused: Make more robust when trying to drop an object that has
@@ -1923,7 +1923,7 @@ git-annex (5.20151116) unstable; urgency=medium
 
   * Use concurrent-output library when configured with -fConcurrentOutput.
     This allows nicely displayed messages when using the -J flag.
-  * Additional commands now support the -J flag: 
+  * Additional commands now support the -J flag:
     fsck, drop, add, addurl, import
   * import: Avoid very ugly error messages when the directory files
     are imported to is not a directort, but perhaps an annexed file.
@@ -2123,7 +2123,7 @@ git-annex (5.20150824) unstable; urgency=medium
   * Sped up downloads of files from ssh remotes, reducing the
     non-data-transfer overhead 6x.
   * sync: Support --jobs
-  * sync --content: Avoid unnecessary second pull from remotes when 
+  * sync --content: Avoid unnecessary second pull from remotes when
     no file transfers are made.
   * External special remotes can now be built that can be used in readonly
     mode, where git-annex downloads content from the remote using regular
@@ -2189,7 +2189,7 @@ git-annex (5.20150812) unstable; urgency=medium
   * Linux standalone: Work around problem that prevented it from working
     properly if unpacked into a directory that contains ":" or ";" in its
     name.
-  * proxy: Fix proxy git commit of non-annexed files in direct mode. 
+  * proxy: Fix proxy git commit of non-annexed files in direct mode.
   * proxy: If a non-proxied git command, such as git revert
     would normally fail because of unstaged files in the work tree,
     make the proxied command fail the same way.
@@ -2245,7 +2245,7 @@ git-annex (5.20150727) unstable; urgency=medium
     edge cases of option parsing. (For example, the metadata command no
     longer accepts the combination of --get and --set, which never actually
     worked.)
-  * Bash completion file is now included in the git-annex source tree, 
+  * Bash completion file is now included in the git-annex source tree,
     and installed into Debian package (and any other packages built using make
     install). This bash completion is generated by the option parser, so it
     covers all commands, all options, and will never go out of date!
@@ -2298,7 +2298,7 @@ git-annex (5.20150710-1) unstable; urgency=medium
     use the ssh agent of a new login session.
   * assistant: Fix local pairing to not include newline in ssh pubkey,
     which is rejected on the other end for security reasons.
-  * assistant: Fix ANNEX_SHELL_DIR written to ~/.ssh/authorized_keys 
+  * assistant: Fix ANNEX_SHELL_DIR written to ~/.ssh/authorized_keys
     in local pairing to be the absolute path to the repository, not "."
     This was a reversion caused by the relative path changes in 5.20150113.
   * Brought back the setkey plumbing command that was removed in 2011, since
@@ -2676,7 +2676,7 @@ git-annex (5.20150219) unstable; urgency=medium
     parameters it does not understand.
   * groupwanted: New command to set the groupwanted preferred content
     expression.
-  * import: Support file matching options such as --exclude, --include, 
+  * import: Support file matching options such as --exclude, --include,
     --smallerthan, --largerthan
   * The file matching options are now only accepted by commands that
     can actually use them, instead of by all commands.
@@ -2865,7 +2865,7 @@ git-annex (5.20141024) unstable; urgency=medium
     making git-annex not re-exec itself on start on windows, and making the
     test suite on Windows run tests without forking.
   * glacier: Fix pipe setup when calling glacier-cli to retrieve an object.
-  * info: When run on a single annexed file, displays some info about the 
+  * info: When run on a single annexed file, displays some info about the
     file, including its key and size.
   * info: When passed the name or uuid of a remote, displays info about that
     remote. Remotes that support encryption, chunking, or embedded
@@ -2947,7 +2947,7 @@ git-annex (5.20140915) unstable; urgency=medium
     capacity/accuracy, fall back to a reasonable default bloom filter size.
   * Fix build with optparse-applicative 0.10. Closes: #761484
   * webapp: Fixed visual glitch in xmpp pairing that was reported live by a
-    user who tracked me down in front of a coffee cart in Portland. 
+    user who tracked me down in front of a coffee cart in Portland.
     (New bug reporting method of choice?)
 
  -- Joey Hess <joeyh@debian.org>  Mon, 15 Sep 2014 10:45:00 -0400
@@ -3165,7 +3165,7 @@ git-annex (5.20140517) unstable; urgency=medium
   * group: When no groups are specified to set, lists the current groups
     of a repository.
   * Add remote.$name.annex-shell configuration.
-    Thanks, Fraser Tweedale 
+    Thanks, Fraser Tweedale
   * Support symlinking git-annex and git-annex-shell
     from the Linux standalone bundle into PATH.
     Thanks, jlebar.
@@ -3181,7 +3181,7 @@ git-annex (5.20140421) unstable; urgency=medium
     notifychanges support (>= 5.20140405)
   * webapp: Show a network signal icon next to ssh and xmpp remotes that
     it's currently connected with.
-  * webapp: Rework xmpp nudge to prompt for either xmpp or a ssh remote 
+  * webapp: Rework xmpp nudge to prompt for either xmpp or a ssh remote
     to be set up.
   * sync, assistant, remotedaemon: Use ssh connection caching for git pushes
     and pulls.
@@ -3250,7 +3250,7 @@ git-annex (5.20140402) unstable; urgency=medium
 
   * unannex, uninit: Avoid committing after every file is unannexed,
     for massive speedup.
-  * --notify-finish switch will cause desktop notifications after each 
+  * --notify-finish switch will cause desktop notifications after each
     file upload/download/drop completes
     (using the dbus Desktop Notifications Specification)
   * --notify-start switch will show desktop notifications when each
@@ -3277,7 +3277,7 @@ git-annex (5.20140402) unstable; urgency=medium
     http://git-annex.branchable.com/bugs/problems_with_glacier/
   * Added required content configuration.
   * assistant: Improve ssh authorized keys line generated in local pairing
-    or for a remote ssh server to set environment variables in an 
+    or for a remote ssh server to set environment variables in an
     alternative way that works with the non-POSIX fish shell, as well
     as POSIX shells.
 
@@ -3801,7 +3801,7 @@ git-annex (4.20131101) unstable; urgency=low
   * unannex: New, much slower, but more safe behavior: Copies files out of
     the annex. This avoids an unannex of one file breaking other files that
     link to the same content. Also, it means that the content
-    remains in the annex using up space until cleaned up with 
+    remains in the annex using up space until cleaned up with
     "git annex unused".
     (The behavior of unannex --fast has not changed; it still hard links
     to content in the annex. --fast was not made the default because it is
@@ -3977,7 +3977,7 @@ git-annex (4.20130827) unstable; urgency=low
     (Thanks, guilhem for the patch.)
   * unused: Fix bugs in two edge cases involving manually staged changes.
     (Thanks, guilhem for the patch.)
-  * Android: Fix bug in terminal app that caused it to spin using much 
+  * Android: Fix bug in terminal app that caused it to spin using much
     CPU and battery. This problem was introduced in version 4.20130601.
   * sync, merge: Bug fix: Don't try to merge into master when in a bare repo.
   * import: Add options to control handling of duplicate files:
@@ -4017,7 +4017,7 @@ git-annex (4.20130802) unstable; urgency=low
     to by the git history, without being forced.
     Like drop, dropunused checks remotes, and honors the global
     annex.numcopies setting. (However, .gitattributes settings cannot
-    apply to unused files.) 
+    apply to unused files.)
   * Fix inverted logic in last release's fix for data loss bug,
     that caused git-annex sync on FAT or other crippled filesystems to add
     symlink standin files to the annex.
@@ -4104,7 +4104,7 @@ git-annex (4.20130709) unstable; urgency=low
     by the last run of git annex unused. Supported by fsck, move, copy.
   * get, move, copy: Can now be run in a bare repository,
     like fsck already could. --all is enabled automatically in this case.
-  * merge: Now also merges synced/master or similar branches, which 
+  * merge: Now also merges synced/master or similar branches, which
     makes it useful to put in a post-receive hook to make a repository
     automatically update its working copy when git annex sync or the assistant
     sync with it.
@@ -4115,7 +4115,7 @@ git-annex (4.20130709) unstable; urgency=low
   * addurl --pathdepth: Fix failure when the pathdepth specified is deeper
     than the urls's path.
   * Windows: Look for .exe extension when searching for a command in path.
-  * Pass -f to curl when downloading a file with it, so it propigates failure. 
+  * Pass -f to curl when downloading a file with it, so it propigates failure.
   * Windows: Fix url to object when using a http remote.
   * webapp: Fix authorized_keys line added when setting up a rsync remote
     on a server that also supports git-annex, to not force running
@@ -4144,9 +4144,9 @@ git-annex (4.20130627) unstable; urgency=low
     server.
   * webapp: Ensure that ssh keys generated for different directories
     on a server are always different.
-  * webapp: Fix bug setting up ssh repo if the user enters "~/" at the start 
+  * webapp: Fix bug setting up ssh repo if the user enters "~/" at the start
     of the path.
-  * assistant: Fix bug that prevented adding files written by gnucash, 
+  * assistant: Fix bug that prevented adding files written by gnucash,
     and more generally support adding hard links to files. However,
     other operations on hard links are still unsupported.
   * webapp: Fix bug that caused the webapp to hang when built with yesod 1.2.
@@ -4290,7 +4290,7 @@ git-annex (4.20130501) unstable; urgency=low
     installed can be used to keep clients' git repos in sync.
   * assistant: Work around misfeature in git 1.8.2 that makes
     `git commit --alow-empty -m ""` run an editor.
-  * sync: Bug fix, avoid adding to the annex the 
+  * sync: Bug fix, avoid adding to the annex the
     dummy symlinks used on crippled filesystems.
   * Add public repository group.
     (And inpreferreddir to preferred content expressions.)
@@ -4450,7 +4450,7 @@ git-annex (4.20130323) unstable; urgency=low
     to the network, or connecting a drive.
   * assistant: Fix OSX bug that prevented committing changed files to a
     repository when in indirect mode.
-  * webapp: Improved alerts displayed when syncing with remotes, and 
+  * webapp: Improved alerts displayed when syncing with remotes, and
     when syncing with a remote fails.
   * webapp: Force wrap long filenames in transfer display.
   * assistant: The ConfigMonitor left one zombie behind each time
@@ -4538,7 +4538,7 @@ git-annex (4.20130314) unstable; urgency=low
     may do undesired things with it.
   * Several improvements to Makefile and cabal file. Thanks, Peter Simmons
   * Stop depending on testpack.
-  * Android: Enable test suite. 
+  * Android: Enable test suite.
 
  -- Joey Hess <joeyh@debian.org>  Thu, 14 Mar 2013 15:29:20 -0400
 
@@ -4606,7 +4606,7 @@ git-annex (3.20130207) unstable; urgency=low
   * assistant: Ignore .DS_Store on OSX.
   * assistant: Fix location log when adding new file in direct mode.
   * Deal with stale mappings for deleted file in direct mode.
-  * pre-commit: Update direct mode mappings. 
+  * pre-commit: Update direct mode mappings.
   * uninit, unannex --fast: If hard link creation fails, fall back to slow
     mode.
   * Clean up direct mode cache and mapping info when dropping keys.
@@ -4626,7 +4626,7 @@ git-annex (3.20130124) unstable; urgency=low
   * webapp: More adjustments to longpoll code to deal with changes in
     variable quoting in different versions of shakespeare-js.
   * webapp: Avoid an error if a transfer is stopped just as it finishes.
-    Closes: #698184 
+    Closes: #698184
   * webapp: Now always logs to .git/annex/daemon.log
   * webapp: Has a page to view the log, accessed from the control menu.
   * webapp: Fix crash adding removable drive that has an annex directory
@@ -4777,7 +4777,7 @@ git-annex (3.20121126) unstable; urgency=low
     it all in memory.
   * S3: Added progress display for uploading and downloading.
   * directory special remote: Made more efficient and robust.
-  * Bugfix: directory special remote could loop forever storing a key 
+  * Bugfix: directory special remote could loop forever storing a key
     when a too small chunksize was configured.
   * Allow controlling whether login credentials for S3 and webdav are
     committed to the repository, by setting embedcreds=yes|no when running
@@ -4831,7 +4831,7 @@ git-annex (3.20121112) unstable; urgency=low
     to test a key's presence.
   * The standalone tarball's runshell now takes care of installing a
     ~/.ssh/git-annex-shell wrapper the first time it's run.
-  * webapp: Make an initial, empty commit so there is a master branch 
+  * webapp: Make an initial, empty commit so there is a master branch
   * assistant: Fix syncing local drives.
   * webapp: Fix creation of rsync.net repositories.
   * webapp: Fix renaming of special remotes.
@@ -4866,7 +4866,7 @@ git-annex (3.20121016) unstable; urgency=low
   * A relative core.worktree is relative to the gitdir. Now that this is
     handled correctly, git-annex can be used in git submodules.
   * Temporarily disable use of dbus, as the haskell dbus library blows up
-    when losing connection, which will need to be fixed upstream. 
+    when losing connection, which will need to be fixed upstream.
 
  -- Joey Hess <joeyh@debian.org>  Tue, 16 Oct 2012 15:25:22 -0400
 
@@ -5173,7 +5173,7 @@ git-annex (3.20120315) unstable; urgency=low
 
 git-annex (3.20120309) unstable; urgency=low
 
-  * Fix key directory hash calculation code to behave as it did before 
+  * Fix key directory hash calculation code to behave as it did before
     version 3.20120227 when a key contains non-ascii characters (only
     WORM backend is likely to have been affected).
 
@@ -5243,7 +5243,7 @@ git-annex (3.20120227) unstable; urgency=low
     version of ssh and default annex.sshcaching accordingly.
   * move --from, copy --from: Now 10 times faster when scanning to find
     files in a remote on a local disk; rather than go through the location log
-    to see which files are present on the remote, it simply looks at the 
+    to see which files are present on the remote, it simply looks at the
     disk contents directly.
 
  -- Joey Hess <joeyh@debian.org>  Mon, 27 Feb 2012 12:58:21 -0400
@@ -5294,7 +5294,7 @@ git-annex (3.20120113) unstable; urgency=low
 
   * log: Add --gource mode, which generates output usable by gource.
   * map: Fix display of remote repos
-  * Add annex-trustlevel configuration settings, which can be used to 
+  * Add annex-trustlevel configuration settings, which can be used to
     override the trust level of a remote.
   * git-annex, git-union-merge: Support GIT_DIR and GIT_WORK_TREE.
   * Add libghc-testpack-dev to build depends on all arches.
@@ -5406,7 +5406,7 @@ git-annex (3.20111122) unstable; urgency=low
     information from the git-annex branch. In particular, git annex add
     no longer needs to auto-merge.
   * init: When run in an already initalized repository, and without
-    a description specified, don't delete the old description. 
+    a description specified, don't delete the old description.
   * Optimised union merging; now only runs git cat-file once, and runs
     in constant space.
   * status: Now displays trusted, untrusted, and semitrusted repositories
@@ -5506,9 +5506,9 @@ git-annex (3.20111011) unstable; urgency=low
     of the repository description, which is ugly but otherwise harmless.
   * Add timestamps to trust.log and remote.log too.
   * git-annex-shell: Added the --uuid option.
-  * git-annex now asks git-annex-shell to verify that it's operating in 
+  * git-annex now asks git-annex-shell to verify that it's operating in
     the expected repository.
-  * Note that this git-annex will not interoperate with remotes using 
+  * Note that this git-annex will not interoperate with remotes using
     older versions of git-annex-shell.
   * Now supports git's insteadOf configuration, to modify the url
     used to access a remote. Note that pushInsteadOf is not used;
@@ -5632,7 +5632,7 @@ git-annex (3.20110705) unstable; urgency=low
 
 git-annex (3.20110702) unstable; urgency=low
 
-  * Now the web can be used as a special remote. 
+  * Now the web can be used as a special remote.
     This feature replaces the old URL backend.
   * addurl: New command to download an url and store it in the annex.
   * Sped back up fsck, copy --from, and other commands that often
@@ -5665,7 +5665,7 @@ git-annex (3.20110624) experimental; urgency=low
     cp is still used when copying file from repos on the same filesystem,
     since --reflink=auto can make it significantly faster on filesystems
     such as btrfs.
-  * Allow --trust etc to specify a repository by name, for temporarily 
+  * Allow --trust etc to specify a repository by name, for temporarily
     trusting repositories that are not configured remotes.
   * unlock: Made atomic.
   * git-union-merge: New git subcommand, that does a generic union merge
@@ -5740,7 +5740,7 @@ git-annex (0.20110427) unstable; urgency=low
 
   * Switch back to haskell SHA library, so git-annex remains buildable on
     Debian stable.
-  * Added rsync special remotes. This could be used, for example, to 
+  * Added rsync special remotes. This could be used, for example, to
     store annexed content on rsync.net (encrypted naturally). Or anywhere else.
   * Bugfix: Avoid pipeline stall when running git annex drop or fsck on a
     lot of files. Possibly only occured with ghc 7.
@@ -5903,7 +5903,7 @@ git-annex (0.23) unstable; urgency=low
   * Support ssh remotes with a port specified.
   * whereis: New subcommand to show where a file's content has gotten to.
   * Rethink filename encoding handling for display. Since filename encoding
-    may or may not match locale settings, any attempt to decode filenames 
+    may or may not match locale settings, any attempt to decode filenames
     will fail for some files. So instead, do all output in binary mode.
 
  -- Joey Hess <joeyh@debian.org>  Sat, 12 Mar 2011 15:02:49 -0400
@@ -6134,7 +6134,7 @@ git-annex (0.05) unstable; urgency=low
     on every file being committed/locked.
     (This actually also works around a bug in ghc, that caused
     git-annex 0.04 pre-commit to sometimes corrupt filename being read
-    from git ls-files and fail. 
+    from git ls-files and fail.
     See <http://hackage.haskell.org/trac/ghc/ticket/4493>
     The excessive number of calls made by pre-commit exposed the ghc bug.
     Thanks Josh Triplett for the debugging.)
diff --git a/debian/control b/debian/control
index e8737cde6f..03767c6086 100644
--- a/debian/control
+++ b/debian/control
@@ -1,7 +1,7 @@
 Source: git-annex
 Section: utils
 Priority: optional
-Build-Depends: 
+Build-Depends:
 	debhelper-compat (= 13),
 	ghc (>= 8.4.3),
 	cabal-install,
@@ -101,19 +101,17 @@ Uploaders:
 Standards-Version: 4.2.1
 Vcs-Git: https://salsa.debian.org/haskell-team/git-annex.git
 Vcs-Browser: https://salsa.debian.org/haskell-team/git-annex
-Homepage: http://git-annex.branchable.com/
-XS-Testsuite: autopkgtest
+Homepage: https://git-annex.branchable.com/
 
 Package: git-annex
 Architecture: any
-Section: utils
 Depends: ${misc:Depends}, ${shlibs:Depends},
 	git (>= 1:2.22),
 	netbase,
 	rsync,
 	curl,
 	openssh-client (>= 1:5.6p1)
-Recommends: 
+Recommends:
 	lsof,
 	gnupg,
 	bind9-host,
@@ -132,7 +130,7 @@ Suggests:
 	yt-dlp,
 Breaks: datalad (<< 0.12.3~)
 Description: manage files with git, without checking their contents into git
- git-annex allows managing large files with git, without storing the file 
+ git-annex allows managing large files with git, without storing the file
  contents in git. It can sync, backup, and archive your data, offline
  and online. Checksums and encryption keep your data safe and secure. Bring
  the power and distributed nature of git to bear on your large files with
diff --git a/debian/copyright b/debian/copyright
deleted file mode 120000
index dc5f40a221..0000000000
--- a/debian/copyright
+++ /dev/null
@@ -1 +0,0 @@
-../COPYRIGHT
\ No newline at end of file
diff --git a/debian/copyright b/debian/copyright
new file mode 100644
index 0000000000..7e15439fd4
--- /dev/null
+++ b/debian/copyright
@@ -0,0 +1,845 @@
+Format: https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
+Source: native package
+Upstream-Name: git-annex
+
+Files: *
+Copyright: © 2010-2023 Joey Hess <id@joeyh.name>
+License: AGPL-3+
+
+Files: Assistant/WebApp.hs Assistant/WebApp/* templates/* static/*
+Copyright: © 2012-2017 Joey Hess <id@joeyh.name>
+           © 2014 Sören Brunk
+License: AGPL-3+
+
+Files: doc/special_remotes/external/* 
+Copyright: © 2013 Joey Hess <id@joeyh.name>
+License: GPL-3+
+
+Files: doc/design/external_backend_protocol/git-annex-backend-XFOO
+Copyright: © 2020 Joey Hess <id@joeyh.name>
+License: GPL-3+
+
+Files: Command/Sync.hs
+Copyright: © Joachim Breitner <mail@joachim-breitner.de>
+           © 2011-2020 Joey Hess <id@joeyh.name>
+License: AGPL-3+
+
+Files: Command/List.hs
+Copyright: © 2013 Joey Hess <id@joeyh.name>
+           © 2013 Antoine Beaupré
+License: AGPL-3+
+
+Files: Remote/Ddar.hs
+Copyright: © 2011-2020 Joey Hess <id@joeyh.name>
+           © 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 <id@joeyh.name>
+License: BSD-2-clause
+
+Files: Utility/Attoparsec.hs
+Copyright: 2019 Joey Hess <id@joeyh.name>
+           2007-2015 Bryan O'Sullivan
+License: BSD-3-clause
+
+Files: Utility/GitLFS.hs
+Copyright: © 2019 Joey Hess <id@joeyh.name>
+License: AGPL-3+
+
+Files: Utility/*
+Copyright: 2012-2022 Joey Hess <id@joeyh.name>
+License: BSD-2-clause
+
+Files: doc/logo* */favicon.ico standalone/osx/git-annex.app/Contents/Resources/git-annex.icns
+Copyright: 2007 Henrik Nyh <http://henrik.nyh.se/>
+           2010 Joey Hess <id@joeyh.name>
+	   2013 John Lawrence
+License: icon-license
+  Free to modify and redistribute with due credit, and obviously free to use.
+
+Files: Utility/MD5.hs
+Copyright: 2001 Ian Lynagh
+License: GPL-2
+ The full text of version 2 of the GPL is distributed in
+ /usr/share/common-licenses/GPL-2 on Debian systems.
+
+Files: Annex/DirHashes.hs
+Copyright: © 2010-2017 Joey Hess <id@joeyh.name>
+License: GPL-3+
+
+Files: doc/tips/automatically_adding_metadata/pre-commit-annex 
+Copyright: 2014 Joey Hess <id@joeyh.name>
+           2016 Klaus Ethgen <Klaus@Ethgen.ch>
+License: GPL-3+
+
+Files: static/jquery*
+Copyright: © 2005-2011 by John Resig, Branden Aaron & Jörn Zaefferer
+           © 2011 The Dojo Foundation
+License: Expat or GPL-2
+
+Files: static/*/bootstrap* static/*/glyphicons-halflings*
+Copyright: 2012-2014 Twitter, Inc.
+License: MIT-twitter
+  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: GPL-2
+ The full text of version 2 of the GPL is distributed in
+ /usr/share/common-licenses/GPL-2 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: BSD-3-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.
+ .
+ 3. Neither the name of the author nor the names of his contributors
+    may be used to endorse or promote products derived from this software
+    without specific prior written permission.
+ .
+ THIS SOFTWARE IS PROVIDED BY THE 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: Expat
+ 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: 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/>.
diff --git a/debian/upstream/metadata b/debian/upstream/metadata
new file mode 100644
index 0000000000..544354eeb6
--- /dev/null
+++ b/debian/upstream/metadata
@@ -0,0 +1,3 @@
+---
+Contact: Joey Hess <id@joeyh.name>
+Repository: git://git-annex.branchable.com/

Run locally

More details

Full run details

Historical runs

© 2018-2023 Jelmer Vernooij. File a bug. Source code. Published under the GNU GPLv2 or later.