[pkg-php-pear] Getting rid of pear-*-channel in favor of pear-channels

[David Prévot]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi pear-{aws,horde,phpunit,symfony-project}-channel maintainers,

pear-channels has just been accepted in the archive, and it Replaces,
Provides and Conflicts: pear-aws-channel, pear-doctrine-channel,
pear-guzzle-channel, pear-horde-channel, pear-phpunit-channel,
pear-symfony-project-channel, pear-symfony2-channel

The next move would then be to ask for removal of the remaining
pear-*-channel packages: the (build-)dependencies will pick
pear-channels instead already if the actual pear-*-channel package is
not available as I’ve tested it in some packages already.

Is there anything that should stop us from asking for pear-*-channel
removal? If not, I’ll submit a bug report against ftp.debian.org next
week for this four packages (or sooner as I get positive acknowledgments).

The following step will be to update the (build-)dependencies to use
pear-channels directly, I guess you already maintain most of them so
that should be easy, lintian (or “cme check dpkg”) should warn about
that anyway once the pear-*-channel packages will be gone, and we can
still propose a MBF later to get rid of the remaining (build-)dependencies.

Regards

David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJSbrr+AAoJEAWMHPlE9r089PAH/1SEnmakAnNZnmKGkZCbyYgr
6kzl7trkLWCBx7Mlca99OSORgESJxxpkYboofilY+sSfBp0DuWiGXav1yMWP900Z
K87OI2IOt0oGb3qrojt8Ud7gbeMXVvgsTqbi7aP3xjZTe4BtkT7wZjJkcjbrkU12
Zx0vId66v7yg++3Kk3BiDAqBnhVwHMihbbwEkEtfPJibI+hijkhNWNbsaBu+D9o7
5mJbi3kcVOm/pkq5lPcZQNEQF8NQwg32FJbZrC6WHyyWBIlABB1/V4YQe340M6Zb
dgSO4psuUTEg8XSnde4NbA06yyZ9m3gJxw0dabWSlgLKIrgqFZyFYjcbRiaGdgI=
=ASjW
-----END PGP SIGNATURE-----