Re: Bug#554003: munin cpu plugin has too strict limits (#554003)

2009-11-25 Thread Holger Levsen
Hi Adam,

On Dienstag, 24. November 2009, Adam D. Barratt wrote:
  Would you accept a fixed package with just this fix in stable?
 Yes, the patch looks fine.

Thanks. Uploaded to stable-proposed-updates. Should I reassign/clone 554003 to 
release.debian.org now?


regards,
  Holger


signature.asc
Description: This is a digitally signed message part.


Re: Bug#554003: munin cpu plugin has too strict limits (#554003)

2009-11-25 Thread Adam D. Barratt
Hi,

On Wed, 2009-11-25 at 12:11 +0100, Holger Levsen wrote:
 On Dienstag, 24. November 2009, Adam D. Barratt wrote:
   Would you accept a fixed package with just this fix in stable?
  Yes, the patch looks fine.
 
 Thanks. Uploaded to stable-proposed-updates. Should I reassign/clone 554003 
 to 
 release.debian.org now?

There's not really any need now that the package is in p-u-new; {o-,}p-u
bugs are more useful for making sure that we don't forget about updates
that are waiting for us to decide whether to approve them.

Regards,

Adam


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Bug#554003: munin cpu plugin has too strict limits (#554003)

2009-11-24 Thread Adam D. Barratt
On Thu, 2009-11-19 at 18:22 +0100, Holger Levsen wrote: 
 On Montag, 16. November 2009, Peter Palfrader wrote:
  http://patch-tracker.debian.org/patch/series/view/munin/1.2.6-17/610-plugin
 -cpu-fix-max.patch
 
 This patch is in sid+squeeze since some time (munin 1.2.6-14 from Aug 26 
 2009) 
 without any negative feedback, fixing a severity normal bug, which many 
 users, including our beloved DSA team, would like to see fixed in stable. 
 
 Would you accept a fixed package with just this fix in stable?

Yes, the patch looks fine.

Regards,

Adam


--
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Bug#554003: munin cpu plugin has too strict limits (#554003)

2009-11-19 Thread Holger Levsen
Hi stable-release-team,

On Montag, 16. November 2009, Peter Palfrader wrote:
 http://patch-tracker.debian.org/patch/series/view/munin/1.2.6-17/610-plugin
-cpu-fix-max.patch

This patch is in sid+squeeze since some time (munin 1.2.6-14 from Aug 26 2009) 
without any negative feedback, fixing a severity normal bug, which many 
users, including our beloved DSA team, would like to see fixed in stable. 

Would you accept a fixed package with just this fix in stable?


regards,
Holger


signature.asc
Description: This is a digitally signed message part.


Re: Bug#554003: munin cpu plugin has too strict limits (#554003)

2009-11-16 Thread Tom Feiner
Hi Peter,

Peter Palfrader wrote:
 I have not heard anything from you munin folks about a possible fix of
 this bug in stable.  Comments?
 

The reason you didn't hear from us is because I've forwarded this bug
upstream [1] as this is not a debian specific issue, and as such, it
will interest upstream developers (and other distributions).

So we should probably continue this discussion in the upstream bug.

However, I've seen that so far upstream developers haven't responded to
this bug. Maybe some more details on when exactly this is happening
might (how to reproduce exactly) might help.

Another thing that I notice, is that according to this bug, you're
running munin version 1.2.5-1 which is the one released for etch. The
cpu plugin was enhanced in munin version 1.2.6, which is packaged for
lenny.

Can you install the latest munin version from lenny (or testing) and see
if the problem persists?

Regards,
Tom Feiner

[1] http://munin.projects.linpro.no/ticket/736



signature.asc
Description: OpenPGP digital signature


Re: Bug#554003: munin cpu plugin has too strict limits (#554003)

2009-11-16 Thread Peter Palfrader
On Mon, 16 Nov 2009, Tom Feiner wrote:

 So we should probably continue this discussion in the upstream bug.

Or we could just fix it.

 However, I've seen that so far upstream developers haven't responded to
 this bug. Maybe some more details on when exactly this is happening
 might (how to reproduce exactly) might help.

I have lined out whent it happens.  And it happens lots and often.

 Another thing that I notice, is that according to this bug, you're
 running munin version 1.2.5-1 which is the one released for etch. The
 cpu plugin was enhanced in munin version 1.2.6, which is packaged for
 lenny.

Bad copy/paste.  It applies to lenny, not etch (bug report accordingly
modified).
-- 
   |  .''`.  ** Debian GNU/Linux **
  Peter Palfrader  | : :' :  The  universal
 http://www.palfrader.org/ | `. `'  Operating System
   |   `-http://www.debian.org/


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: Bug#554003: munin cpu plugin has too strict limits (#554003)

2009-11-16 Thread Peter Palfrader
On Mon, 16 Nov 2009, Tom Feiner wrote:

 Peter Palfrader wrote:
  On Mon, 16 Nov 2009, Tom Feiner wrote:
  
  Bad copy/paste.  It applies to lenny, not etch (bug report accordingly
  modified).
 
 Thanks for updating the found version.
 
 After digging a bit more, this looks like the same issue as debian bug [1] ,
 which is fixed in testing. They used a similar fix as you proposed, only
 instead of increasing the MAX field slightly, they removed it completely.
 
 This is also the same solution offered by upstream [2], only backported to
 munin 1.2.6.
 
 Can you test if munin from testing fixes your problem?

http://patch-tracker.debian.org/patch/series/view/munin/1.2.6-17/610-plugin-cpu-fix-max.patch

If that's the patch you are referring to then it very likely fixes my
bug.  It's a more brutal version of my patch, both will do.


-- 
   |  .''`.  ** Debian GNU/Linux **
  Peter Palfrader  | : :' :  The  universal
 http://www.palfrader.org/ | `. `'  Operating System
   |   `-http://www.debian.org/


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org