
* 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
21 lines
1.1 KiB
Markdown
21 lines
1.1 KiB
Markdown
After making a release yesterday, I've been fixing some bugs in the
|
|
webapp, all to do with repository configuration stored on the git-annex
|
|
branch. I was led into this by a strange little bug where the webapp stored
|
|
configuration in the wrong repo in one situation. From there, I noticed
|
|
that often when enabling an existing repository, the webapp would stomp on
|
|
its group and preferred content and description, replacing them with
|
|
defaults.
|
|
|
|
This was a systematic problem, it had to be fixed in several places. And
|
|
some of the fixes were quite tricky. For example, when adding a ssh
|
|
repository, and it turns out there's already a git-annex repository at the
|
|
entered location, it needs to avoid changing its configuration. But also,
|
|
the configuration of that repo won't be known until after the first git
|
|
pull from it. So it doesn't make sense to show the repository edit form
|
|
after enabling such a repository.
|
|
|
|
Also worked on a couple other bugs, and further cleaned up the [[bugs]]
|
|
page. I think I am finally happy with how the bug list is displayed,
|
|
with confirmed/moreinfo/etc tags.
|
|
|
|
Today's work was sponsored by François Deppierraz.
|