baserev update by copy to link target

• Files Changed
• Browse Source

require python3-importlib-metadata for python < 3.8 (boo#1219652)

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Update to 2.2.6:
  * FIX: extended variables were not correctly written if content of file
         hadn't changed and file was read-only (API 201).
  * FIX: failed parsing of arguments would return code 2 for warnings
         instead of 1 for errors
  * FIX: quoting variables where not correctly propagated when set from
         the command line (API 201).
  * FIX: some new functions were needed with higher security level and
         had to be sorted accordingly (API 201).
  * FIX: test action would fail with empty error message when using API
         201
  * FIX: timezone was not always correctly calculated in countries with
         historically changing DST, closes #902
  * NEW: add environment variable RDIFF_BACKUP_API_VERSION to
         artificially modify the API version dictionary, see the man page for
         details.
  * NEW: add warning that server will be called with deprecated CLI and
         how to avoid the corresponding warning (see also the FAQ)
  * NEW: there is now a weekly release with changelog for intermediate
         testing available at
         https://github.com/rdiff-backup/rdiff-backup/releases/tag/weekly
  * FIX: cross-version issue with 2.0.5 complaining about KeyError
         restrict_path, closes #872
  * FIX: fail gracefully when connection(s) can't be setup e.g. in case
         of network error, closes #868

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Require python3-PyYAML, python3-pylibacl, python3-xattr
  (the latter two were Recommends only; all are runtime dependencies).

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- update to 2.2.4:
  * Only very small code and documentation fixes, hopefully
    really the last fix release of the stable branch 2.2, before
    the development effort for v2.4 starts.

- update to 2.2.3:
  * Only small code and documentation fixes and additions,
    probably the last fix release of the stable branch 2.2,
    before the development effort for v2.4 starts.
  * That's embarrassing but the last version still had a glitch
    and the sdist package `rdiff-backup-2.2.2.tar.gz` didn't
    contain the pre-rendered man-pages which some packagers
    requested.

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- Happy Holidays release v2.2.0
- Despite all these changes, rdiff-backup 2.2 remains compatible with
  rdiff-backup 2.0, but you can, and are encouraged to, use the new API
  using --api-version 201, enabling two additional features:
  * there is at last a --help parameter
  * the CLI (Command Line Interface) has been refurbished and modernized
    (the old one is still present but deprecated)
  * You can store your parameters in a file, one per line, and call
    rdiff-backup @myfile to use them
  * Verbosity levels and error codes have been standardized for clearer
    interaction with the tool
  * Last backup can be regressed even if it isn't failed
  * Locking of repositories has been greatly improved

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

- update to 2.0.5: 
  * CHG: explicitly refuse to back-up to exFAT because it doesn't
    handle properly case insensitive deletion of files
  * CHG: testing explicitly for existence of tempdir might make
    certain setups fail now because tempdir was silently ignored
  * DEV: Add a misc script to setup an ArchLinux as development
    platform
  * DEV: fix compatibility in rollsum and sum-size with rdiff
    2.2/2.3 leading to errors in librsynctest
  * DEV: function rpath.getdevnums now also returns the device
    type, block or char
  * DEV: replace deprecated xattr.xattr with xattr. function
  * FIX: address PY_SSIZE_T deprecation warning appearing
    under Python 3.8 in the C code
  * FIX: avoid TypeError: a bytes-like object is required,
    not 'str' when logging error message by fixing encoding
  * FIX: explicitly test existence of tempdir and avoid "Can't
    mix strings and bytes in path components" error
  * FIX: failed on certain device files with no such file
    or directory error
  * FIX: Force encoding of log file to be UTF-8 on all platforms
    and be lenient to avoid codec errors on logging

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

update to 2.0.3

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

update to 2.0.0

• Files Changed
• Browse Source

update to 1.9.2rc0, first rc for 2.0.0

• Files Changed
• Browse Source

baserev update by copy to link target

• Files Changed
• Browse Source

update to 1.9.1b0, third beta before 2.0.0

• Files Changed
• Browse Source

initialized devel package after accepting 769264

• Files Changed
• Browse Source