>> Grarpamp, I just discovered monotone last year while searching for a >>
>> minimalist no-bullshit dvcs, and promptly became quite fond of it. Sadly >>
>> it seems like it's on the verge of death. Would you or anyone else you >>
>> know be interested in collaborating to get Lapo Luchini's
>On 2021-05-08 13:22, Michael Raskin wrote:
>> Hello
>> I am trying to maintain a Monotone package in Nixpkgs. Currently
>> the Botan 1 version needed to build the latest Monotone release seems to
>> get a bunch of vulnerabilities reported
>> I believe you could also enable the incoming connections on the port in
>> the firewall settings…
>
>That's what I did originally on port 4691, and it did not work.
>I suspect that netsync sets up an other port that the modem firewall
>does not know about. Is the port usage of netsync
>> >Netsync relies on some underlying conventions on the use of TCP for a
>> >two-way connexion. Is there some other protocol that shares these
>> >conventions? If so I could tell the modem that this other protocol is
>> >now being used on port 4691.
>>
>> I would frankly start with tcpdump
>On Sun, Jun 06, 2021 at 10:51:21AM +0200, Michael Raskin wrote:
>> >Or is here some other way of achieving the same result -- letting
>> >netsync work when I'm not at home?
>>
>> As an «adapt to the modem» approach, I would consider forwarding SSH and
>>
>On Sat, Jun 05, 2021 at 05:51:38PM +0200, Michael Raskin wrote:
>> >Is anything being done about this?
>> >Is the current botan so incompatible that it's hopeless to adapt?
>> >
>> >Or is monotone development and maintenance truly dead and I need to
&
>As people noted in last months / years... the worlds OS, apps,
>developers, and tech oriented operating system / repo / code / porters
>eyeballs users and interactors have more or less moved en masse
>to git, primarily on github, often augmented by running
>their own git copies in house if they
>Or is here some other way of achieving the same result -- letting
>netsync work when I'm not at home?
As an «adapt to the modem» approach, I would consider forwarding SSH and
either port forwarding netsync in SSH connection or directly using SSH
repository address (which means netsync through
>Is anything being done about this?
>Is the current botan so incompatible that it's hopeless to adapt?
>
>Or is monotone development and maintenance truly dead and I need to
>abandon ship and take what data I ca with me?
1. You can easily check out a branch that actually works with botan2.
I
and compare with
upstream repository diff by diff) and use GitHub's tarball download
feature from there. (Choice of GitHub: so that the mirror is linked to
my Nixpkgs comitter identity)
Thank you, goodbye
Michael Raskin.
10 matches
Mail list logo