From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: Interested in maintaining zabbix addon package Date: Sat, 27 Mar 2021 08:30:52 +0100 Message-ID: In-Reply-To: <1a94488fff57c194e9cb4aabb18559b8be82dfe9.camel@filekeeper.sicho.home> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5928387650083307909==" List-Id: --===============5928387650083307909== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Robin, Sent from my Desktop Computer On 27/03/2021 00:13, Robin Roevens wrote: > Hi all > > I'm Robin, living in Belgium and a daily administrator of Zabbix both > professionally and at home. I use linux on all my computers, mainly > openSUSE, and administer RHEL based linux servers as a profession.=C2=A0Used > Gentoo, Debian, Slackware, Redhat, Mandrake etc many many years ago.. > > I have been using IPFire also for many years now, coming from > Smoothwall and IPcop, first in a VM on my home server, currently on an > IPFire appliance from Lightning Wire, so evidently I like monitoring my > appliance using Zabbix. > Hence I wrote a Zabbix Template to monitor and alert on IPFire specific > metrics (https://github.com/RobinR1/zbx-template-ipfire) and had > recently added a suggestion in the IPFire wiki - zabbix addon page to > use my template. > In response to my edit, Alexander Koch added a notice to that page that > the current Zabbix IPFire addon was no longer maintained. > > As an experienced user of both I may be interested in taking up the > role as package maintainer for the zabbix addon in IPFire. > I created packages before using Suse's OBS but never officially > maintained ones, so this would be my first, and with a currently > 'unknown' technology for me (Pakfire). You will of course be very welcomed by the IPFire dev team.They are a bit bus= y right now with the build up to the Core Update 155 release. Welcome to the IPFire team. I started out a year and a half ago with updating= am addon that I used that had become out of date and now am also helping wit= h providing patches to any programs I happen to find that are out of date. So I have trod the path you are setting out on and will be willing to help in= any way I can. > I started by reading the info available on the IPFire wiki and found > https://wiki.ipfire.org/devel/ipfire-2-x/addon-howto as, I think, the > most current documentation on how to build packages on IPFire 2.x. > Other Pakfire-related info seems to be mainly for IPFire 3. > The required build environment is currently building on my PC, so I > hope to start working on it soon. > However at the end of that document, the instructions as of how to > actually submit the package for inclusion in IPFire seems to be > missing. The addon page you found is exactly the one to use. The end part of that page= needs to be tidied up to point at the patch submission section. > So I will try to update the zabbix agent using this build env as soon > as it is ready, and for as far as I currently understand it, I will > then probably end up with changes in lfs/zabbix_agentd and > config/zabbix_agentd/, which I then just have to submit here as a patch > following the instructions on ipfire wiki about submitting patches? A few bits I have learned are:- use git commit -s=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 The -s adds your email = address as the Signed-by: line automatically use git format-patch=C2=A0=C2=A0 This gives you a patch formatted in the way = that IPFire need it use git send-email=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 This send the patch to= the IPFire development mailing list without mangling it like some mail MUA's= can do (as I found out). > Anyway, this was my introduction, and I hope I will be of some help in > this great project. Welcome and just ask for help if you hit any problems. Sometimes response may take a day or so as they are a small team and especial= ly at times leading up to a Core Update Release. > Regards > Robin > > --===============5928387650083307909==--