Bug#231862: closed by John Ferlito <johnf at inodes.org> (libvorbis0a: oggenc still dies sometimes with floating point exception)

[John Ferlito]

Hi Helge,

On Sun, Apr 04, 2010 at 04:42:07PM +0200, Helge Kreutzmann wrote:
> Hello John,
> On Sat, Apr 03, 2010 at 03:33:08AM +0000, Debian Bug Tracking System wrote:
> > This bug is ancient and is most likely fixed. Feel free to re-open if
> > you don't think that is the case.
> 
> What kind of bug maintenance is this????

<snip>

I find it unfortunate that you find the need to simply jump to
conclusions and send such an incendiary email in a public forum,
rather than perhaps send me a quick private email to find out why I
went down this path.

I have only recently taken over maintenance of these packages in an
effort to try and clean up the mess that has been accumulating for
many years. With a goal to try and keep them maintained much better,
seeing as I do have some time to devote to this whereas past
maintainers may not have.

libvorbis, vorbis-tools and libao have not been maintained in an
extremely long time. I have spent the past two days of my Easter
creating new packages since upstream have finally after many years
released new versions.

This required me to go through approx 60 bugs, most of them dating
back to 2004 and 2005 which are simply not relevant to the current
code base.

For most bugs including this one I took the time to have a quick look
at the source code and change logs to try and ascertain whether or not
the bug was likely fixed. This involved me taking one of a
couple of steps

a) Pushing the bug upstream where I confirmed it was still an issue

b) Closing bugs that were unreproducible and no response had been
heard from the original submitter when queried

c) Closing bugs where it seemed unlikely there was a problem any
longer asking for them to be reopened if it was believed the problem
still existed

d) probably some others I can't remember right now

For this bug and many others, (Keep in mind this bug was originally filed
back in 2004, that's 6 years ago now), after a quick look at the code
and considering the amount of time I came to the conclusion that
it was extremely unlikely that the bug still existed and chose option
c).

Thank you very much for taking the time to indeed confirm that this
bug is most likely no longer relevant.

Cheers,
John

-- 
John
Blog                             http://www.inodes.org
LCA2010                          http://www.lca2010.org.nz