Upgrade to 1.0.3 release

[dobey]

Binary package hint: ubuntuone-client

Please upgrade the package to the 1.0.3 release of ubuntuone-client as packaged in the linked branch. This update includes several bug fixes, some of which are critical and important for our users. It requires ubuntuone-storage-protocol 1.0.1 as it also includes a few fixes that we depend on in this versrion. Thanks!

[dobey (dobey)]

This and the new ubuntuone-storage-protocol are both in ppa:ubuntuone/stable for Karmic and Jaunty. Can someone install from there and please verify the mentioned bugs are fixed? Thanks.

[David (davidmarch007)]

Hello. I'll gladly give it a go on my near stock Karmic machines. What are the exact bugs you need tested?

[David (davidmarch007)]

Installed beta from PPA on a Karmic UNR netbook. Previously had an issue where U1 was not seemingly automatically updating a file which was added on another machine to the U1 folder from within Nautilus, nor doing so when manually connecting. After installing from the PPA U1 seemed to connect properly. It didn't appear that it automatically added the file so I clicked Connect within Nautilus. It then indicated it was updating the files and verified that it added 1 file. This is an improvement over previously where even manually clicking connect did nothing for me. Will check for specific bugs you need checked, just let me know exactly which ones please. Will also do more testing more methodically and detailed testing cases and will document.

[Mathias Gug (mathiaz)]

Fixed in the devellopement release (1.1.0).

[Mathias Gug (mathiaz)]

Accepted for Karmic. Please follow the process for a Stable Release Update outlined in https://wiki.ubuntu.com/StableReleaseUpdates#Procedure.

In particular the bug description needs to be updated with the following information:

Update the bug report description and make sure it contains the following information:

   1. A statement explaining the impact of the bug on users and justification for backporting the fix to the stable release
   2. An explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix.
   3. A minimal patch applicable to the stable version of the package. If preparing a patch is likely to be time-consuming, it may be preferable to get a general approval from the SRU team first.
   4. Detailed instructions how to reproduce the bug. These should allow someone who is not familiar with the affected package to reproduce the bug and verify that the updated package fixes the problem. Please mark this with a line "TEST CASE:".
   5. A discussion of the regression potential of the patch and how users could get inadvertently affected.

[Benjamin Drung (bdrung)]

I unsubscribed ubuntu-sponsors. Please provide all requested information, a debdiff for sponsoring and then resubscribe ubuntu-sponsors again.