[ogg-dev] Make check failure

Timothy B. Terriberry tterribe at email.unc.edu
Mon Apr 5 01:57:45 PDT 2010

Erik de Castro Lopo wrote:
> Gregory Maxwell wrote:
>> Nothing is broken.
> The test suite failed. AFAIAC, that means that what is in HEAD is not
> currently fit for release.

The test suite should already be fixed, see r17124. Thanks for reporting
the problem.

> If for instance there was new CVE released against libogg, how do 
> you do a new release that fixes that CVE without fixing the other
> issues as well?

The amount of code in libogg is so small and changes so infrequent that
it would be trivial to backport almost any conceivable change to the
prior release tag (which was just a few days ago) and work from there,
if that was necessary. In fact, in Monty's work with Red Hat, they have
usually _required_ him to backport security fixes to all prior releases
and make new point releases with them, because they are still shipping
old versions in many of their stable products.

In this case, fixing the test suite was also relatively easy. No need to

More information about the ogg-dev mailing list