Bug 606774 – dev-php/PEAR-PEAR-1.10.1-r1 : * ERROR: dev-php/PEAR-PEAR-1.10.1-r1::gentoo failed (postinst phase):

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Toralf Förster 2017-01-22 08:52:51 UTC]

Trying channel "pear.php.net" over https:// instead
Cannot retrieve channel.xml for channel "pear.php.net" (Connection to `pear.php.net:443' failed: Connection timed out)
 * ERROR: dev-php/PEAR-PEAR-1.10.1-r1::gentoo failed (postinst phase):
 *   failed to update channels
 * 
 * Call stack:

  -----------------------------------------------------------------

  This is an unstable amd64 chroot image (named hardened-unstable_20170120-150937) at a hardened host acting as a tinderbox.

  -----------------------------------------------------------------

gcc-config -l:
 [1] x86_64-pc-linux-gnu-6.3.0 *
llvm-config --version:
3.9.1

Available Python interpreters, in order of preference:
  [1]   python3.4
  [2]   python2.7 (fallback)
Available Ruby profiles:
  [1]   ruby21 (with Rubygems) *
java-config:

  -----------------------------------------------------------------

[Comment 1 Toralf Förster 2017-01-22 08:52:54 UTC]

Created attachment 460892 [details]
emerge-info.txt

[Comment 2 Toralf Förster 2017-01-22 08:52:57 UTC]

Created attachment 460894 [details]
dev-php:PEAR-PEAR-1.10.1-r1:20170122-004250.log

[Comment 3 Toralf Förster 2017-01-22 08:53:00 UTC]

Created attachment 460896 [details]
emerge-history.txt

[Comment 4 Toralf Förster 2017-01-22 08:53:03 UTC]

Created attachment 460898 [details]
etc.portage.tbz2

[Comment 5 Michael Orlitzky 2017-01-22 17:15:48 UTC]

This is unfixable at the moment. Our packages aren't supposed to rely on the network being available, but PEAR-PEAR does. In a perfect world, we wouldn't need the "pear" executable to "cp -r" a bunch of files into place, but that's what the php-pear-r1 eclass is doing.

This pkg_postinst() phase that hits the network should be pkg_config() instead. It should only be run by users who want to use the "pear" executable, after installation, and ideally behind something like USE=executable. However, as long as the php-pear-r1 eclass assumes that the "pear" executable exists and is set up to use the network, I can't fix it without breaking all consumers of that eclass. I can't even move it to pkg_config() because PEAR-PEAR might only get pulled in as a dependency of something else that will try to use it before you get a chance to emerge --config.

I've been slowly dropping that eclass where I can, but this is essentially blocked on the removal of php-pear-r1.eclass.

[Comment 6 Brian Evans (RETIRED) 2017-02-20 21:51:42 UTC]

I believe this is related to pear.agavi.org being unavailable.

I have removed it from the PEAR-PEAR ebuild.  Please retry and confirm

[Comment 7 Toralf Förster 2017-02-21 10:04:15 UTC]

(In reply to Brian Evans from comment #6)
isntalls fine now