[pkg-php-pear] php-symfony2-yaml to php-symfony-yaml transition

David Prévot david at tilapin.org
Mon Sep 22 12:12:12 UTC 2014

Hi Daniel,

Agreed on all points of your previous message: it seems to match exactly
what I’ve tried to plan (last time I came across an actual
php-symfony-yaml – version 1 – used in a package, I embedded the code
copy instead of depending on php-symfony-yaml, to make sure it won’t
come across our way for this move). There is just one detail that should
make things a bit easier:

Le 22/09/2014 03:59, Daniel Beyer a écrit :
> 1. Upgrade php-symfony-yaml to 2.3.19-1~sid1 and let it
>    Conflicts: (+Breaks?, +Replaces:?) with php-symfony2-yaml

Following policy 7.6.2, Provides, Conflicts, and Replaces should do the
trick. Indeed it worked well for pear-channels: it allowed us get rid of
the existing pear-*-channel packages pretty quickly without the need to
update all existing (build-)dependencies (some are still around).


Using the same trick in the php-symfony-yaml package built from the
proper symfony source will ensure consistency (or even vanish the need
of updating the php-symfony-yaml standalone package, that I’ll be
preparing anyway following this plan).

> 3. Update/rebuild all packages (see below) depending on
>    php-symfony2-yaml to now depend on php-symfony-yaml.

That should “only” be needed for packages currently depending on
specific version of php-symfony2-yaml (i.e., two packages if your count
is correct, that are both team-maintained, so that should be really
quick ;).



P.-S.: things are easy when, as a team, we have everything under our
control ;).

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-php-pear/attachments/20140922/4427c426/attachment.sig>

More information about the pkg-php-pear mailing list