
* webapp: Detect when upgrades are available, and upgrade if the user desires. (Only when git-annex is installed using the prebuilt binaries from git-annex upstream, not from eg Debian.) * assistant: Detect when the git-annex binary is modified or replaced, and either prompt the user to restart the program, or automatically restart it. * annex.autoupgrade configures both the above upgrade behaviors. * Added support for quvi 0.9. Slightly suboptimal due to limitations in its interface compared with the old version. * Bug fix: annex.version did not get set on automatic upgrade to v5 direct mode repo, so the upgrade was performed repeatedly, slowing commands down. * webapp: Fix bug that broke switching between local repositories that use the new guarded direct mode. * Android: Fix stripping of the git-annex binary. * Android: Make terminal app show git-annex version number. * Android: Re-enable XMPP support. * reinject: Allow to be used in direct mode. * Futher improvements to git repo repair. Has now been tested in tens of thousands of intentionally damaged repos, and successfully repaired them all. * Allow use of --unused in bare repository. # imported from the archive
15 lines
891 B
Markdown
15 lines
891 B
Markdown
While I said I was done with fsck scheduling yesterday, I ended up adding
|
|
one more feature to it today: Full anacron style scheduling. So a fsck can
|
|
be scheduled to run once per week, or month, or year, and it'll run the
|
|
fsck the next time it's available after that much time has passed. The nice
|
|
thing about this is I didn't have to change Cronner *at all* to add this,
|
|
just improved the Recurrance data type and the code that calculates when
|
|
to run events.
|
|
|
|
Rest of the day I've been catching up on some bug reports. The main bug I
|
|
fixed caused git-annex on Android to hang when adding files. This turns out
|
|
to be because it's using a new (unreleased) version of git, and
|
|
`git check-attr -z` output format has changed in an incompatable way.
|
|
|
|
I am currently 70 messages behind, which includes some ugly looking bug
|
|
reports, so I will probably continue with this over the next couple days.
|