[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#55682: RFC packaging for lcsync

From: Vagrant Cascadian
Subject: bug#55682: RFC packaging for lcsync
Date: Wed, 10 Aug 2022 19:32:34 -0700

On 2022-07-30, Vagrant Cascadian wrote:
> On 2022-05-27, Vagrant Cascadian wrote:
>> Have a work-in-progress patch series for lcsync:
>>   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,

Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]