Hi Jonas,

On 29/10/2024 11:15, Jonas Smedegaard wrote:
> Quoting Matthieu Baerts (2024-10-26 18:50:10)
>> On 26/10/2024 17:01, Jonas Smedegaard wrote:
>>> Quoting Matthieu Baerts (2024-10-26 15:39:47)
>>>> I was able to install the new version (0.12-5) on Debian Sid, but it 
>>>> is currently not possible to install the previous one (0.12-4) 
>>>> because of the break in libell0. And on Debian testing, it is not 
>>>> possible to install the new version, because it depends on the last 
>>>> version of libell0 :)
>>>>
>>>>>> I then sent the new version to Debian Mentors.
>>>>>>
>>>>>>   https://mentors.debian.net/package/mptcpd/
>>>>>>
>>>>>> Do you think you could sponsor this small update please? If not, I
>>>>>> understand, I can ask someone else.
>>>>>
>>>>> I don't do sponsoring - because I find it awkward how exactly the
>>>>> responsibility is then split.
>>>>>
>>>>> What I prefer instead is long-term collaboration: Would you like to
>>>>> have me on board as a co-maintainer of the mptcpd package in Debian?
>>>>
>>>> Yes, good idea! I'm totally fine with that!
>>>>
>>>> How can I do that? By adding your name to the "Maintainer" (without
>>>> 's'?) field in debian/control file? It looks like it can only have one
>>>> person / team, no?
>>>>
>>>>   https://www.debian.org/doc/debian-policy/ch-controlfields.html
>>>>
>>>> Or should I use the Uploaders field? They mention the 
>>>> "co-maintainers" term there. Or do we need to create a team just for 
>>>> that?
>>>>
>>>> (Also, should I modify the current version on Salsa and re-tag?)
>>>
>>> First things first: Regarding the "I"'s in the above, only if you want
>>> to learn and therefore want us to take it slow. Otherwise you just lean
>>> back now that you have something that seems to work from your end of
>>> builds-and-seems-to-function-as-intended, and then I take over and
>>> polish the package hinting and formally release it - unless there are
>>> some bits that puzzles me, then I ask you.
>>
>> I'm really open to learn, but I don't know how long things will take.
>> What I mean is that, if it can help, a version 0.13 is supposed to be
>> released soon, including the two patches included here. Here, I prepared
>> a new bug-fix version (0.12-5) to unblock the issue with ELL 0.69, and
>> to be able to install mptcpd again on Sid before any auto-removal.
>>
>> I guess it is best not to "block" this version. But there is nothing
>> that urgent here either, but that would be good to have this bug-fix
>> version released before the 5 of November:
>>
>>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1084302
> 
> I have released the package, almost as you left it.

Thank you! And thank you for the modifications you did, that makes sense!

> Technically the "deadline" of November 5th could be postponed by simply
> posting to that bugreport, but no need for that when you have fixed the
> issue, only complicated by my stubborn approach to releasing the fix.

OK, thank you, I didn't know that.

>>> What I prefer is to keep relatively formal conversations in bugreports,
>>> and more casual chatter on matrix/irc.  I am @jonas:matrix.jones.dk in
>>> case you wanna chat on matrix.
>>
>> I'm matttbe on IRC (Libera.chat and OFTC). You can find me on #mptcp on
>> Libera.chat for example. But I can check Matrix if IRC is an issue.
> 
> I am old enough to use irc and be sceptical about other platforms, but
> young (or just stupid?) to find irc clunky to manage.  I self-holst mail
> and other services (including a matrix node) but have stopped running an
> irc proxy, now relying on matrix.org gateways - and unfortunately such
> gateway is blocked by Libera: https://libera.chat/guides/matrix

:)

> So I cannot easily join you at Libera, but you need not mess with Matrix
> as I hang out on OFTC as well (via a Matrix bridge).
> 
> Since I expect most of out chatter about Debian packaging rather that
> mptcpd project, I suggest we just hang out at my favorite spot used for
> misc. smaller projects I am involved in: Please join channel #tinker at
> OFTC.

Just did!

Cheers,
Matt
-- 
Sponsored by the NGI0 Core fund.

Reply via email to