13_migrate_oldconfig.patch is very silly

Bug #674188 reported by Luiten
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nicotine (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: nicotine

Hello,

I received a file called "13_migrate_oldconfig.patch", and if I interpret http://<email address hidden>/msg02644.html and http://launchpadlibrarian.net/51405259/nicotine_1.2.14%2Bdfsg-1ubuntu1.diff.gz correctly you apply this patch before you distribute Nicotine+ to your users.

You are very silly.

For the last two years the SLSK network had two servers, knows as the old server and the new server. These run on separate user databases, so an account on one server doesn't exist on the other server. This also goes for user privileges, if you have them on one server they don't work on the other. Because of this Nicotine+ deliberately doesn't force people to migrate to the new server but shows a warning instead, giving the user information so they can decide for themselves if and when to switch.

Your patch on the other hand forces everybody to join the new server, separating them from any privileges they might have had.* The original meaning of the code was well thought out, it puts people on the new server *ONLY* if their server setting points to mail.slsknet.org: There hasn't been a server behind this address for ages.

Could you please submit future patches upstream so I can tell you in advance that you're being very silly? Saves me the hassle of coming over here. Thanks in advance.**

* Yeah I know, not many people will be in that situation. But that's no reason to frustrate those that are
** While this report has been written in a satirical style, I do appreciate patches.

PS: To complete this report:
1) I don't use Ubuntu
2) I don't use Ubuntu
3) I expect distributions to send all patches upstream unless the only reason for the patch is to integrate the product with the OS
4) Ubuntu changed the working of a well contemplated section of source code to do something different entirely, frustrating end users and developers in the process.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.