[pkg-php-pear] Bug#813125: Bug#813125: php-proxy-manager 2.0.0* has a dependency on a new PHP API PackageVersions

[Nish Aravamudan]

On 29.01.2016 [18:31:11 -0400], David Prévot wrote:
> Hi,
> 
> Le 29/01/2016 12:39, Nishanth Aravamudan a écrit :
> > Package: php-proxy-manager
> > Version: 2.0.0-*
> 
> Not in Debian.

Yes, I understand that. I apologize for not being clear. It seems like
the upstream maintainer is stating that phpunit failures with PHP7 +
1.2.0 are expected -- so we'd need to update the tests in the Debian &
Ubuntu packages.

> > While updating the packages in an Ubuntu Xenial PPA to use PHP7.0 by
> > default, I ran into phpunit failures with the php-proxy-manager package.
> 
> From #811431:
> 
> Again (#810526#10), you may wish to not file such bugs currently [0]:
> the (soon to be) ongoing transition of php will require a lot of rebuild
> (and NEW processing). We already know that, but all the tools are not
> yet in place.
> 
> 0: https://lists.debian.org/debian-devel-announce/2016/01/msg00002.html

Yep, I'm aware of this and am in contact with Ondřej on the progress in
Ubuntu for the same transitions (I've got phpunit bootstrapped at this
point but am hitting another build-depends cycle).

> > The same issues should be seen with Debian unstable.
> 
> FWIW, with what is currently in Debian, I don’t get such issue.

Right, because, I'm expecting that the php-proxy-manager package is
still depending on PHP5, rather than PHP7.

> > I see that per https://packages.qa.debian.org/p/php-proxy-manager.html,
> > there is a 2.0.0~beta1 available to package.
> 
> Even 2.0.0~beta2, I already prepared the package for experimental, will
> push my changes to the VCS tomorrow.

Ok, thanks, I'll take a look!

> > […] it has a dependency that prevents it
> > from successfully packaging currently. The upstream code has introduced
> > a new dependency on https://github.com/Ocramius/PackageVersions, which I
> > am guessing would need to be packaged as a new package, i.e.,
> > php-package-versions.
> 
> I instead patched the package to not use this new dependency.

Ok, I'll look at your version when it's in the VCS tomorrow.

-- 
Nishanth Aravamudan
Ubuntu Server
Canonical Ltd