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
24 lines
1.4 KiB
Markdown
24 lines
1.4 KiB
Markdown
Went out and tried for the second time to record a screencast demoing
|
|
setting up syncing between two computers using just Jabber and a cloud
|
|
remote. I can't record this one at home, or viewers would think git-annex
|
|
was crazy slow, when it's just my dialup. ;) But once again I encountered
|
|
bugs, and so I found myself working on progress bars today, unexpectedly.
|
|
|
|
Seems there was confusion in different parts of the progress bar code
|
|
about whether an update contained the total number of bytes transferred, or
|
|
the delta of bytes transferred since the last update. One way this bug
|
|
showed up was progress bars that seemed to stick at 0% for a long time.
|
|
Happened for most special remotes, although not for rsync or git remotes.
|
|
In order to fix it comprehensively, I added a new BytesProcessed data type,
|
|
that is explicitly a total quantity of bytes, not a delta. And checked and
|
|
fixed all the places that used a delta as that type was knitted into
|
|
the code.
|
|
|
|
(Note that this doesn't necessarily fix every problem with progress bars.
|
|
Particularly, buffering can now cause progress bars to seem to run ahead
|
|
of transfers, reaching 100% when data is still being uploaded. Still,
|
|
they should be a lot better than before.)
|
|
|
|
I've just successfully run through the Jabber + Cloud remote setup process
|
|
again, and it seems to be working great now. Maybe I'll still get the
|
|
screencast recorded by the end of March.
|