Comment 0 for bug 2073801

phpunit depends on php-deepcopy and built against php-deepcopy 1.11.1. Meanwhile the newer php-deepcopy 1.12.0 runs tests against itself using phpunit during *build time*; phpunit needs the older php-deepcopy but can't install it, which causes the tests to fail and in turn causes php-deepcopy to FTBFS. With no build for the new php-deepcopy it's not possible to no-change rebuild phpunit to get around this.

Debian gets through this by performing binary-only uploads followed by a source upload, however Ubuntu policy disallows that approach.

A workaround we've used in the past is to temporarily disable running the tests during build for the problematic package(s), versioning the package with a "maysync1" suffix so that the package can be re-sync'd after the migration completes.

Ideally, the packaging should be fixed to not enter this messy situation to begin with. An approach is being explored with Debian to adjust the autoload.php include to use a relative rather than absolute path in all packages in the dependency chain.