Summary - Broken dependencies in Fedora Extras - 2006-11-24

Michael Schwendt bugs.michael at gmx.net
Sun Nov 26 00:08:05 UTC 2006


On Sat, 25 Nov 2006 18:08:17 +0100, Till Maas wrote:

> On Saturday 25 November 2006 17:22, Michael Schwendt wrote:
> 
> > That sounds as if you don't know that package owners do receive a private
> > email when their package is broken. The mail is sent again every 14 days
> > as long as the package remains broken. Those private messages are also
> > summed up at the bottom of the big report to this list. It is just
> > a "summary", not a report you must read everytime.
> 
> How about a weekly summary of every broken dependency and a daily report of 
> new broken dependencies?

Yes. At least put the new breakage at the top of the report. And if there
is no new breakage, the summary report won't be sent more often than every
week or so.

The EVR upgrade problems report to maintainers-list is too often, too.
There is no visibile interest either in fixing that breakage, not even in
response to bugzilla tickets.

> Maybe with a reference of how many broken 
> dependencies a certain maintainer already has if there is one new and how 
> many other packages have the same broken dependency?

Everybody is free to write code that creates different reports and
different statistics. But more important is to reduce the number of broken
packages. When the community gets larger and the number of problems
increases, this asks for adjusted guidelines/policies.




More information about the fedora-extras-list mailing list