On Mon, 16 May 2005 17:27:49 -0700, John Reiser wrote: > IgnitionWorks wrote: > > The developers are working on high priority issues and > > I personally do not think this is a high priority or a > > show stopper. > > > > The build system script needs to check for updated > > packages, if any, else send 'No packages' email. > > > > For the interm, they can run cron M-F only. > > > > Either way, it's a trivial issue. > > No, the _issue_ is NOT trivial. The current behavior directly > undermines the little trust that volunteer testers have > left in the Fedora development system. It's broken, > in a MAJOR way. > > The _fix_ IS trivial. At the end of the report, add a line: > > <n> packages updated. > > If the list is empty and 0==n, then everyone will know > that the probability is at least 0.99999 that no packages > were updated, and that therefore an empty list is to be expected. > Otherwise, an empty list and no line "0 packages updated." > will indicate an error somewhere in the process. > Imagine that: truly effective communication. Empty list means no new packages found by the script. -- Fedora Core release 3 (Heidelberg) - Linux 2.6.11-1.14_FC3 loadavg: 1.00 1.00 1.00