#2032: please list broken deps at the top of the rawhide report

[Fedora Release Engineering]

#2032: please list broken deps at the top of the rawhide report
----------------------+-----------------------------------------------------
  Reporter:  alexlan  |       Owner:  rel-eng at lists.fedoraproject.org
      Type:  defect   |      Status:  reopened                       
 Milestone:           |   Component:  other                          
Resolution:           |    Keywords:                                 
----------------------+-----------------------------------------------------
Changes (by till):

  * status:  closed => reopened
  * resolution:  fixed =>

Comment:

 I disagree that just moving broken deps at the top of the rawhide report
 is a good solution. First of all, this change was not announced and
 therefore broke peoples expectations. At least someone else and me thought
 that there are now new packages, because we did not bother to scroll
 beyond the broken dependencies.

 Also the current report is not very useful. It does not show, whether the
 package is broken for a longer period of time or only just now. Since the
 package maintainers will also get a personal e-mail, it is not even worth
 to go through the list to see, if there are some packages that one owns in
 the list. The list also contains a lot of broken dependencies that are
 there for a longer period and that is already worked on (the clutter
 stuff), so these should be less prominent in the report.

 How about another approach for this and use bugzilla to track long term
 broken dependencies. E.g. if the report script notices, that there is a
 broken dependency, it first checks, whether this is might be a new broken
 dependency, e.g. if the package was also updated within the push or a
 package that provides a package that the package depends upon is updated,
 then the broken dependency is considered to be new and the maintainers are
 only noticed via e-mail. If the broken dependency is not new, then a bug
 report on Bugzilla is created, if there is none already, and the progress
 can be tracked. The script could then also report these bug reports
 according to their activity / staleness. So that there is e.g. a warning
 if a bug was not touched for X days. So then superpackagers can start to
 work on fix these packages.

 In conlusion, I guess if the information is helpful to fix the broken
 dependencies, then they will most likely be less ignored. Btw. is there a
 mailing list to reach all superpackagers? Then maybe the report could also
 go there, because afaik normal packagers cannot fix these packages anyhow.

-- 
Ticket URL: <https://fedorahosted.org/rel-eng/ticket/2032#comment:3>
Fedora Release Engineering <http://fedorahosted.org/rel-eng>
Release Engineering for the Fedora Project