Natty needs to bundle 2.4.1 or data loss occurs when network is down

[Tom Chiverton]

Binary package hint: amarok

https://bugs.kde.org/show_bug.cgi?id=268767

[Tom Chiverton (bugs-launchpad-net-falkensweb)]

Only v2.4.0 is installed if I'm reading dpkg right, which will lose user ratings if the network share with the file on is not available when Amarok is started. See upstream for details.

[Tom Chiverton (bugs-launchpad-net-falkensweb)]

Why is this invalid ?

[Jonathan Thomas (echidnaman)]

The upstream bug is marked as invalid, not the Ubuntu one.

[Myriam Schweingruber (myriam)]

Jonathan, the upstream bug is not marked as invalid, but as a duplicate of an already solved bug: https://bugs.kde.org/show_bug.cgi?id=268739

Tom, it is not possible to ship Natty with Amarok 2.4.1, as the latter is not released yet and will not make it before the freeze. There will be an update available soon enough, check http://kubuntu.org for announcements of available packages. You are of course free to already use the beta version of 2.4.1

[Tom Chiverton (bugs-launchpad-net-falkensweb)]

Wow, so you'll ship with a known data loss bug (and not a little one, and not one that's hard to trigger) rather than ship the perfectly fine and stable Amarok 2.4.1 beta (no regressions spotted so far) and then the minor update to the release version ?

[Jonathan Thomas (echidnaman)]

@Mariam

I know it wasn't marked as invalid. Launchpad considers Bugzilla's duplicate status as invalid, which is why the Bug Watch Updater marked it as "invalid".

[Myriam Schweingruber (myriam)]

Sorry Tom, there is nothing we can do about that, the package freeze simply doesn't allow to ship an application that is not even released yet.
Also this is not a bug affecting a majority of users, nor is it a security problem, and you do not loose any files, only ratings. Make sure to save your database (something that should always be done before an upgrade anyway) so you can get back the ratings once the fix is backported.

[Tom Chiverton (bugs-launchpad-net-falkensweb)]

if you cant alter the version shipped then, why not bring over the very small patch into your 2.4.0 version ?
I disagree with the overall charaterisation of the bug - this is a very popular application, though I realise the focus is on Unity and GNOME. While not a security problem, you wouldn't ship an email client that moved all your mail out of folders and into the inbox if your printer is unplugged would you ? That's the same metadata loosing scenerio.
There's never been anything in the release notes about backing up obscure files in the .kde directory before - take it there will be this time then ?