Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 20136 - subversion-0.21.0.ebuild doesnt check apxs version
Summary: subversion-0.21.0.ebuild doesnt check apxs version
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-28 18:51 UTC by Markus Luisser
Modified: 2003-04-29 09:35 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Luisser 2003-04-28 18:51:52 UTC
ebuild failed because apxs version was 9.2 instead of at least 9.3 which comes with 
the latest apache ebuild (2.0.45) 

Reproducible: Didn't try
Steps to Reproduce:
1. ACCEPT_KEYWORDS="~x86" emerge subversion .... fails - wrong apxs version 
2. ACCEPT_KEYWORDS="~x86" emerge apache - installs apache 2.0.45 
3. ACCEPT_KEYWORDS="~x86" emerge subversion .... works 


Expected Results:  
ebuild should ckeck proper apache2 (apxs) version 

my box is partly '~x86' - if i recall it correctly i had apache 2.0.43-r1 installed when the 
ebuild threw the error - this might be the reason - however, swig and neon where 
installed/upgraded with the correct versions as expected but apache was not... 
 
great job with the ebuild - i was waiting for it - works like a charm - i tried to tweak the 
script - on another box - to use the new db version 4.1.24 - worked without 
problems...
Comment 1 Paul de Vrieze (RETIRED) gentoo-dev 2003-04-29 07:14:37 UTC
Sorry, I updated the ebuilds to depend on apache-2.0.45. Apache-2.0.44 is unsafe so shouldn't be used anyway. I do wonder though why merging worked with apache-2.0.43, that shouldn't happen. If you are sure that you where running apache-2.0.43 then please comment and I will reopen it.
Comment 2 Markus Luisser 2003-04-29 09:35:52 UTC
nah - leave it resolved - i am not 100% sure and as apache catches up it would vanish anyway... just wanted to provide some very limited help by reporting my experience...