[opensuse-factory] [ANN] zypper-cron: zypper package updates reporter
Hi, I am new to the mailing list, I hope I am posting this to the right place :-). I have just thrown together https://github.com/ifad/zypper-cron, a tool inspired by Debian's apticron[1]. It runs zypper ref and zypper -x list-patches, parses the XML output and, if patches are missing, summarizes them on the standard output. I have packaged it here: https://build.opensuse.org/package/show/home:vjt:ifad/zypper-cron, upon installation it adds /etc/cron.d/zypper-cron that runs the script daily at 4AM. It'll certainly need saving its state to avoid duplicate e-mails about updates already notified, and as well incremental mailings. I am not aware on any other similar open source effort, so I decided to scratch my own itch. Comments (and GitHub pull requests) appreciated! ~Marcello [1]: http://packages.debian.org/wheezy/apticron -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 26.01.2014 21:17, Marcello Barnaba wrote:
Hi,
I am new to the mailing list, I hope I am posting this to the right place :-).
I have just thrown together https://github.com/ifad/zypper-cron, a tool inspired by Debian's apticron[1].
It runs zypper ref and zypper -x list-patches, parses the XML output and, if patches are missing, summarizes them on the standard output.
I have packaged it here: https://build.opensuse.org/package/show/home:vjt:ifad/zypper-cron, upon installation it adds /etc/cron.d/zypper-cron that runs the script daily at 4AM.
It'll certainly need saving its state to avoid duplicate e-mails about updates already notified, and as well incremental mailings.
I am not aware on any other similar open source effort, so I decided to scratch my own itch.
Comments (and GitHub pull requests) appreciated!
~Marcello
Nice work but isn't there already a yast module to schedule periodic zypper runs? At least in SLES I think I saw one. -- Ralf Lang Linux Consultant / Developer Tel.: +49-170-6381563 Mail: lang@b1-systems.de B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Hello, Am Sonntag, 26. Januar 2014 schrieb Marcello Barnaba:
I have just thrown together https://github.com/ifad/zypper-cron, a tool inspired by Debian's apticron[1].
It runs zypper ref and zypper -x list-patches, parses the XML output and, if patches are missing, summarizes them on the standard output.
It'll certainly need saving its state to avoid duplicate e-mails about updates already notified, and as well incremental mailings.
I am not aware on any other similar open source effort, so I decided to scratch my own itch.
I didn't check your tool in detail, but the description sounds somewhat similar to my patch2mail ;-) Regards, Christian Boltz --
sdfgsdfg sind denn die Schreibmaschinenkurse an der VHS echt so überbelegt, daß man die Liste damit behelligen muß? [> Georg Poetting und Michael Schulz in suse-linux]
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Christian Boltz <opensuse <at> cboltz.de> writes:
It runs zypper ref and zypper -x list-patches, parses the XML output and, if patches are missing, summarizes them on the standard output. [] I am not aware on any other similar open source effort, so I decided to scratch my own itch.
I didn't check your tool in detail, but the description sounds somewhat similar to my patch2mail
Definitely! We wrote the same thing, but with different approaches. You use XSLT to do parsing and rendering, I instead used a Ruby XML Parser (Nokogiri) to build an object model of the updates, and a Ruby templating engine (Erubis) to render the e-mail. Both approaches are valuable - yours is definiely more language-agnostic, OTOH I think that mine can evolve more easily. Once the object model is built, it can be used to build web services on top of it. Think about having a OAuth'ed REST API endpoint that can be queried from a single dashboard: you'd have a patch management solution with web and mobile clients. It sounds fun to me, so I think I'll embark in implementing it in my spare time in the future - also because we need it at work ;-). What do you others? Does it sound like a reasonable effort or am I reinventing a wheel that's already rolling somewhere? Thanks! ~Marcello -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Christian Boltz -
Marcello Barnaba -
Ralf Lang