** No longer affects: wslu (Ubuntu Focal) ** Description changed:
[Impact] - For groovy/hirsute, - this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. - - For focal, - it is proposed to be updated from 2.x to 3.x in 20.10/21.04 circle. + this affects wslu 3.x which, when tries to start with a clean + environment after upgrade, the terminal will throw `rm: file not found` + error. [Test Case] - - For groovy/hirsute: * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. - For focal: - - * Follow the testing process outlined in https://wiki.ubuntu.com/wslu-Updates - * Run the autopktest in a WSL environment. - * View the result of the test, with 7 Windows Explorer open and 3 webpage open on the default browzer. - [Regression Potential] - - For groovy/hirsute: This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. - - For focal: - - This is a large version update from 2.x to 3.x. according to the - previous process merging to groovy on bug LP: #1895525, there is no - clear issue. Potential regressions would be a result of badly generated - ~/.config/wslu/. ** Summary changed: - [SRU] wslu 3.2.1-0ubuntu2 + [SRU] wslu 3.2.1-0ubuntu2 to hirsute and groovy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to wslu in Ubuntu. https://bugs.launchpad.net/bugs/1911379 Title: [SRU] wslu 3.2.1-0ubuntu2 to hirsute and groovy Status in wslu package in Ubuntu: New Status in wslu source package in Groovy: New Status in wslu source package in Hirsute: New Bug description: [Impact] this affects wslu 3.x which, when tries to start with a clean environment after upgrade, the terminal will throw `rm: file not found` error. [Test Case] * Install Ubuntu 20.10 to WSL. * run any wslu tools (like wslfetch) * Verify that there is no `rm -rf` error. [Regression Potential] This patch will try to remove ~/.config/wslu/ to order to reset to default state (especially when first upgrade to latest wslu). Potential regressions would be a result of ~/.config/wslu/ not being cleaned properly. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wslu/+bug/1911379/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
