updates-testing notification changes

Luke Macken lmacken at redhat.com
Fri Nov 30 01:30:14 UTC 2007

On Wed, Nov 28, 2007 at 10:26:10PM +0100, Michael Schwendt wrote:
> On Wed, 28 Nov 2007 16:09:10 -0500, Luke Macken wrote:
> > > I'll see what I can do about getting a digest of push updates sent out,
> > > similar to the rawhide report.
> > 
> > I implemented this in changeset 15cff3005c0b[0].  It will send a single mail
> > with the string representations of all of the latest testing updates
> > after each push.  They'll look different than the normal update notices;
> > if you guys don't like them, let me know and I can generate the other
> > ones instead.
> > 
> > This code path isn't exactly the easiest to test, so I updated our
> > production instance with it.  We'll see if it works during the next push
> > ;)
> > 
> > comments/suggests welcome!
> No spec changelog diffs?
> If you cannot use treediff (as used in the rawhide report) because of
> disk space constraints, it should still be possible to it similarly as
> in the Extras build report (which maintains a history of src.rpm
> changelogs in a small database in order to generate the diffs).

Good call, changelogs are pretty crucial.
I switched it back to producing a single digest of our normal
update-notices until I find a better way of doing it.


More information about the test mailing list