Thomas,

You have only build your latest openal fix:
openal-soft-1.10.622-3.3793919892e6d61e5fec3abeaaeebc3f2332be13git.fc12

For Fedora-12 and not for development. Meaning that people upgrading from F-12 to F-13 / rawhide, will keep the F-12 build of the package as that is the newest. This is not what we want as from version to version things like compiler flags (and version) etc, may change, so we want people to get an F-13 build when updating to F-13.

So please copy your F-12 changes to the devel branch in CVS and do a build there too. Also next time it would be good to first make the changes in the devel branch and then copy them back to the F-12 branch, this is how I always work and this makes sure that you don't forget to build for the devel branch.

###

While on this subject when you made the specfile fixes for F-11 you also created a broken upgrade path from F-11 to F-12, as then you had:
F-11: openal-soft-1.10.622-3.fc11
F-12: openal-soft-1.10.622-2.fc12

Making the F-11 version newer then the F-12 one, what you should do in cases
like this, where you only want to make changes to an older release is add a .1
(and if a second fix is needed .2, etc.) after the %{?dist}, then the
releases would have become:
F-11: openal-soft-1.10.622-2.fc11.1
F-12: openal-soft-1.10.622-2.fc12

Making the F-12 version newer, note that with your recent rebase to git fix,
this is no longer needed as now we have:
F-11: openal-soft-1.10.622-3.fc11
F-12: openal-soft-1.10.622-3.3793919892e6d61e5fec3abeaaeebc3f2332be13git.fc12

And rpm happens to think that the F-12 version is newer (normally you should
never trust on this, but I verified using the rpmdev-vercmp command).

Regards,

Hans