Captured from the log :
TRACE : DownloadManager::applyFinished : Apply 1/1 finished
INFO : PatchOperation::applyData : Patch succeeded path_diff2.txt

Recent change to xdelta licensing, the apparition of the brotli compressor and new goals of the Stargate Network project are leading me to create a better version of this library.

Here is the TODO list:

• brotli encoder/decoder (static linking)
• xdelta3 encoder/decoder (static linking)
• lzma encoder/decoder (static linking)
• refactoring

Some stats could be useful

• total amount of checked/downloaded/applied bytes
• time to check/download/apply
• number of failures

It's a bit late, but here is the version that compiles fine (the one that you modified by taking control of my computer) : https://dl.dropboxusercontent.com/u/28570337/QtUpdateSystem-mingw.zip

Is there an option to check local repo integrity if a file or folder is missing ?

Is it possible to have an apps to call and get output return for calling from managed apps.

Add a function to the Updater to create a copy of the repository in a safe way.

Actually there is the updatingTo variable, but if there is multiple update step, the restart will sometimes require a complete download.

The probably best way to fix this issue if to keep a more complete state of the current download.

where xdelta.exe and lama.exe ?

http://tukaani.org/xz/ provide liblzma in the public domain. So there is no reason to not embed it directly
The only remaining dependency would be xdelta3 that support lzma compression

Actually folders that are created to store files aren't managed

Actually, there is no way to check if to package that the creator says it go to the same state actually go to the same state

• Ability to add a new revision without having to care about the previous revision

Actually, exception are mostly thrown QString.
Having a special class for throwing exceptions would allow feature like :

• Detect what as gone wrong with ease and apply the best fix automatically
• Log the exception, the related context, etc.
  ...

Actually not setting the temporary directory to the packager or the updater leads to having temporary files created in the current program directory.
This is probably not the best behavior

Is it possible to push a new repo version on remote server ?

https://github.com/richgel999/lzham_codec

Add the capability to update a directory to another directory.
For example, if you want to make a application that use this lib to autoupdate itself.

On local side, the status file should maintain a list of managed files
On repository side, metadata information must contains a list of all files and not just a list of what have changed.

Actually, fixing updates errors requires re download of often previously downloaded metadata files.
Caching them until the update finished could speed up fixing times a lot. Specially when there is a lot of small files than have failed