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
15 lines
832 B
Markdown
15 lines
832 B
Markdown
Pushed out a minor release of git-annex today, mostly to fix build problems
|
|
on Debian. No strong reason to upgrade to it otherwise.
|
|
|
|
Continued where I left off with the Git.Destroyer. Fixed quite a lot of
|
|
edge cases where git repair failed due to things like a corrupted .git/HEAD
|
|
file (this makes git think it's not in a git repository), corrupt
|
|
git objects that have an unknown object type and so crash git hard, and
|
|
an interesting failure mode where git fsck wants to allocate 116 GB of
|
|
memory due to a corrupted object size header. Reported that last to the git
|
|
list, as well as working around it.
|
|
|
|
At the end of the day, I ran a test creating 10000 corrupt git
|
|
repositories, and **all** of them were recovered! Any improvements will
|
|
probably involve finding new ways to corrupt git repositories that my code
|
|
can't think of. ;)
|