pidgin uploaded to unstable

[Martin-Éric Racine]

This is an extremely messy way to handle the upgrade.

The correct way would have been to get every plug-in to build
gaim-foobar as a dummy package depending upon pidgin-foobar.

Likewise, piding should have been built and uploaded with a dummy
package called gaim that depends upon pidgin.

On 5/7/07, Ari Pollak <ari at debian.org> wrote:
> Hi all,
>
> You're getting this message if you're listed as the maintainer or an
> uploader of a gaim plugin package.
> Pidgin has been accepted into unstable, and I plan to upload
> transitional dummy packages from gaim to pidgin in two weeks or so. This
> means that you should be getting your separate pidgin plugin packages
> uploaded ASAP, so that they have enough time to go through NEW. As a
> quick checklist, you should be doing the following:
> - Create a new package called pidgin-plugin, where it used to be called
> gaim-plugin, with the sources separate from the gaim-plugin package.
> - The build should be almost identical to the gaim plugin package, but
> change the build-dependency from gaim-dev to pidgin-dev, and change
> running dh_gaim to dh_pidgin.
> - Prepare a gaim-plugin dummy package that just depends on
> pidgin-plugin, but don't upload this until the gaim dummy packages are
> uploaded. I'd be glad to upload your package at the same time as the
> dummy gaim packages, just let me know.
>
> As always, if you have any questions, please let me know.
>
> Thanks,
> Ari
>
>


-- 
Martin-Éric Racine
http://q-funk.iki.fi