unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: 55682@debbugs.gnu.org
Subject: [bug#55682] RFC packaging for lcsync
Date: Fri, 27 May 2022 12:10:25 -0700	[thread overview]
Message-ID: <87v8tq6bby.fsf@yucca> (raw)

[-- Attachment #1: Type: text/plain, Size: 539 bytes --]

Have a work-in-progress patch series for lcsync:

  https://librecast.net/lcsync.html

  Librecast file and data syncing tool.
  Compare data with merkle trees, sync via multicast.

blockers seem to be:

* issues around test suites

* not knowing the appropriate place or way to run "setcap
  cap_net_raw=eip bin/lcsync" ... setuid root would not be appropriate
  as that would allow overwriting nearly any file on the filesystem.

Will send patches shortly, one for the librecast library, and one for
lcsync itself.

live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

             reply	other threads:[~2022-05-27 20:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 19:10 Vagrant Cascadian [this message]
2022-05-27 19:27 ` [bug#55682] RFC packaging for lcsync Vagrant Cascadian
2022-05-27 19:27   ` Vagrant Cascadian
2022-07-30 23:39 ` Vagrant Cascadian
2022-07-30 23:41   ` [bug#55682] [PATCH V2 1/3] gnu: Add lcrq Vagrant Cascadian
2022-07-30 23:42     ` [bug#55682] [PATCH V2 2/3] gnu: Add librecast Vagrant Cascadian
2022-07-30 23:43       ` [bug#55682] [PATCH V2 3/3] gnu: Add lcsync Vagrant Cascadian
2022-08-11  9:48     ` [bug#55682] [PATCH V2 1/3] gnu: Add lcrq Maxime Devos
2022-08-12 18:15       ` Vagrant Cascadian
2022-08-11  2:32   ` bug#55682: RFC packaging for lcsync Vagrant Cascadian

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87v8tq6bby.fsf@yucca \
    --to=vagrant@debian.org \
    --cc=55682@debbugs.gnu.org \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).