Ticket #991 (closed defect: fixed)

Opened 12 years ago

Last modified 11 years ago

Dependency Resolution difference between Package and yum

Reported by: Owned by: desai
Priority: major Milestone: Bcfg2 1.2.0 Release
Component: bcfg2-server Version: 1.0
Keywords: Cc: [email protected]…, [email protected]


I'm running BCFG2 1.1.0 on CentOS 5.5 and there seems to be an issue with the Package plug-in. I have an Apache+PHP bundle which contains the following packages:

<Package name='httpd'/>
<Package name='php'/>
<Package name='php-pecl-apc'/>
<Package name='php-pecl-memcache'/>

The YUM sources are set to the official CentOS 5.5, EPEL and REMI. Now BCFG2 want to install php-devel on the web servers whereas YUM does not require this.


bcfg2-package-php-debug.log (60.0 KB) - added by 12 years ago.
debug log generated using bcfg2-info

Change History

Changed 12 years ago by

debug log generated using bcfg2-info

comment:1 Changed 12 years ago by

comment:2 Changed 12 years ago by solj

  • Cc [email protected] added
  • Milestone changed from Bcfg2 1.2.0 Release to Bcfg2 1.3.0 Release

It appears as though yum's dependency handling is incorrect in this case. In your debug log, it shows php-pecl-apc requires /usr/bin/pecl. php-pear provides /usr/bin/pecl and therefore satisfies that dependency. The php-pear package lists php-devel as a requirement.

Packages: Package php-pecl-apc added requirements set(['rtld(GNU_HASH)', '', '', '', '', 'php(api)', '/usr/bin/pecl', '/bin/sh', '', 'php(zend-abi)', ''])
Packages: requirement /usr/bin/pecl satisfied by set(['php-pear'])
Packages: Package php-pear added requirements set(['php-devel', 'php-cli'])

comment:3 Changed 11 years ago by

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone changed from Bcfg2 1.3.0 Release to Bcfg2 1.2.0 Release

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.