From: Christian Bricart <christian@bricart.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Help wanted with net-misc/frr maintenance
Date: Thu, 13 Jul 2023 09:39:21 +0200 [thread overview]
Message-ID: <4ac60bf4-b9d9-3ae4-4182-ea40e6356907@bricart.de> (raw)
In-Reply-To: <26a3c656-ffa2-52ea-e072-9fd5cd9fd53f@uls.co.za>
Am 13.07.23 um 09:10 schrieb Jaco Kroon:
> Hi Alarig,
>
> On 2023/07/12 15:18, Alarig Le Lay wrote:
>> Hello Jakov,
>>
>> On Wed 12 Jul 2023 10:54:47 GMT, Jakov Smolić wrote:
>>> Hi all,
>>> I was recently left as the sole maintainer of net-misc/frr and given I'm
>>> not actively using the package anymore it would be good if someone who
>>> is an active user could take over. There are several open bugs and a new
>>> upstream release.
>>>
>>> I can stay as a secondary maintainer and help out (non-Gentoo developers
>>> are also welcome, I can proxy for you), otherwise if no one is
>>> interested I'll drop the package to maintainer-needed soon.
>>>
>>> Regards,
>> I’m already maintaining bird, so I could happily step in for frr as
>> well!
> Happy to assist where I can. For the most part frr "just works" for us
> though. Also not something we like to upgrade on a frequent basis
> unless there is a specific reason to.
>
> Kind Regards,
> Jaco
>
>
FYI: upstream also has a (neglected?) overlay on their site:
https://github.com/FRRouting/gentoo-overlay
Christian
prev parent reply other threads:[~2023-07-13 7:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 8:54 [gentoo-dev] Help wanted with net-misc/frr maintenance Jakov Smolić
2023-07-12 13:18 ` Alarig Le Lay
2023-07-12 20:38 ` Jakov Smolić
2023-07-13 15:45 ` Alarig Le Lay
2023-07-13 7:10 ` Jaco Kroon
2023-07-13 7:39 ` Christian Bricart [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=4ac60bf4-b9d9-3ae4-4182-ea40e6356907@bricart.de \
--to=christian@bricart.de \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox