b6d46c212e
* unannex, uninit: Avoid committing after every file is unannexed,
for massive speedup.
* --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
file upload/download starts.
* webapp: Automatically install Nautilus integration scripts
to get and drop files.
* tahoe: Pass -d parameter before subcommand; putting it after
the subcommand no longer works with tahoe-lafs version 1.10.
(Thanks, Alberto Berti)
* forget --drop-dead: Avoid removing the dead remote from the trust.log,
so that if git remotes for it still exist anywhere, git annex info
will still know it's dead and not show it.
* git-annex-shell: Make configlist automatically initialize
a remote git repository, as long as a git-annex branch has
been pushed to it, to simplify setup of remote git repositories,
including via gitolite.
* add --include-dotfiles: New option, perhaps useful for backups.
* Version 5.20140227 broke creation of glacier repositories,
not including the datacenter and vault in their configuration.
This bug is fixed, but glacier repositories set up with the broken
version of git-annex need to have the datacenter and vault set
in order to be usable. This can be done using git annex enableremote
to add the missing settings. For details, see
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
alternative way that works with the non-POSIX fish shell, as well
as POSIX shells.
# imported from the archive
22 lines
1.3 KiB
Markdown
22 lines
1.3 KiB
Markdown
When I wasn't dealing with the snowstorm today, I was fixing more bugs.
|
|
Rather serious bugs.
|
|
|
|
One actually involved corruption to git-annex's location tracking info, due
|
|
to a busted three-way merge. Takes an unusual set of circumstances for that
|
|
bug to be triggered, which is why it was not noticed before now. Also,
|
|
since git-annex is designed to not trust its location tracking info, and
|
|
recover from it becoming inconsistent, someone could have experienced the
|
|
bug and not really noticed it. Still it's a serious problem and I'm in debt
|
|
to user a-or-b for developing a good test case that let me reproduce it and
|
|
fix it. (Also added to the test suite.)
|
|
[[This is how to make a perfect bug report|bugs/Annex_thinks_file_exists_afer_being_dropped]]
|
|
|
|
Another bug made `git add; git commit` cause data loss in direct mode.
|
|
I was able to make that not lose data, although it still does something
|
|
that's unlikely to be desired, unless the goal is to move a file from an
|
|
annexed direct mode file to having its entire contents stored in git.
|
|
|
|
Also found a bug with sync's automatic resolution of git conflicts. It
|
|
failed when two repositories both renamed a file to different names.
|
|
I had neglected to explicitly `git rm` the old file name, which is
|
|
necessary to resolve such a conflict.
|