The aotuv patches are missing from libvorbis 1.2.2. While looking at the ebuild, I see that the maintainer mistakenly though aotuv was merged in 1.2.2. It was not. It is scheduled for merge in 1.3.0. Monty's announcement: "Work has already begun on the next two libvorbis releases. The approximate roadmap is: the async error interface just added to libogg will be the next change to libvorbis, and will be the basis of the 1.2.3 release. AoTuV merges are scheduled for immediately after and will form the basis of 1.3.0."
Latest aotuv is broken ( as you can see for yourself by searching our bugzilla by keyword libvorbis ) So unless they release new aotuv .. or it gets merged, it's unlikely we downgrade our users to broken version
and we are up to 1.2.3, and still no new aoTuV release, closing as RESOLVED, UPSTREAM
Well you didn't have to remove it from portage completely. The aotuv patched 1.2.1 RCs are better than any later version. It's a popular Vorbis tuning and tested to provide better sound than vanilla Vorbis. Most people aren't updating to 1.2.2 at all because 1.2.1+aotuv is still better.
(In reply to comment #3) > Well you didn't have to remove it from portage completely. It isn't. The 1.2.1_rc1-r2 version is actually the latest stable.
Latest aoTuV was broken, the one in 1.2.1_rc1-r1 is the last working one in fact... Also libvorbisfile in libvorbis-1.2.2 was broken. So we have latest _working_ aotuv+libvorbis in stable. And latest _working_ libvorbis in ~arch for which there isn't aoTuV released. But I'm requesting latest libvorbis stable pretty soon, and with it, aoTuV will disappear.. again, not our problem, there's no upstream release for it
*** Bug 468526 has been marked as a duplicate of this bug. ***
