[pkg-php-pear] Uploading spree (Was: php-symfony2-yaml to php-symfony-yaml transition)

David Prévot david at tilapin.org
Tue Sep 23 22:31:38 UTC 2014


Hi,

FYI (even if you may have already noticed the “processing of
[…]_amd64.changes” and soon to come “[…]_amd64.changes ACCEPTED into
unstable” message flood), I just went on with the php-symfony-yaml
transition, including pear-channels (to drop the now obsolete override),
phpunit-mock-object (to allow running the symfony and aws-sdk-for-php
tests), and also doctrine that used to build-depend on php-symfony2-yaml.

That means that no local tricks won’t be needed anymore to build symfony
(pear-channels and phpunit-mock-object have been fixed), and you may
already start testing the transition in real life from INCOMING if you
can’t wait a few hours for the next dak run to test it from Sid.

I may take care of the other php-symfony-* standalone packages tomorrow,
unless Daniel let us now symfony is ready, in which case I’ll look into
it first.

Regards

David

P.-S.: for reference, the uninteresting message I thought to send
yesterday to announce my plans, and lamely attached encrypted in another
message. Nothing interesting here, just for tho posterity…

Hi,

Le 22/09/2014 08:12, David Prévot a écrit :

> There is just one detail that should make things a bit easier

On my way to prepare the php-symfony-* standalone packages to
2.3.19-1(~sid1), I finally came across that last one, and it’s not as
smooth as I would have hopped.

> 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).

Actually, since as you already pointed, there are some versionned
(build-)dependencies around, and given that versionned provide can’t be
used before Jessie gets released (apt in Wheezy would choke on them), we
actually need to synchronize the upload of the build-dependencies
quickly enough to get rid of php-symfony2-yaml.

>> 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 ;).

Given that versionned provide can’t be used before Jessie gets released
(apt in Wheezy would choke on them), we should synchronize the upload of
the build-dependencies to get rid of php-symfony2-yaml, I intend to go
that path (consider that as an explicit in advance warning of my intent
to team upload phpunit, and the others, for which I’m already the
(unique) uploader anyway). I’ll also take care of doctrine that
currently build-depends on php-symfony2-yaml (I don’t even remember why
— EDIT: it’s for the scripts provided in bin, that is run at build time
to generate the manpage via help2man).

Since I’m done preparing the php-symfony-* standalone updates, I will
now check that all reverse (build-)dependencies are still working with
these new versions (that had to be done before uploading symfony
anyway), and once ready, I’ll upload them all (well, starting with
php-symfony-yaml and all related packages). That may happen pretty soon
(aka tomorrow or the day after).

Regards

David

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


More information about the pkg-php-pear mailing list