Package: wordpress-l10n Version: 3.0.5+dfsg-1 Severity: important I just ran into the following problem:
wordpress was upgraded, but wordpress-l10n was not (I was upgrading to the squeeze version of wordpress on Ubuntu, but this issue will also be present on e.g. 3.0 -> 3.x upgrades). I ended up with wordpress 3.0 and wordpress-l10n 2.9, which is not exactly a proper setup. Please let wordpress-l10n depend on the exact version and revision of wordpress (e.g. 3.0.5+dfsg-1). Since both packages are Architecture: all also that shouldn't cause NMU problems. For preventing the problem to happen e.g. on squeeze -> wheezy upgrades, wordpress should conflict with unfixed versions of wordpress-l10n. Thanks in advance Adrian -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
