From: Libor Ukropec <ace@seznam.cz>
To: cygwin-apps@cygwin.com
Subject: [ITA] duplicity
Date: Thu, 7 Apr 2022 00:10:55 +0200 [thread overview]
Message-ID: <e0d04cbc-fc4c-9c53-8ae5-1953774382ee@seznam.cz> (raw)
I'd like to offer to adopt maintenance of duplicity (Encrypted
bandwidth-efficient backup system)
Information from https://duplicity.gitlab.io/ - """The last stable 0.7
release is *0.7.19*, released Apr 19, 2019""", while cygwin contains
0.7.11 from 2017
Updated cygport:
https://github.com/cz6ace/cygwin-duplicity
Updated build:
https://github.com/cz6ace/cygwin-duplicity/releases
Please note for successful installation the python 2.7 fasteners package
is required, not yet in cygwin, I plan to offer [ITP] for it:
cygport:
https://github.com/cz6ace/cygwin-python-fasteners
build:
https://github.com/cz6ace/cygwin-python-fasteners/releases
Python standard library provides a lock for threads (both a reentrant
one, and a non-reentrant one, see below). Fasteners extends this, and
provides a lock for processes, as well as Reader Writer locks for both
threads and processes.
This library (in newer version) is also present in LInux distributions,
e.g. Ubuntu:
https://packages.ubuntu.com/source/focal/s390x/python-fasteners
Regards,
Libor
next reply other threads:[~2022-04-06 22:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-06 22:10 Libor Ukropec [this message]
2022-04-06 23:40 ` Brian Inglis
2022-04-07 19:39 ` Libor Ukropec
2022-04-07 22:26 ` Libor Ukropec
2022-04-07 23:44 ` Brian Inglis
2022-04-10 18:26 ` Libor Ukropec
2022-04-12 0:09 ` Libor Ukropec
2022-04-12 13:10 ` Jon Turney
2022-04-12 19:24 ` Libor Ukropec
2022-04-12 16:56 ` Achim Gratz
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=e0d04cbc-fc4c-9c53-8ae5-1953774382ee@seznam.cz \
--to=ace@seznam.cz \
--cc=cygwin-apps@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).