dump (0.4b49-2) unstable; urgency=high

  release 0.4b49 is not fully backwards compatible
  with older releases: older releases cannot restore backups
  that have been created with 0.4b49.

  the codebase has been refreshed and fixed up quite substantially
  by tim woodall, the new upstream developer; a good overview of
  the changes can be found in /usr/share/doc/dump/NEWS.gz.

 -- Alexander Zangerl <az@debian.org>  Fri, 14 Feb 2025 15:44:44 +1000

dump (0.4b47-4) unstable; urgency=medium

  dump now records the actual filesystem argument that it was given
  in /var/lib/dumpdates; that argument may not be the same
  as the underlying disk device but this change makes
  incremental backups with filesystems selected by LABEL=x
  or UUID=y possible without format changes to dumpdates.

  there is one small limitation:

  if you want to perform incrementals, then you must give dump the same
  filesystem selection parameter for all invocations (level 0 and up),
  or it won't find previous backups in /var/lib/dumpdates.
  
  for example, you can't mix selection by device path /dev/sdxyz with
  selection by UUID=whatever, regardless of whether the two identify the
  same physical filesystem or not.

 -- Alexander Zangerl <az@debian.org>  Tue, 03 May 2022 15:34:16 +1000
