Changelog:
from 2.4.9 to to 2.4.10
- fixing libdar about dar_manager database corruption that occurred when
deleting the first archive of a base containing a plain file only
existing in that first archive.
- Added code to cleanup databases instead of aborting and reporting
that previously described type of database corruption.
- Added feature when comparing archive with filesystem in order to report
the offset of the first difference found in a file. This was necessary to
help solving the following bug:
- fixed bug in sparse file detection mechanism that could lead in some very
particular (and rare) situations to the loss of one byte from file being
saved. In that case testing the archive reported a CRC error for that
file. So if you keep testing achives in your backup process and have not
detect any problem, you can then keep relying on your old backups. This
bug also expressed when merging archives: dar aborted and reported that a
merged file had a different CRC than the one stored in the archive of
reference.
from 2.4.8 to 2.4.9
- fixed bug: during differential backup dar saved unchanged hard linked inode
when a hard link on that inode was out of the -R root directory. This also
has the effect to always save files with long names on NTFS filesystems (!)
- Adapted patch provided by Kevin Wormington (new messages displayed)
- Fixed syntax error in configure script about execinfo detection
- Removed unused AM_ICONV macro from configure script
- fixed bug met under Cygwin when auxiliary test command failed to link when
libgcrypt was not available.
- updated mini-howto by Grzegorz Adam Hankiewicz
- updating French message translations
- restricted security warning for plain files and hard linked plain files
- fixed display bug in dar_cp when manipulating files larger than 2 GB
- fixed SEGFAULT met when adding to a dar_manager database an archive which
base name is an empty string
- improved error message, reporting the -B included file in which a syntax error
has been met
- modified dar_manager database to consider both ctime and mtime as timestamp
value for data of saved files. This suppresses the warning about badly ordered
archives in database when at some files have been restores from a old
backup.
from 2.4.7 to 2.4.8
- documentation fixes and updates
- improved database listing efficiency
- reduced memory usage of the caching layer in libdar
- fixed self reported bug caused by memory allocation failure
- fixed a SIGSEGV caused by double free in dar_xform when syntax error is
met on command-line
- dar_xform was not able to properly transform archive generated by dar older
than release 2.4.0
- fixed bug that lead dar be unable to remove a directory at restoration time
- replaced old remaining "bcopy" occurrence by a call to memcpy
- fixed compilation warning under ArchLinux
- fixed crash met while creating a backup with on-fly isolation
- fixed libdar behavior when reading a strongly corrupted encrypted archive
from 2.4.6 to 2.4.7
- fixing memory allocation bug in crc class, that lead glibc aborting dar
- reviewed code and replaced some remaining occurences of bzero/bcopy by
their recommended replacement version
- fixed compilation problem under Solaris
- fixed bug that could lead a file to be wrongly reported as different from the
one on filesystem, when that file has been changed while it was saved, then
saved a second time but has its size modified since the first time it was
saved.
from 2.4.5 to 2.4.6
- fixed bug met while interrupting compressed archive creation, the resulting
archive was only readable in --sequential-read mode
- fixed bug met while reading an interrupted archive in sequential reading
mode. It lead dar to not release some objects from memory at the end of
the operation, which displayed an ugly error message from libdar selfcheck
routine.
- fixed message reporting unknown system group when converting gid to name
(was reporting unknow "user" instead of unknown "group")
- removing the $Id:$ macro from file as we moved from CVS to GIT
- updating package to distribute Patrick Nagel's scripts and documentation
- updated URL pointing to Patrick Nagel's web site
- updating documentation describing how to get source code from GIT (no more
from CVS)
- fixed typo in configure.ac
- added info on how to build a brand-new dar tarball from source in GIT
- modifies the end of messages shown by -h option to point to man page for
more _options_ rather than _details_
- replaced − in the HTML generated documentation by a standard ASCII dash
- fixed alignement bug in CRC calculation that lead libdar based application to
crash on sparc-based systems.
from 2.4.4 to 2.4.5
- updated sample scripts to be compatible with dar's --min-digit option
- added missing included file to be able to compile with gcc-4.7.0
- removing an unused variable in filtre.cpp
- fixed a display bug when comparing archive with filesystem, leading to a
segmentation fault (%S in place of %i in mask)
- fixed bug leading dar to not restore some directories from differential
backups when they are absent in the filesystem
- fixed bug that show a "uncaught exception" message at the end of archive
listing for dar shared binaries only, compiled in infinint mode, under
ArchLinux
- updated the configure script to link with libexecinfo when available
- added possibility to disable the use of execinfo in libdar thanks to the
new --disable-execinfo option for the ./configure script
- added Andreas Wolff patch to fix bug under Cygwin (segfault on program
termination).
from 2.4.3 to 2.4.4
- fixed man pages in the NAME section: added whatis entry
- fixed segfault: in the internal error reporting code (delete[] in place of
free())
- fixed bug: dar_manager was not able to read properly the latest generated
databases version when having Extended Attributes recorded for some files
- avoided reporting unreleased memory block when compilation optimization
have been used (dar, dar_manager, dar_cp, dar_slave, dar_xform do all
reported unreleased memory when gcc optimization was used in "infinint" mode)
from 2.4.2 to 2.4.3
- fixed absurd compilation warning about possibly uninitialized variable
- added -ai switch to dar_manager to disable warning about improper file order
in database.
- fixed bug met while changing order of archives in a dar_manager database
- avoiding concurrent use of -p and -Q options, error message shown in that
situation.
- modified slice overwriting detection code to use a single atomic system call
to create a new slice
- replaced delete by delete[] for conversion routine of user/group to uid/gid
- added the possibility to disable speed optimization for large directories
- added memory troubleshooting option --enable-debug-memory
- simplified class CRC implementation
- fixed failed memory release upon exception thrown in class deci
- modified tlv, tlv_list classes and ea_filesystem routines to not require
any corresponding temporary objects in libdar (saves a few new/delete calls)
- fixed silent bug in tlv class: due to the absence of copy constructor and
destructor, some memory was not released and referred after the corresponding
object's destruction
- modified generic_file class to avoid temporary crc objects
- fixed bug in header class that lead unreleased field (this class lacked a
destructor), memory impact was however little: 10 bytes per slice
- fixing bug in class tlv: unreleased memory
- added protection code in class deci to properly release memory against
exception thrown from called routines when user interrupts the operation.
- replace previous internal stack report code by backtrace()/backtrace_symbols()
- complete change of the implementation of the 'special-alloc' feature:
the old code eat too much memory not to be adapted to new features added
in release 2.4.0. This new implementation also bring some speed improvement
from 2.4.1 to 2.4.2
- fixing bug met when reading an archive in sequential-read mode
- fixing bug while filtering in sequential-read mode
- fixing backward compatibility in dar_manager with old archives (wrong dates
for deleted files).
- fixing compilation problem on certain systems (missing #include statement)
- fixing documentation syntax and spelling
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
from 2.3.6 to 2.3.7
- fixed bug in dar_manager about the localization of the archive in which to fin
d the latest EA
- fixed bug in configure script to properly report full blowfish encryption supp
ort
- fixed a bug in the statistics calculus of dar_manager for most recent files pe
r archive
- removed inappropriate internal error check
- added --disable-libdl-linking option
- fixed mistake in API tutorial
- updated Swedish translation by Peter Landgren
- fixed bug in the file filtering based on listing file ( -[ option )
- fixed typo and spelling errors in documentation
- updated code for clean compilation with gcc-4.2.3
- updated code for clean compilation with gcc-4.3 20080208 (experimental gcc)
from 2.3.7 to 2.3.8
- fixed bug in libdar met when user supply an empty file as a list of file to
include or exclude ( -[ and -] options )
- fixed bug concerning elastic buffers used beside strong encryption. No
security issue here, just in some almost rare situations the generated archive
was not readable (testing your archive prevents you loosing data in this
situation)
- added some speed optimizations
- avoided warning to appear without -v option set, when an error is met while
fetching value of nodump flag (flag not supported on filesystem for example).
Changes within pkgsrc:
(*) While here, add some logic to allow REPLACE_PERL and
REPLACE_BASH to work without USE_TOOLS+="perl bash".
Thus, the paths in share/dar/samples will now [usually]
be correct. Simplify options handling.
(*) Use PTHREAD_AUTO_VARS to ensure harmony with the
rest of pkgsrc, add USE_FEATURES.openssl=threads
when necessary. Threads are enabled if a built-in
thread library is used.
Changes in source (since version 2.3.5):
(*) fixed: Makefile.am in src/dar_suite
(removed "/" after $(DESTDIR))
(*) fixed: bug in regex mask building when not using
ordered masks
(*) fixed: bug that led dar_manager to report no error while
some files failed to be restored due to command-line
for dar being too large.
(*) fixed: bug encountered when user aborts operation while
dar is finalizing archive creation [SF #1800507]
(*) fixed: problem with execvp when dar_manager launches dar
This is a minor release. Changes from 2.3.4 are:
- changed displayed message when adding a hard link to an archive while
performing a differential backup
- added back the possibility to use old blowfish implementation (bfw cipher)
- integrated optimization patch from Sonni Norlov
- updated Swedish translation by Peter Landgren
- updated French translation
- fixed broken Native Language Support in 2.3.x (where x<5)
Pkgsrc changes:
- Use an option group for dar-int32 Vs dar-int64 Vs neither (infinint)
- Default to dar-int64 (the infinint support is excessive, and hugely
expensive)
- REPLACE_FOO doesn't work if FOO isn't a dependency, and we don't want to
pull in Bash and Perl just for a few samples! So, don't replace the
interpreters in the samples, just leave them as is.
ChangeLog from 2.3.3 to 2.3.4:
- fixed behavior when differential backup is interrupted (no more store file
that would have been read if no interruption had been done as "deleted"
since thearchive of reference) [SF #1669091].
- added official method to access catalogue's statistics through the API (for
kdar next version).
- Fixed syntax error in dar_par_create.duc and dar_par_test.duc files
(Parchive integration with dar).
- minor spelling fix in error message (compressor.cpp)
- added Wiebe Cazemier's two patches for dar man page
- integrated patch from Dwayne C. Litzenberger to fix weakness in dar's
implementation of the blowfish encryption.
- improved the returned message when an invalid path is given as argument
- updated doc/sample/sample1.txt script file
via NetBSD's patch(1) just fine, but failed on a Debian Linux box. We
need to provide three lines of context in the diff or else They complain
about patching fuzz, even if 100% of the diff context matches the target.
options.
Upgrading to 2.3.3 is strongly recommended if you use Dar to backup across
multiple filesystems:
http://article.gmane.org/gmane.comp.sysutils.backup.dar.announce/31
Changelog entry from 2.3.2 to 2.3.3:
- avoid using getpwuid() and getgrgid() for static linking.
- fixed typo in dar's man page
- update FAQ
- fixed bug: uncaught exception thrown when CTRC-C was hit while dar waits an
answer from the user [SF #1612205]
- fixed bug: unusable archive generated when CTRC-C was hit and blowfish
encryption used [SF #1632273]
- added a check to verify that the libdar used is compatible with the current
dar suite programs [SF #1587643]
- fixed bug: added workaround for the right arithmetic shift operator (the
binary produced by gcc-3.4.2 produces computes "v>>s" equal to "v" when when
v is a integer field composed of s exactly bits. It should rather compute it
to zero...).
this problem leads 32 bits generated archive incompatible with 64 bits
generated archive only when blowfish is used.
- fixed bug met when the inode space is exhausted, thanks to "Jo - Ex-Bart" for
this new feedback. [SF #1632738]
- replaced &, <, >, ' and " in XML listing by &...; corresponding sequence.
[SF #1597403]
- dar_manager can receive arguments after stick to -o options (it is an error
in regard to documentation, but no warning was issued in that case, leading
to confusion for some users) [SF #1598138]
- updated Veysel Ozer's automatic_backup script
- fixed hard link detection problem [SF #1667400]
- verbose output did not displayed hard links information
- merged patch on dar_cp by Andrea Palazzi to have it to return EXIT_DATA_ERROR
when some data have been reported [SF #1622913]
from 2.3.1 to 2.3.2
- fixed bug in Native Language Support when --enable-locale-dir was not set (Thomas Jacob's patch)
- updated Swedish translation by Peter Landgren
- --verbose=skipped was not available (only the short -vs form was available)
- reviewed regex with ordered mask for the feature to better fits user's need (Dave Vasilevsky's feedback)
- fixed bug where compression algorithm was changed to maximum (fixed with Richard Fish's adequate patch)
- fixed tutorial with command line evolution (dar's -g option in particular)
- latest version of Grzegorz Adam Hankiewicz's mini-howto
- fixed bug concerning restoration of only more recent files
Patch provided by Martin Wilke via PR 34430.
- Changelog
from 2.3.0 to 2.3.1
- set back Nick Alcock's patch which has been dropped from
2.2.x to 2.3.x (patch name is "Do not moan about every
single file on a non-ext2 filesystem")
- fixed compilation problem when thread-safe code is disabled
- integrated Wiebe Cazemier's patch for dar's man page
- fixed bug in listing: -as option also listed files that
had EA even when theses were not saved in the archive
- file permission of installed sample scripts lacked the
executable bit
- fixed a bug that appeared when a file is removed while at
the time it is saved by dar
- avoid having an unnecessary warning appearing when
restoring a file in a directory that has default EA set
- Cygwin has changed and does not support anymore the path
in the form "c:/some/where", you have to use
"/cygdrive/c/some/where" instead. Documentation has been
updated in consequence.
Dar is built by default with an arbitrary-size-integer library for managing
all file length/timestamp details. If 32-bit or 64-bit integers (with
overflow protection) are sufficient for requirements, the dar-int32 and
dar-int64 options can significantly reduce the run-time memory and CPU
overheads of Dar.
Leave the default unchanged (thus no package version bump).
PKGLOCALEDIR and which install their locale files directly under
${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries. From now
on, pkgsrc/mk/plist/plist-locale.awk will automatically handle
transforming the PLIST to refer to the correct locale directory.
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
so it doesn't build with its own libintl.
The error was: error: too many arguments to function `const
char* _nl_expand_alias()'
Include devel/gettext-lib/buildlink3.mk.
Bump PKGREVISION.
This is for PR 30993.
