https://bugzilla.novell.com/show_bug.cgi?id=712749
https://bugzilla.novell.com/show_bug.cgi?id=712749#c70
--- Comment #70 from Kalenz .
it seems Amarok needs to be rebuilt every time mysql is updated
If this is the case, then the simplest solution IMHO is for the Amarok packagers to specify a requirement for mysql=5.5.16 (for example), rather than mysql>=5.5.16. This will trigger a dependency conflict warning from zypper/YaST when a new MySQL becomes available: - Desktop user case: keep old mysql (and functioning amarok). - Server user case: upgrade mysql (amarok probably not installed). Then, when a new amarok becomes available (compatible with new mysql), a zypper/YaST update will automatically pull in the latest mysql and amarok.
you need a fix that doesn't require a rebuild with every mysql update
Not strictly necessary... but probably wouldn't be a bad idea! I would have thought that the mysql developers make considerable efforts for backward compatibility... More in general, I should perhaps clarify that my last post was not meant as an attack to any individual, and I appreciate everybody's great work on Amarok and openSUSE. But irrespective of this *specific* instance (resolving amarok-mysql dependencies), it worries me that *in general* it is apparently possible for an important openSUSE component to be broken for so long. Which means, there is something wrong with the system, something wrong with how we communicate here. This bug simply did not get the attention it deserved, fast enough. I hope that, after this bug is permanently resolved, maintainers will give some thought to "how do we make sure this doesn't happen again". Not just with amarok/mysql, but in general, with any (important) part of openSUSE. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.