Changes
Revision history, newest first. The authoritative list is the
Changes file in the distribution.
0.002.2 — 18 November 2026
Bug fixes
- A server repo created with
--trash-days 0pruned its trash after 30 days, while a client's"local_trash_days": 0kept its trash forever. 0 now means “keep forever” on both sides.filesync-admin repo showprints “kept forever” for such a repo instead of “0 days”. filesync-admin repo showprinted “0 files / 0%” for a repo whose deletion limits are switched off, which read as “nothing may be deleted”. It now says “no file limit”, “no percentage limit”, or “none (any number of deletions)” when both are off.filesync-admin repo create --max-delete-percentaccepted values over 100. It now refuses anything above 100, and so does the deletion check when a policy file holds such a value.- A bad argument was reported in
Params::Validate::Strict's own English, naming the internal parameter. It is now a catalogued message that names the option that was typed:--trash-days must be at least 0, not -1. - A directory that became a file could not be synced if it still held
an ignored file (a
.DS_Store, say): the sync failed with “Cannot replace non-empty directory”, then and on every later run. The directory, with whatever the sync does not track, now goes to the trash and the file takes its place. - An error the server sent a client named where the server keeps its
files. A path in the master is now given relative to the repo, and any
other server path starts with
[server root]. The server's log is written the same way; the journal keeps the full paths. - The server accepted a
mkdirrequest for a path whose planned action was a conflict the client's file had won, which no client sends. Such a request is now refused like any other outside the plan.
Documentation
filesync-admin help, the POD and this website describe therepo createoptions, and say that a--max-deletesor--max-delete-percentof 0 switches that deletion limit off.- Both deletion limits are inclusive, and the percentage limit rounds down but always allows one file; the help, the POD and this website now say so.
filesync-serverdocuments its exit status.
0.002.1 — 15 November 2026
Enhancements
- Block deltas are much faster to compute. A changed file of 8 MiB or more with no blocks in common took about 45 seconds to diff; it now takes about 3. Signatures are computed about twice as fast. The wire format is unchanged, so old and new clients and servers still work together.
- JSON now goes through
JSON::MaybeXS(a new dependency), which installs and usesCpanel::JSON::XSwherever there is a compiler. Reading a 100,000-file manifest took about 15 seconds withJSON::PPand takes under half a second withCpanel::JSON::XS. Pure-Perl installs still work, onJSON::PP, and either side of a sync may use either backend. - Paths read back from JSON as hash keys (manifests are keyed by path)
kept Perl's UTF-8 flag, so a file test on a non-ASCII name looked for a
differently encoded file.
verifysilently left such files out of its random sample. Keys are now byte strings, like values.
Bug fixes
- On Windows, a client whose session ended early (any error mid-sync) hung for ever instead of reporting the error: the server or ssh it started inherited the client's end of its own input pipe, so it never saw end of file. The client's pipe ends are no longer inheritable, and a server or ssh that has not exited 30 seconds after the session ends is stopped.
filesync settingson Windows named an environment variable in the spelling it was looked up with (App__FileSync__ssh_identity) rather than the one the environment holds (APP__FILESYNC__SSH_IDENTITY).
0.002.0 — 4 November 2026
Enhancements
- Created this website.
filesync sync --quietprints nothing for a repo where nothing happened, instead of an all-zero summary and transfer line, so a cron job that finds nothing to do stays silent.
Bug fixes
- The system-locale tests in
t/locales.tfailed on Windows: they passed a multi-line child program toperl -e, which Windows cut at the first newline, and importedLC_MESSAGES, which Windows' POSIX lacks. The child is now a script file and falls back toLC_CTYPE.
0.001.5 — 25 October 2026
Bug fixes
Log::Abstraction0.36 is now required, because the client logs its run summary as structured fields in a trailing hashref. An older copy, which the installer accepted, turned that intosync finishedHASH(0x...)in the log file and an empty entry in an array logger, so the counts were lost and the settings test failed its seven logger assertions.
0.001.4 — 25 October 2026
Bug fixes
t/ssh.t: the stand-in for ssh now names the perl running the tests on its first line instead of#!/usr/bin/env perl. The transport starts that file as a program, so the kernel picked whichever perl came first onPATH— on a smoke tester the system perl, which cannot see the modules the build installed — and thefilesync-serverit then ran died withCan't locate Params/Validate/Strict.pmagainst a build that never lacked it. The Windows wrapper already named$^X.
Tests
t/ssh.tchecks the interpreter line of the stand-in it writes, so thePATH-dependent first line cannot come back unnoticed.
0.001.3 — 25 October 2026
Documentation
- More improvements.
Bug fixes
- Bump the minimum
Config::Abstraction.
0.001.2 — 24 October 2026
Bug fixes
filesync-admin repo createnames the server root and the directory that blocks it when the root cannot be written, and says to chown it to the running account or use--rootelsewhere. It used to report onlyPermission deniedagainst a path below the root.- That advice is given only when a directory really is unwritable, so a full disk or a root that is a file keeps its own error.
Documentation
- The examples are split by machine — what to run on the server, on each client, and from cron — and keep the master in a home directory, so nothing needs sudo.
- What a
/srv/filesyncroot needs instead, the wrapper that adds--roottofilesync-server, and the ssh key the first sync requires. - The backup and restore commands follow the example's master layout, and make the backup directory before cron mirrors into it.
- The synopsis creates the repo first, so it runs as printed.
0.001.1 — 24 October 2026
Bug fixes
- Build: test on Windows with Perl 5.42 again. Its
B::Hooks::EndOfScopefaults at exit, so the plain-Perl hook is used there. filesync,filesync-serverandfilesync-adminselect that hook for themselves on 5.42 for Windows, so it no longer has to be set to run them; an implementation already in the environment is left alone. A test checks the choice in a child process that starts without the variable.- Security: an ssh server of the form
-v@host(or a program name starting with-) is refused; it was passed to ssh as an option. - Security: client and repo names that are not plain ids
(
../x, over 64 characters) are refused by the server, admin and client. - Server: a conflict copy is kept under the planned name whether or not the client names it, and any other name is refused; acks are accepted only for actions the client applies; get validates its offset and caps its size; an upload larger than announced is refused and discarded.
- Ignore: building a matcher no longer modifies the caller's pattern list
(which turned
!keep.tmpintokeep.tmpand could delete the file remotely);/topanchors to the root;build/matches at any depth. - Trash: same-day versions sort numerically and are no longer capped at
.99. Each client repo has its own local trash; restore still finds files in the old shared one. - Admin:
journal_readworks when the server root contains spaces. - All messages come from a catalogue
(
App::FileSync::I18N::en) and can be translated; errors no longer show Perl file and line numbers unlessFILESYNC_TRACEis set. - Internals: new
Args,Base,Constants,I18N,IOandPlatformmodules; private subs are enforced with Sub::Private; full POD. - Removed the unused POSIX and Encode prerequisites.
- Build: requires Perl 5.14; declares ExtUtils::MakeMaker 6.64 as a
configure prerequisite so test prerequisites are honoured; the gzip and (on
macOS) gtar dist settings are now actually applied;
t/andxt/are not indexed; bug tracker link added. $VERSIONis a version object (version->declare), so every tool reads 0.001.1 as the dotted version v0.1.1.- Every module and program carries the same GPL v2 licence notice.
0.001.0 — 23 October 2026
- First draft.