Re: Happy Holidays release v2.2.0

Frank Crawford <[email protected]>
Newsgroups gmane.comp.sysutils.backup.rdiff-backup.general
Message-ID <2ddf5d20cc251ba244f603330c088eeccf55cbb5.camel@crawford.emu.id.au>
Eric,

On Sun, 2022-12-18 at 11:54 +0100, EricZolf wrote:
> Hi,
> 
> as the subject says, happy holidays and enjoy this new release!
> 
> Kind Regards, Eric
> 
> 
>    Happy Holidays release v2.2.0
>    <https://github.com/rdiff-backup/rdiff-backup/releases/tag/v2.2.0>
> 
> Repository: rdiff-backup/rdiff-backup 
> <https://github.com/rdiff-backup/rdiff-backup> · Tag: v2.2.0 
> <https://github.com/rdiff-backup/rdiff-backup/tree/v2.2.0> · Commit: 
> b768c1d 
> <https://github.com/rdiff-backup/rdiff-
> backup/commit/b768c1defa9f9d1ae7662e40f7609bd0f215c59c> 
> · Released by: github-actions[bot] <https://github.com/apps/github-
> actions>
> 
> 
>      Main changes
> 
> After 2 years of development, 48 fixed issues, 17 new features, we're
> releasing our next major version of rdiff-backup. At time of writing 
> only one known (and obscure) bug is left to be fixed. Most of the
> time 
> has been spent on modernizing the code with a clearer plug-in based 
> structure, but we've also found the time to implement a few cool
> 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
>    * Window wheels are now working, and rdiff-backup is available in
> 32
>      and 64 bits for Windows
> 
> And 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:
> 
>    * the last backup can be regressed even if it isn't failed (I
> think,
>      our oldest enhancement request)
>    * locking of repositories has been greatly improved (there wasn't
> much
>      of a locking before)
> 
> Detailed release notes are at the top of the changelog 
> </rdiff-backup/rdiff-backup/blob/v2.2.0/CHANGELOG.adoc>. As always, 
> consider especially the changes marked with |CHG| as they might
> impact 
> your workflow.
> 
> And, last but not least, our website rdiff-backup.net 
> <https://rdiff-backup.net/> has been revamped and merged with the
> docs 
> folder, allowing for easier maintenance and up-to-date documentation,
> in 
> alignment with the code evolution.
> 
> 
>      Install
> 
> The installation, described in details in the read me 
> </rdiff-backup/rdiff-backup/blob/v2.2.0/README.adoc>, has the quick
> version:
> 
>    * Linux, trust on your distro to provide the latest version of
>      rdiff-backup "soon-ish" (or copr/PPA)
>    * Windows, download the asset |rdiff-backup-2.2.0.win32/64exe.zip|
>      from the tagged release
>      <https://github.com/rdiff-backup/rdiff-
> backup/releases/tag/v2.2.0>
>      and unpack it somewhere in your |PATH|.
>    * Any supported Platform, and a few unsupported like BSD and
> MacOSX,
>      use |pip install rdiff-backup| (or download and install the
> proper
>      asset from the tagged release
>      <https://github.com/rdiff-backup/rdiff-
> backup/releases/tag/v2.2.0>).
>    * in call cases, you might want to have a look at the migration
> guide
>      </rdiff-backup/rdiff-backup/blob/v2.2.0/docs/migration.adoc>,
> eps
> 
> 
>      Help!
> 
> If you encounter issues, contact us on the rdiff-backup-users mailing
> list <https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users> 
> and/or report an issue 
> <https://github.com/rdiff-backup/rdiff-backup/issues/new/choose>.
> 
> We could also use some help, so don't hesitate to raise your hand on
> the 
> mailing list if you'd like to help your favorite backup tool!
> 
> —
> 
> This release has 23 assets:
> 
>    * rdiff-backup-2.2.0.tar.gz
>    * rdiff-backup-2.2.0.win32exe.zip
>    * rdiff-backup-2.2.0.win64exe.zip
>    * 
> rdiff_backup-2.2.0-cp310-cp310-
> manylinux_2_12_i686.manylinux2010_i686.whl
>    * 
> rdiff_backup-2.2.0-cp310-cp310-
> manylinux_2_12_x86_64.manylinux2010_x86_64.whl
>    * 
> rdiff_backup-2.2.0-cp310-cp310-
> manylinux_2_17_x86_64.manylinux2014_x86_64.whl
>    * rdiff_backup-2.2.0-cp310-cp310-manylinux_2_28_x86_64.whl
>    * rdiff_backup-2.2.0-cp310-cp310-win32.whl
>    * rdiff_backup-2.2.0-cp310-cp310-win_amd64.whl
>    * 
> rdiff_backup-2.2.0-cp37-cp37m-
> manylinux_2_12_i686.manylinux2010_i686.whl
>    * 
> rdiff_backup-2.2.0-cp37-cp37m-
> manylinux_2_12_x86_64.manylinux2010_x86_64.whl
>    * 
> rdiff_backup-2.2.0-cp37-cp37m-
> manylinux_2_17_x86_64.manylinux2014_x86_64.whl
>    * rdiff_backup-2.2.0-cp37-cp37m-manylinux_2_28_x86_64.whl
>    * rdiff_backup-2.2.0-cp38-cp38-
> manylinux_2_12_i686.manylinux2010_i686.whl
>    * 
> rdiff_backup-2.2.0-cp38-cp38-
> manylinux_2_12_x86_64.manylinux2010_x86_64.whl
>    * 
> rdiff_backup-2.2.0-cp38-cp38-
> manylinux_2_17_x86_64.manylinux2014_x86_64.whl
>    * rdiff_backup-2.2.0-cp38-cp38-manylinux_2_28_x86_64.whl
>    * rdiff_backup-2.2.0-cp39-cp39-
> manylinux_2_12_i686.manylinux2010_i686.whl
>    * 
> rdiff_backup-2.2.0-cp39-cp39-
> manylinux_2_12_x86_64.manylinux2010_x86_64.whl
>    * 
> rdiff_backup-2.2.0-cp39-cp39-
> manylinux_2_17_x86_64.manylinux2014_x86_64.whl
>    * rdiff_backup-2.2.0-cp39-cp39-manylinux_2_28_x86_64.whl
>    * Source code (zip)
>    * Source code (tar.gz)
> 
> Visit the release page 
> <https://github.com/rdiff-backup/rdiff-backup/releases/tag/v2.2.0> to
> download them.

Thank you for all the hard work getting this out.

It is also now available for immediate download from RPM based systems
from

https://copr.fedorainfracloud.org/coprs/frankcrawford/rdiff-backup/

It will also be available for Fedora and EPEL 8 and 9 standard updates
in about a week.

Regards
Frank
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.