From mboxrd@z Thu Jan  1 00:00:00 1970
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
Message-ID: <BFAE52D2-B1CA-4A9E-BDEE-0F15CB2CEE03@ipfire.org>
In-Reply-To:
 <78b6f618dfc6a6fb168d77516e7896e6814ba94c.camel@filekeeper.sicho.home>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============5881586270990623471=="
List-Id: <development.lists.ipfire.org>

--===============5881586270990623471==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

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 cou=
ple of other things I am working on.

> On 7 Apr 2021, at 16:39, Robin Roevens <robin.roevens(a)disroot.org> wrote:
>=20
> Hello
>=20
> 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.
>=20
> 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..=20
> 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.=20
>=20
> 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=E2=80=99t promise anything, but if I find some time I will review the p=
atches and then we will see.

-Michael

> Regards
>=20
> Robin
>=20
> Michael Tremer schreef op wo 07-04-2021 om 16:04 [+0100]:
>> Hello,
>>=20
>> I would like to formally close Core Update 156 as soon as possible to
>> merge it into =E2=80=9Cmaster=E2=80=9D and release it to a wider audience =
for testing.
>>=20
>> Does anyone have any changes that *must* be in this update?
>>=20
>> I have the following things on my list:
>>=20
>> * 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
>>=20
>> * Jonatan wanted to drop the other templates for the web UI
>>=20
>> * Peter has some sysctl changes
>>=20
>> 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.
>>=20
>> 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 :)
>>=20
>> Best,
>> -Michael
>=20
>=20
> --=20
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
>=20


--===============5881586270990623471==--