public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Libor Ukropec via Cygwin-announce <cygwin-announce@cygwin.com>
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] duplicity 1.2.2-2 (TEST)
Date: Sun, 29 Jan 2023 10:13:23 +0100	[thread overview]
Message-ID: <announce.1408edb7-fb9a-ffb0-5ed3-95b37e844138@seznam.cz> (raw)

The following packages have been uploaded to the Cygwin distribution as a test release:

* duplicity-1.2.2-2

Duplicity backs directories by producing encrypted tar-format
volumes and uploading them to a remote or local file server. Because duplicity
uses librsync, the incremental archives are space efficient and only record
the parts of files that have changed since the last backup. Because duplicity
uses GnuPG to encrypt and/or sign these archives, they will be safe from
spying and/or modification by the server.


This package is the latest upstream version. After some testing period it will be moved 
from test to release. Any feedback is appreciated.
For changes see https://gitlab.com/duplicity/duplicity/-/blob/main/CHANGELOG.md

Please send questions or concerns to the main Cygwin mailing list as usual.

Libor

-- 

*** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO ***
If you want to unsubscribe from the cygwin-announce mailing list, look at the 
"List-Unsubscribe:" tag in the email header of this message. Send email to the address 
specified there. It will be in the format:

cygwin-announce-unsubscribe-you=yourdomain.com<at>cygwin.com

If you need more information on unsubscribing, start reading here:

https://sourceware.org/lists.html#unsubscribe

-- 
Problem reports: https://cygwin.com/problems.html
FAQ: https://cygwin.com/faq/
Documentation: https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

                 reply	other threads:[~2023-01-29  9:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=announce.1408edb7-fb9a-ffb0-5ed3-95b37e844138@seznam.cz \
    --to=cygwin-announce@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).