Bug 1008846 - depending collections do not point into correct directory
depending collections do not point into correct directory
Product: Red Hat Software Collections
Classification: Red Hat
Component: php-pear (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 1.1
Assigned To: Web Stack Team
David Kutálek
Depends On:
Blocks: 1002434
  Show dependency treegraph
Reported: 2013-09-17 03:34 EDT by Marcela Mašláňová
Modified: 2014-06-04 03:17 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-06-04 03:17:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Marcela Mašláňová 2013-09-17 03:34:48 EDT
There are issues with dependent collection. Please, verify if your collection can also have same problem as Python/Ruby collection and apply fix for it. Otherwise comment why it can't be a problem and close as wontfix. Details can be seen in the tracker bug: rhbz#1002434, example in rhbz#994548.
Comment 2 Remi Collet 2013-09-17 04:13:18 EDT
Macros defined in php-pear

%__pear %{_bindir}/pear
%__pecl %{_bindir}/pecl
%pear_xmldir %{_localstatedir}/lib/pear/pkgxml
%pecl_xmldir %{_localstatedir}/lib/pear/pkgxml

Other macros are wrapper on the pear/pecl command, so probably doesn't need to be changed.
Comment 3 Remi Collet 2013-09-17 07:15:40 EDT
%pear_metadir is also concerned as this macro is new on recent version (don't exists in RHEL-6) and package expect it to not be defined.
Comment 10 errata-xmlrpc 2014-06-04 03:17:49 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.