 |
|
 |
We are aware of this ... it is also upstream. As is the case with any update, one should look for and fix any .rpmnew (or .rpmsave) files that result from the update. In this case, one should replace the jar files in question with the .rpmnew jar file. |
|
|
You, I and many know this. Those who updated using yum from the terminal will have seen the messages and have like us fixed the issue locally. However, many users who used a GUI updater i.e. 'gnome-packagekit' are likely unaware of the issue. Maybe an email out on the list(s) informing people of the issue and remedy would be the correct thing to do? |
- Anonymous
