[Dar-news] dar release 2.7.19 is available

Hi,

source package and windows binary for release 2.7.19 are available at:

https://sourceforge.net/projects/dar/files/dar/2.7.19

As an alternative to Sourceforge you can fetch source and windows
binary packages but also fully featured dar_static binaries for Linux/x86_64
from the _low bandwidth_ ftp and https servers at:

ftp://ftp.edrusb.org/dar.linux.free.fr/Releases
https://dar.edrusb.org/dar.linux.free.fr/Releases

Package signatures are available at:

http://dar.linux.free.fr/sign/v2.7.19

Author's keys are available on public key servers and on dar website:

http://dar.linux.free.fr/doc/authentification.html

Release 2.7.19 brings several bug fixes which are detailed in the extract
of the Changelog below.

Thanks to RSmain at github for findings and feedback about script launching
(-E/-F/-~ options) under Cygwin and thanks to logging-synchronous@github 
for
bug report.


Cheers,
Denis Corbin

-------
from 2.7.18 to 2.7.19
- fixed the trailing slash support in path, that was broken by commit
  503326bf8735d8eab48d4ff0ab9c000ffa031dec added at version 2.7.17
- leveraging RSmain@github's feedback to modify dar windows packaging for
  -E/-F/-~ options to work under Cygwin. See the updated FAQ for more
  details.
- Adding documentation on dar's man page on the way dar uses stdin, stdout
  and stderr.
- removing too restrictive control of compression level inside libdar,
  dar CLI already does that and libzstd/libz/libbz2/... also do that and
  triggers an error in case of invalid value.
- handling the case where a binary patch is also a hard link: at 
restoration
  time, the inode is tried to be patched again when a second hard link is
  met, which leads dar to report an error and exiting with code 5 (while
  restoration was fine).
- fixing dead-lock condition met when dar is about to end due to the 
fact two
  threads unexpectedly access the same object at the same time (which 
object
  is not designed for concurrent accesses). This occurred in sequential 
mode
  with parallel compression and parallel deciphering after data has been
  restored, leading dar in dead-lock situation (sleeping forever).
- fixing bug met in sequential read mode when retrieving archive summary
  information (dar asked for the last slice and could not find it).
- In some rare conditions gpgme fails upon memory allocation failure, 
leading
  dar to abort but without displaying the root cause. Error message now 
shows
- fixed bug in sar::truncate() which lead dar to create a hole in the slice
  numbering when one of the last file to backup was so badly compressed 
that
  re-saving it uncompressed lead to remove enough slices for the rest of 
the
  backup to need less slices that reached at that time (bug detected with
  slices of 1024 bytes). Such archive are still readable in sequential
  read mode but end with dar asking for the missing slices at the end of
  the process.
- fixing bug met in sequential-read mode lead dar to try restoring file a
  second time from differential backup having entries marked as deleted,
  which fails (reporting CRC mismatch) as the data of the file is no more
  accessible due to the sequential reading mode.