all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: 55682-done@debbugs.gnu.org
Subject: bug#55682: RFC packaging for lcsync
Date: Wed, 10 Aug 2022 19:32:34 -0700	[thread overview]
Message-ID: <87mtcb7bnh.fsf@contorta> (raw)
In-Reply-To: <87wnbuyxu5.fsf@contorta>

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

On 2022-07-30, Vagrant Cascadian wrote:
> On 2022-05-27, Vagrant Cascadian wrote:
>> 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
>
> Have mostly fixed these with some new patches.
>
> There are some tests that require networking, and upstream is working on
> a way to skip those when networking is unavailable.

I removed the failing network tests for now.


>> * 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.
>
> This is still outstanding, feature request reported as:
>
>   #55683: Support binaries that need "setcap" similar to "setuid-programs"

Since this can still be useful as root, I pushed without resolving this
issue. I think the approach outlined in the above bug report should work
in theory...


>> Will send patches shortly, one for the librecast library, and one for
>> lcsync itself.
>
> Will submit an updated patch series to new usptream versions and to run
> the correct test suites, and also added the lcrq library.

Push to guix master as:

  6bdcd2f3f08d054f8a605fc33935c4057528cdcc gnu: Add lcsync.
  78b81bf95166562921284a5257580eb2ff01e4f3 gnu: Add librecast.
  24ec1b5a2046111d34bc5a965a6bef992f7c8d78 gnu: Add lcrq.


live well,
  vagrant

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

      parent reply	other threads:[~2022-08-11  2:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-27 19:10 [bug#55682] RFC packaging for lcsync Vagrant Cascadian
2022-05-27 19:27 ` 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   ` Vagrant Cascadian [this message]

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=87mtcb7bnh.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=55682-done@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.