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
20 lines
1 KiB
Markdown
20 lines
1 KiB
Markdown
These themed days are inaverdent, but it happened again: Nearly everything
|
|
done today had to do with encoding issues.
|
|
|
|
The big news is that it turned out everything written to files in the
|
|
git-annex branch had unicode characters truncated to 8 bits. Now fixed so
|
|
you should always get out the same thing you put in, no matter what
|
|
encoding you use (but please use utf8). This affected things like storing
|
|
repository descriptions, but worse, it affected metadata. (Also preferred
|
|
content expressions, I suppose.)
|
|
|
|
With that fixed, there are still 7 source files left that use Char8 libraries.
|
|
There used to be more; nearly every use of those is a bug. I looked over
|
|
the remaining uses of it, and there might be a problem with Creds using it.
|
|
I should probably make a push to stamp out all remaining uses of Char8.
|
|
|
|
Other encoding bugs were less reproducible.
|
|
|
|
And just now, Sören made some progress on
|
|
[[bugs/Bootstrap3_icons_missing_on_Android]] ... and my current theory
|
|
is this is actually caused by an encoding issue too.
|