Description of problem: Latest upgrade caused yum upgrade to break Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. yum upgrade Actual results: sudo yum upgrade [...] --> Running transaction check --> Processing Dependency: libopenal.so.0 for package: torcs --> Processing Dependency: libopenal.so.0 for package: scorched3d --> Finished Dependency Resolution Error: Missing Dependency: libopenal.so.0 is needed by package torcs Error: Missing Dependency: libopenal.so.0 is needed by package scorched3d See also bug #183133, bug #183134. Expected results: Upgrade should have worked. Additional info: There should be better co-ordination of releases of this package with the maintainers of dependent packages, before it reaches the end user. It seems a general problem with extras that maintainers are unaware of the influences their package updates have on other packages. There really needs to be some automated system that could notify them. It's my one major beef with Extras right now. Another example is the R package, see bug #176763.
As I said in #181989, I am sorry for this. I am aware that there are a number of packages like blender, torcs, scorched3d and so on require openal and would need a rebuild due to soname changes in openal. This soname change was meant as a fix for broken versioning but as this was just brought to the openal dev's attention by the debian maintainers of openal to exactly avoid a situation like we have here now I did not think that there where any changes in cvs regarding this. Reverted back to the old cvs snapshot for now. In a side note: I think you are right... There should be ways that this kind of stuff is automated and not visible for endusers in case something like this happens...