Comment 43 for bug 676972

On Saturday 27,November,2010 04:57 AM, André Pirard wrote:
> On 2010-11-25 21:21, Martin Pitt wrote :
>> Accepted pidgin into lucid-proposed, the package will build now and be
>> available in a few hours. Please test and give feedback here. See
>> https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
>> enable and use -proposed. Thank you in advance!
> Glad to not just make a test every other year, like for my other reports.
> Thanks to everybody working on this !!!
>
> This test did *not* work for me at first and it wasn't until I hacked
> the DEB that I found why.
> The certificates are not in pidgin but in libpurple0.
> But pidgin...4.2 does not depend on libpurple0...4.2 which is, of
> course, *required*.
> So, my click on pidgin was a do-nothing.
> After sighs, sweat and thoughts, everything was superb.
>
> But hence, my conclusions are:
> - that many users don't follow -proposed but are eagerly watching their
> -updates for the word pidgin.
> - that those lucky enough to notice the wagon on the other track and
> jump on it may well fall over it.
> Even if the wagon were painted in purple for a hint ;-)
>
> It may even be argued that a Certificate update is a security update.
>
> For the sake of Ubuntu.

Updates are pushed to -proposed first for testing to make sure that they
actually work. After the packages in -proposed have been verified to work using
the test case, the bug is marked "verification-done" and the package is copied
to -updates. Otherwise it's just deleted from -proposed.

Perhaps what's needed is to make the instructions in the wiki page more verbose
to mention that all the binary packages from the source package (apt-cache
showsrc $pkg | grep Binary) need to be updated together before running the test
case.

--
Kind regards,
Loong Jin