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
23 lines
1.1 KiB
Markdown
23 lines
1.1 KiB
Markdown
Spent all day on some horrible timestamp issues on legacy systems.
|
|
|
|
On FAT, timestamps have a 2s granularity, which is ok, but then Linux adds
|
|
a temporary higher resolution cache, which is lost on unmount. This
|
|
confused git-annex since the mtimes seemed to change and it had to
|
|
re-checksum half the files to get unconfused, which was not good.
|
|
I found a way to use the inode sentinal file to detect when on FAT
|
|
and put in a workaround, without degrading git-annex everywhere else.
|
|
|
|
On Windows, time zones are a utter disaster; it changes the mtime it reports
|
|
for files after the time zone has changed. Also there's a bug in the
|
|
haskell time library which makes it return old time zone data after a time
|
|
zone change. (I just finished developing a fix for that bug..)
|
|
|
|
Left with nothing but a few sticks, I rubbed them together, and
|
|
actually found a way to deal with this problem too. Scary details in
|
|
[[bugs/Windows_file_timestamp_timezone_madness]]. While I've implemented
|
|
it, it's stuck on a branch until I find a way to make git-annex notice when
|
|
the timezone changes while it's running.
|
|
|
|
----
|
|
|
|
Today's work was sponsored by Svenne Krap.
|