Summary: | mod_php-4.4.0 blocks >=apache-2.0.54-r30, apache-2.0.54-r31 is stable | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Pablo Yanez Trujillo <shaoran> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | christian.strauf, linuxnoob, moixa, toto |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Pablo Yanez Trujillo
2005-09-18 15:35:34 UTC
Unmerge old mod_php-4.4.0 first, you need mod_php-4.4.0-r2 for apache-2.0.54-r31. *** This bug has been marked as a duplicate of 79606 *** *** Bug 106490 has been marked as a duplicate of this bug. *** Emerging mod_php 4.4.0-r2 is not the solution to the problem because the ebuild still features the line --------8<--------8<--------8<--------8<-------- DEPEND_EXTRA=">=net-www/apache-1.3.26-r2 apache2? ( >=net-www/apache-2.0.43-r1 !>=net-www/apache-2.0.54-r30 )" --------8<--------8<--------8<--------8<-------- which forbids the use of 4.4.0-r2 with Apache >= 2.0.54-r31 (and ...-r31 is stable)! I found that emerging mod_php 4.4.0-r3 solves the problem. Maybe it's a good idea to go forward and unmask it. (BTW: I think that bug 106490 is no dupe of this bug because it refers to the mod_php version that you recommend to use which also doesn't work.) (In reply to comment #3) > Emerging mod_php 4.4.0-r2 is not the solution to the problem because the ebuild > still features the line > > --------8<--------8<--------8<--------8<-------- > DEPEND_EXTRA=">=net-www/apache-1.3.26-r2 > apache2? ( >=net-www/apache-2.0.43-r1 > !>=net-www/apache-2.0.54-r30 )" > --------8<--------8<--------8<--------8<-------- > > which forbids the use of 4.4.0-r2 with Apache >= 2.0.54-r31 (and ...-r31 is stable)! > > I found that emerging mod_php 4.4.0-r3 solves the problem. Maybe it's a good > idea to go forward and unmask it. I wanted to do that, but I masked all new mod_php and apache ebuilds. I will unmask then when I'm sure that all dependencies work well. All dependencies to work well, simply you need mod_php-4.4.0-r3 to work with the new Apache, that's all. Best regards, CHTEKK. sure, but mod_php-4.4.0-r3 is still unstable (masked by ~x86) and I don't want to unmask any package. Then keep your stuff broken... Either you use the unstable mod_php or it won't work with the new stable Apache, that's how it is. Simply add dev-php/mod_php to /etc/portage/pacakge.keywords, here's the command for you: echo dev-php/mod_php >> /etc/portage/pacakge.keywords That's simple, isn't it? :) And the "unstable" mod_php is the same as the stable mod_php, only the configuration changed to work with the new Apache, so it's _perfectly_ safe to emerge it. Best regards, CHTEKK. (In reply to comment #6) > sure, but mod_php-4.4.0-r3 is still unstable (masked by ~x86) and I don't want > to unmask any package. Alternatively, put >=net-www/apache-2.0.54-r30 into package.mask @Luca Longinotti: I know that, I'm not stupid.
@Jakub Moc: That's what I did for about 3 hours. I will wait until the
dependencies are correct, I added
>=net-www/apache-2.0.54-r30
>=dev-php/mod_php-4.4.0-r2
(In reply to comment #9) > I will wait until the > dependencies are correct, I added > >=net-www/apache-2.0.54-r30 > >=dev-php/mod_php-4.4.0-r2 We won't be marking mod_php-4.4.0-r3 stable; you can wait until dev-lang/php is marked stable and switch then (Oct. 8, if everything goes well). *** Bug 106500 has been marked as a duplicate of this bug. *** Sorry devs, but this is not the way it should be. Stable is stable. And that's what those flags are for. What's the point in not marking mod_php-r3 stable if the only difference is the matching for the new stable (sic!!) apache layout? (Anyone wants to bet how many duplicates this bug will get? ;-) mod_php-4.4.0-r3 stable on x86 now, emerge sync in and hour or so... FIXED and closing. *** Bug 106521 has been marked as a duplicate of this bug. *** |