Red Hat Bugzilla – Bug 215440
circular build dependency for php-pear and php
Last modified: 2014-01-21 17:55:54 EST
Description of problem:
php-pear requires php to build. php requires php-pear to install.
php cannot be installed via a mock style build setup to build php-pear, because
it requires php-pear.
Version-Release number of selected component (if applicable):
php-pear-1.4.9-1.2 and php php-5.1.6-1.2
Steps to Reproduce:
1. remove php-pear from mock build repository (to 'start fresh')
2. build php and create metadata for build repo to use php (builds fine)
3a. (cheat, and run repoclosure to see the missing php-pear)
3b. go the full build route, and attempt to build php-pear.
build will fail because php cannot be installed without php-pear
build succeeds and build system is allowed to work
Previous versions of php-pear complete the dependency allowing it to be built,
but the dependency chain is not 100% proper.
This is intentional to preserve php-pear on upgrades.
to preserve it on upgrades? It's not possible to rebuild it from raw packages.
How does that preserve anything?
I meant to preserve the existence of PEAR on the system from when PEAR was not
split out from the php package.
php-pear BRs php is a genuine build dependency.
php-pear BR's php
php Requires php-pear for install.
so when you make the chroot to build in - you cannot build php-pear w/o first
having a php-pear available.
Yes Seth, it's a circular dependency, it's perfectly intentional, and it's not a
At some point the "php Requires php-pear" dependency can be dropped when we no
longer have to care about upgrades from distros without the php-pear package
split, but not yet and certainly not from the FC5 package.
And all I'm saying is that it is impossible to build the packages with a
circular dep w/o first having the package. As long as that's clear and isn't
propagated into fc6 and therefore rhel5.