From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 156
Date: Wed, 07 Apr 2021 16:41:58 +0100 [thread overview]
Message-ID: <BFAE52D2-B1CA-4A9E-BDEE-0F15CB2CEE03@ipfire.org> (raw)
In-Reply-To: <78b6f618dfc6a6fb168d77516e7896e6814ba94c.camel@filekeeper.sicho.home>
[-- Attachment #1: Type: text/plain, Size: 3108 bytes --]
Hello Robin,
Thanks for your email.
I have seen your patches and I had hoped that somebody else would jump on it and give it a good review.
My priority was indeed lying on getting the current update together and a couple of other things I am working on.
> On 7 Apr 2021, at 16:39, Robin Roevens <robin.roevens(a)disroot.org> wrote:
>
> Hello
>
> It would be nice to have my zabbix_agentd update in this core update
> too, which I provided at the start of previous week and seems to be
> requested by a community member
> (https://community.ipfire.org/t/zabbix-agent-on-stable-release/3636)
> since October.
>
> And of course as a newbie here I can't wait for my submission to be
> reviewed/included. But that should of course not be the reason to try
> to squeeze it in this update. And apart from that, other than the fact
> that the current version of zabbix_agentd is very old (august 2019), I
> don't see any sudden urgent reasons to really have this package
> included in update 156 as it already was not updated for so long..
> And I understand, seeing how much patches where submitted here in the
> meantime, that the priorities currently are not set on some arbitrary
> addon package like zabbix_agentd.
Yes this is old. So thank you for looking into this.
> So I guess it can wait for 157.
>
> I also noticed that in the meantime there is a Zabbix Agent v5.0.10
> (LTS) available, so I will re-submit my patchset shortly upgrading
> current 4.2.6 to 5.0.10. And then hopefully have it included in 157?
> Unless you still see a possibility to have it included in 156? :-)
I won’t promise anything, but if I find some time I will review the patches and then we will see.
-Michael
> Regards
>
> Robin
>
> Michael Tremer schreef op wo 07-04-2021 om 16:04 [+0100]:
>> Hello,
>>
>> I would like to formally close Core Update 156 as soon as possible to
>> merge it into “master” and release it to a wider audience for testing.
>>
>> Does anyone have any changes that *must* be in this update?
>>
>> I have the following things on my list:
>>
>> * Dropping macvtap support: This is broken and I do not think that we
>> would need this because we have bridges. Please review my proposed
>> patch:
>> https://lists.ipfire.org/pipermail/development/2021-April/009858.html
>>
>> * Jonatan wanted to drop the other templates for the web UI
>>
>> * Peter has some sysctl changes
>>
>> Apart from that I would like to move our attention to testing this
>> update and collecting patches for the next update. Core Update 156 is
>> already quite large (15 MB compressed on x86_64) and so I would reject
>> any larger changes unless really necessary.
>>
>> Lots of thanks to Adolf for putting in so many hours to update all
>> these packages that have received so little love in the past.
>> Especially Perl is one of those which take ages and ages :)
>>
>> Best,
>> -Michael
>
>
> --
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
>
next prev parent reply other threads:[~2021-04-07 15:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-07 15:04 Michael Tremer
2021-04-07 15:39 ` Robin Roevens
2021-04-07 15:41 ` Michael Tremer [this message]
2021-04-07 16:43 ` Adolf Belka
2021-04-07 20:08 ` Michael Tremer
2021-05-11 11:16 ` Adolf Belka
2021-05-11 11:29 ` Michael Tremer
2021-05-11 12:42 ` pmacct (was Core Update 156) Adolf Belka
2021-05-11 13:17 ` Michael Tremer
2021-05-11 13:51 ` Adolf Belka
2021-05-11 16:44 ` Michael Tremer
2021-04-07 18:32 ` Core Update 156 Michael Tremer
2021-04-07 19:37 ` Matthias Fischer
2021-04-07 19:52 ` Matthias Fischer
2021-04-07 20:07 ` Michael Tremer
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=BFAE52D2-B1CA-4A9E-BDEE-0F15CB2CEE03@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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