Accepted git-annex 5.20140210~bpo70+2 (source amd64)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Thu, 20 Feb 2014 22:56:45 +0000
Source: git-annex
Binary: git-annex
Architecture: source amd64
Version: 5.20140210~bpo70+2
Distribution: wheezy-backports
Urgency: medium
Maintainer: Joey Hess <joeyh@debian.org>
Changed-By: Joey Hess <joeyh@debian.org>
Description:
git-annex - manage files with git, without checking their contents into git
Closes: 737476 737480
Changes:
git-annex (5.20140210~bpo70+2) wheezy-backports; urgency=medium
.
* Updating backport to newest release.
* Remaining differences in this backport:
- No webdav special remote support.
- Test suite is not built into git-annex as it now uses haskell-tasty,
which is not yet backported.
- No skein hash support.
.
git-annex (5.20140210) unstable; urgency=medium
.
* --in can now refer to files that were located in a repository at
some past date. For example, --in="here@{yesterday}"
* Fixed direct mode annexed content locking code, which is used to
guard against recursive file drops.
* This is the first beta-level release of the Windows port with important
fixes (see below).
(The webapp and assistant are still alpha-level on Windows.)
* sync --content: Honor annex-ignore configuration.
* sync: Don't try to sync with xmpp remotes, which are only currently
supported when using the assistant.
* sync --content: Re-pull from remotes after downloading content,
since that can take a while and other changes may be pushed in the
meantime.
* sync --content: Reuse smart copy code from copy command, including
handling and repairing out of date location tracking info.
Closes: #737480
* sync --content: Drop files from remotes that don't want them after
getting them.
* sync: Fix bug in automatic merge conflict resolution code when used
on a filesystem not supporting symlinks, which resulted in it losing
track of the symlink bit of annexed files.
* Added ways to configure rsync options to be used only when uploading
or downloading from a remote. Useful to eg limit upload bandwidth.
* Fix initremote with encryption=pubkey to work with S3, glacier, webdav,
and external special remotes.
* Avoid building with DAV 0.6 which is badly broken (see #737902).
* Fix dropping of unused keys with spaces in their name.
* Fix build on platforms not supporting the webapp.
* Document in man page that sshcaching uses ssh ControlMaster.
Closes: #737476
* Windows: It's now safe to run multiple git-annex processes concurrently
on Windows; the lock files have been sorted out.
* Windows: Avoid using unix-compat's rename, which refuses to rename
directories.
* Windows: Fix deletion of repositories by test suite and webapp.
* Windows: Test suite 100% passes again.
* Windows: Fix bug in symlink calculation code.
* Windows: Fix handling of absolute unix-style git repository paths.
* Android: Avoid crashing when unable to set file mode for ssh config file
due to Android filesystem horribleness.
.
git-annex (5.20140127) unstable; urgency=medium
.
* sync --content: New option that makes the content of annexed files be
transferred. Similar to the assistant, this honors any configured
preferred content expressions.
* Remove --json option from commands not supporting it.
* status: Support --json.
* list: Fix specifying of files to list.
* Allow --all to be mixed with matching options like --copies and --in
(but not --include and --exclude).
* numcopies: New command, sets global numcopies value that is seen by all
clones of a repository.
* The annex.numcopies git config setting is deprecated. Once the numcopies
command is used to set the global number of copies, any annex.numcopies
git configs will be ignored.
* assistant: Make the prefs page set the global numcopies.
* Add lackingcopies, approxlackingcopies, and unused to
preferred content expressions.
* Client, transfer, incremental backup, and archive repositories
now want to get content that does not yet have enough copies.
* Client, transfer, and source repositories now do not want to retain
unused file contents.
* assistant: Checks daily for unused file contents, and when possible
moves them to a repository (such as a backup repository) that
wants to retain them.
* assistant: annex.expireunused can be configured to cause unused
file contents to be deleted after some period of time.
* webapp: Nudge user to see if they want to expire old unused file
contents when a lot of them seem to be piling up in the repository.
* repair: Check git version at run time.
* assistant: Run the periodic git gc in batch mode.
* added annex.secure-erase-command config option.
* test suite: Use tasty-rerun, and expose tasty command-line options.
* Optimise non-bare http remotes; no longer does a 404 to the wrong
url every time before trying the right url. Needs annex-bare to be
set to false, which is done when initially probing the uuid of a
http remote.
* webapp: After upgrading a git repository to git-annex, fix
bug that made it temporarily not be synced with.
* whereis: Support --all.
* All commands that support --all also support a --key option,
which limits them to acting on a single key.
Checksums-Sha1:
2ded3d01b0c2228427a38920be52beb5a06ed3e7 3256 git-annex_5.20140210~bpo70+2.dsc
9f933437d5372271ee11b5cf6e9cfae5006bea89 5703073 git-annex_5.20140210~bpo70+2.tar.gz
5d94b821c3186c18abc0f3d7aea5eeb8c97c91cb 10429746 git-annex_5.20140210~bpo70+2_amd64.deb
Checksums-Sha256:
38d3825c421ef6191007cbf664fdcbc333c8bd09e3b4c99114e466013e5643fe 3256 git-annex_5.20140210~bpo70+2.dsc
6fb932a883b37b206f813277ce722e0c923853bc8144775839d66d158715d57c 5703073 git-annex_5.20140210~bpo70+2.tar.gz
086eafbbc526093a2e76746e5b85ab363e9526d835d20e1b2c37613a0d25d8ea 10429746 git-annex_5.20140210~bpo70+2_amd64.deb
Files:
2562c63c506c48f0edb5dee239dff968 3256 utils optional git-annex_5.20140210~bpo70+2.dsc
85c0ef5aabbe42e51e6b0e1aa0e7dc90 5703073 utils optional git-annex_5.20140210~bpo70+2.tar.gz
51dffb84e32cccd5c847e628cefa4f8d 10429746 utils optional git-annex_5.20140210~bpo70+2_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQIVAwUBUwbFRskQ2SIlEuPHAQiL8Q/+OCz29ssENAJXBzhFukwTikIskBqPGfUx
V1KLRD0WNSRzms+MPV/nX3WQUosUCAaJDbF7WquBCxW1ZoEvLWeBFb72+laHP8Jr
F3e2/0l4tBHBlVBc3jVKC3zUQ4wmt3PLdSzFJTNFCf5bpiLcfVwPUTVZ+hXdb2e6
8qHPG9tSHT4QQ/UYOi1wOCSGX98VTt3KbXGteMtybFHRZ+bG8fjRa7iWRTWKx6KK
bMhNX8Yg+cqhewGewPC4h6O0TXS+BIoviF1SHIBB+ftGXq+n9xL3xowSLxpHcUGw
4yZb2oC5Qiuc4onG8XBxM5erioW7bZ/UdZguPafpizD4KlyPZRKnBw2SQJNKiOLp
fj2rgBCANaCK92kcAlSTrNxA0jexF2CeLoRIpx8WRpkTHhNG16WO1ir4x7SkZla9
ZZ+Cg6sIKXce/pmj25bqGzwGMP/V2QoY28377JqD+d07n0MU1Ql7CfFEMkNzihJy
ixiZ5O192DueM7HPPkYLB9vlEguEBC3PtjyUdPn24z0GJd0utupnKCM/AEHqsD9T
cFWQ29amyVPhMSC1DNe6sEKUE+k7Q8JdSN3bS9120wh+d/cf8DL58fNPFFwc60d2
3cZA3XYBDSatNvBUeLmisjL1kpuMpJAzpkkFH2/u/Ef6QbyJnj1ovE3MPe/EoqQD
0SXPvhztsPI=
=o+y0
-----END PGP SIGNATURE-----
Reply to: