e213ef310f
* Fix minor FD leak in journal code. Closes: #754608 * direct: Fix handling of case where a work tree subdirectory cannot be written to due to permissions. * migrate: Avoid re-checksumming when migrating from hashE to hash backend. * uninit: Avoid failing final removal in some direct mode repositories due to file modes. * S3: Deal with AWS ACL configurations that do not allow creating or checking the location of a bucket, but only reading and writing content to it. * resolvemerge: New plumbing command that runs the automatic merge conflict resolver. * Deal with change in git 2.0 that made indirect mode merge conflict resolution leave behind old files. * sync: Fix git sync with local git remotes even when they don't have an annex.uuid set. (The assistant already did so.) * Set gcrypt-publish-participants when setting up a gcrypt repository, to avoid unncessary passphrase prompts. This is a security/usability tradeoff. To avoid exposing the gpg key ids who can decrypt the repository, users can unset gcrypt-publish-participants. * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet exist, since it is not automatically created for Gnome 3 users. * Windows: Move .vbs files out of git\bin, to avoid that being in the PATH, which caused some weird breakage. (Thanks, divB) * Windows: Fix locking issue that prevented the webapp starting (since 5.20140707). # imported from the archive
18 lines
892 B
Markdown
18 lines
892 B
Markdown
Pushed out a new release today, fixing two important bugs, followed by a
|
|
second release which fixed the bugs harder.
|
|
|
|
Automatic upgrading was broken on OSX. The webapp will tell you upgrading
|
|
failed, and you'll need to manually download the .dmg and install it.
|
|
|
|
With help from Maximiliano Curia, finally tracked down a bug I have been
|
|
chasing for a while where the assistant would start using a lot of CPU
|
|
while not seeming to be busy doing anything. Turned out to be triggered by
|
|
a scheduled fsck that was configured to run once a month with no particular
|
|
day specified.
|
|
|
|
That bug turned out to affect users who first scheduled such a fsck job
|
|
after the 11th day of the month. So I expedited putting a release out to
|
|
avoid anyone else running into it starting tomorrow.
|
|
|
|
(Oddly, the 11th day of this month also happens to be my birthday. I did not
|
|
expect to have to cut 2 releases today..)
|