2013-02-07 - Re: [GRASE-Hotspot] Monit Service

Header Data

From: Tim White <ti***8@gmail.com>
Message Hash: a3ab6f6f73aaa4e7d4790bc17aa401ccc5ae2c050dcde21bd8fe2002d1e41b6f
Message ID: <51136A0A.5020705@gmail.com>
Reply To: <201302070919.28884.solbu@solbu.net>
UTC Datetime: 2013-02-07 01:47:06 UTC
Raw Date: Thu, 07 Feb 2013 18:47:06 +1000

Raw message 

On 07/02/13 18:19, Johnny Solbu wrote:
> On Thursday 7. February 2013 07.26, Tim White wrote:
>> It has been recommended (requested?) for some time that you uninstall
>> this package (and probably also the monit package) as it's "leaking
>> data" and not maintained. If you wish to use monit yourself, please
>> remove my package so your monit settings are active and I stop getting
>> these email attempts.
> One thing RPM packaging have over Deb packaging is that we can uninstall any installed package, by obsoleting it.
> That is, an obsoleted package will be uninstalled by the package manager when instaling any package that obsolete another one, and the user can do little to prevent it, short of not installing the package that obsoletes the old package.
>
> If the Debian package manager tools doesn't have this feature, you could release an updated package, that contains No files, which will have the sole purpose of disableing itself. Maybe have a script run when instaling the new updated package, that will explicitly stop and remove the files that is responsible for this. Then all those installations that still send you mail, will stop upon next system update cycle.
>
> You should to take into account that many of the sysadmins which manage these systems do not read this list, and therefore doesn't know that they should manually uninstall the package. Some of them might not even know how to do that. (Yes, such people really do exist.)
Thanks Johnny

I am aware that many people probably aren't on this list. Debian has a 
way of obsoleting packages too. And I can use the grase-repo package to 
force an uninstall of something if needed. I've kinda been trying to 
avoid doing that, but the more I look at it, the more I'm thinking it's 
a good idea. It wasn't until today that I realised how many systems 
still tried to send me monit emails. Originally I thought it was just 
one, and that particular one I know doesn't auto update ether (still on 
version 3.1), so hadn't thought of forcing an uninstall on something 
that didn't appear to be a big problem.

Tim

Thread