Laney, SRU info added to description.
Well, when you looked at the im-config MP yesterday, no code for removing 80im-switch was there actually. (Code for removing 80im- config_launch was there, though.) Today is another thing. ;-) Since I try to minimize the differences to Debian, I now propose that the 0.21 version of debian/postinst is merged. Even if that file does contain code for removing 80im-switch, the latter won't be removed here since the md5sum for 80im-switch on Ubuntu is not listed. So, with the extra condition I added in revision 26 in my branch, it should be ok, and everyone should be happy. :) ** Description changed: - In raring, we are replacing im-switch with im-config, but when im-switch - isn't purged but only removed, scripts in /etc/X11/Xsession.d/ will - still try to set related variables, so that im-config cannot work - correctly. + Nomination of im-switch for Precise and Quantal SRUs + ==================================================== + + [Impact] + In raring, we are replacing im-switch with im-config, but when im-switch isn't purged but only removed, scripts in /etc/X11/Xsession.d/ will still try to set related variables, so that im-config cannot work correctly. + + [Test Case] + Steps to reproduce: + * Make sure you have an updated Precise or Quantal. + * Select "ibus" from Language Support. + * Remove im-switch without purging. + * Log out and log in again. + * Run "env | grep IM" from a terminal window and find that im related + environment variables were set when they shouldn't. + + [Regression Potential] + None. + + Remaining from original description + =================================== Fixing im-switch in Precise and Quantal is part of the solution to this problem, something else must be done for those who haven't got the chance to upgrade to the fixed version. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to im-switch in Ubuntu. https://bugs.launchpad.net/bugs/1101836 Title: Needs to keep hands off when removed but not purged Status in “im-config” package in Ubuntu: In Progress Status in “im-switch” package in Ubuntu: In Progress Status in “im-config” source package in Precise: Invalid Status in “im-switch” source package in Precise: Fix Committed Status in “im-config” source package in Quantal: Invalid Status in “im-switch” source package in Quantal: Fix Committed Status in “im-config” source package in Raring: In Progress Status in “im-switch” source package in Raring: In Progress Status in “im-config” package in Debian: New Status in “im-switch” package in Debian: Fix Released Bug description: Nomination of im-switch for Precise and Quantal SRUs ==================================================== [Impact] In raring, we are replacing im-switch with im-config, but when im-switch isn't purged but only removed, scripts in /etc/X11/Xsession.d/ will still try to set related variables, so that im-config cannot work correctly. [Test Case] Steps to reproduce: * Make sure you have an updated Precise or Quantal. * Select "ibus" from Language Support. * Remove im-switch without purging. * Log out and log in again. * Run "env | grep IM" from a terminal window and find that im related environment variables were set when they shouldn't. [Regression Potential] None. Remaining from original description =================================== Fixing im-switch in Precise and Quantal is part of the solution to this problem, something else must be done for those who haven't got the chance to upgrade to the fixed version. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/im-config/+bug/1101836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
