The www-apps/horde-pear ebuild has been changed in horde-pear-1.3-r3 to be a meta-package that RDEPENDs on dev-php/PEAR-* packages instead of using the outdated snapshot tarball that was used until horde-pear-1.3-r3. This new behaviour fixes "race conditions" between the www-apps/horde-pear package and the correspondig dev-php/PEAR-* packages and is also recommended by UPSTREAM. This is a request to all ARCHes to stabilize the www-apps/horde-pear-1.3-r3, dev-php/PEAR-Auth_SASL, dev-php/PEAR-Cache, dev-php/PEAR-Crypt_RC4, dev-php/PEAR-Date, dev-php/PEAR-DB, dev-php/PEAR-File, dev-php/PEAR-File_Find, dev-php/PEAR-HTML_Common, dev-php/PEAR-HTTP, dev-php/PEAR-HTTP_Request, dev-php/PEAR-HTTP_WebDAV_Server, dev-php/PEAR-Log, dev-php/PEAR-Mail, dev-php/PEAR-Mail_Mime, dev-php/PEAR-Net_DIME, dev-php/PEAR-Net_DNS, dev-php/PEAR-Net_Sieve, dev-php/PEAR-Net_SMTP, dev-php/PEAR-Net_Socket, dev-php/PEAR-Net_URL, dev-php/PEAR-Services_Weather, dev-php/PEAR-SOAP, dev-php/PEAR-Text_Wiki, dev-php/PEAR-Tree, dev-php/PEAR-XML_Parser, dev-php/PEAR-XML_Serializer, dev-php/PEAR-XML_Util packages. Reproducible: Always Steps to Reproduce:
Sebastian: did you know that you can add more than one CC at once? You're annoying a big bunch of devels with this, specially those who are on more than one arch alias. We're getting a zillion copies of this because each modification gets notified. So please, get a couple gmail addresses and play with a bug to see how it works (i have a couple of spare invites if you want). Thanks.
Gustavo: Sorry, I did not know that.
Removing mips since we don't have any keywords in any of these ebuilds.
I've tested them on ppc64 by installing them, but I don't have the time to do any further testing. ~ppc64 has been added to each of horde-pear-1.3-r3 dependencies. I'll mark them stable when x86 goes stable, as this seems to be *portable* php code. Whould this be a sufficient solution?
Markus: This sounds good to me. I would be interested what unportable PHP code looks like (apart from / and \ between *NIX and Windows).
Unportable PHP code looks pretty much identical to portable PHP code. That's part of what makes it so fun.
Stable on x86 and amd64.
Please don
Please don´t mark stable unless the dependencies are marked stable as well. # emerge -uDpv world These are the packages that I would merge, in order: Calculating world dependencies - !!! All ebuilds that could satisfy ">=dev-php/PEAR-PEAR-1.3.5-r1" have been masked. !!! One of the following masked packages is required to complete your request: - dev-php/PEAR-PEAR-1.3.5-r1 (masked by: ~x86 keyword) For more information, see MASKED PACKAGES section in the emerge man page or section 2.2 "Software Availability" in the Gentoo Handbook. !!! (dependency required by "dev-php/PEAR-Log-1.8.4" [ebuild]) !!! Problem with ebuild dev-php/PEAR-Log-1.8.4 !!! Possibly a DEPEND/*DEPEND problem. !!! Depgraph creation failed.
These ebuilds appear OK on SPARC. I am running into a problem where horde and/or mod_php don't think that PEAR-DB, PEAR-HTML_Common and PEAR-HTML_Select_Common are installed and I get various errors when trying to use horde because of that. How do I go about verifying php believes these packages are installed other than horde's test.php?
I initially created the list of PEAR packages that I put into www-apps/horde-pear-1.3-r3 as RDEPENDencies based upon the files that are in the horde-pear-1.3 tarball. I now reduced the RDEPENDencies to the PEAR packages that are listed in http://cvs.horde.org/co.php/horde/docs/INSTALL. The new list of packages that need to be stabilized is as follows: dev-php/PEAR-Mail_Mime-1.2.1-r1, dev-php/PEAR-File-1.0.3, dev-php/PEAR-DB-1.6.8, dev-php/PEAR-Log-1.8.4, dev-php/PEAR-XML_Parser-1.2.4, dev-php/PEAR-XML_Util-1.1.1, dev-php/PEAR-XML_Serializer-0.15.0, dev-php/PEAR-Net_DIME-0.3, dev-php/PEAR-Net_URL-1.0.14, dev-php/PEAR-Net_Socket-1.0.5, dev-php/PEAR-HTTP_Request-1.2.4, dev-php/PEAR-SOAP-0.8.1, dev-php/PEAR-Cache-1.5.4, dev-php/PEAR-Services_Weather-1.3.1, dev-php/PEAR-Date-1.4.3, www-apps/horde-pear-1.3-r3. I have never used Horde so I cannot comment on #9.
Alpha stable.
By emerging the versions in comment #10, horde was now not able to access even more PEAR modules than before. As the link indicated in comment #10 is for horde-3.0, can we get a list as to what applies to the current stable version of horde (2.2.7 on SPARC)?
stable on ppc64
Stable on sparc now that the php-pear eclass works with a sandbox.
already done for ia64
yeah, dunno what changed in the eclass, but it fixed things on s390 too thanks !
Already done on ppc.
Closing, thanks to the ARCH teams.
