Bug#149425: [Popcon-developers] Bug#149425: Please, do not forget to explain why you reset the severity of a bug

[Bill Allombert]

On Thu, Oct 30, 2003 at 08:03:13PM +0100, Mathieu Roy wrote:
> severity 149425 important
> thanks
> 
> No reason was provided in 
> <http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=149425&msg=4>
> to set severity as wishlist.

This is not a bug in the package but on the popcon server side,
that we cannot fix. We are in the process of reorganizing popcon
to be able to improve the server side.

> This pop-con project is interesting only if installing it on 100
> computers of a network does not mean sending 10 Mb by mail per week,
> just for statistical purpose.

My popularity-contest file is 23kb uncompressed and 7.5kb compressed.
Admitting you have more package installed, that lead to 10Mb
uncompressed, 3.3Mb compressed and 4.4Mb base64 encoded. 

If you have 100 computers, I expect they all have a similar packages
use, so just install popcon on some of them. You will save more bandwidth
and avoid flooding popcon with nearly identical reports, for which it
is not well-designed.

Anyway, I eagerly wait for your patches.

> In my opinion, this problem is a bug, not a wish, and it fits the
> following severity:  

I hope you understand the above give more information about you than
about the bug.

I prefer to fix bugs instead of discussing their severities to death.

> If you do not agree, please argue, do not just reset the severity
> without any meaningful explanation, this is misbehaving, as DD you
> agreed to take care about users.

You ask for a new feature that require significant work to implement
and is basically out of our reach at this point.

> Such a bug should not remain unfixed for "1 year and 143 days old", I
> hope more attention will be paid to that problem with this more
> appropriate severity.

I hope you understand the above sentence is accepted by most Debian
developers as a sufficient ground to killfile you.

Read the popcon changelog. I assume you will understand why this bug
has remained unfixed for "1 year and 143 days old".

In case it is still not clear to you, don't waste the time of people
that try to fix the problem. That is unlikely to make it fixed 
faster.

Cheers,
-- 
Bill. <ballombe@debian.org>

Imagine a large red swirl here.