I'm running Subversion 1.2.1 (which currently needs apache-2.0.54-r12) but I also want to run mod_php 4.4.0. Which is blocked if you run > apache-2.0.54-r10. (I need mod_php 4.4.0 because mediawiki 1.4 is incompatible with php5 and mediawiki 1.5 which does support php5 is not stable yet). Anyway, a subversion ebuild which works with apache-2.0.54-r8 would solve this dependency mess :-) Reproducible: Always Steps to Reproduce: 1. 2. 3.
(In reply to comment #0) > I'm running Subversion 1.2.1 (which currently needs apache-2.0.54-r12) but I > also want to run mod_php 4.4.0. Which is blocked if you run > apache-2.0.54-r10. mod_php-4.4.0-r1 is for that version of Apache, put it into /etc/portage/package.keywords.
(In reply to comment #1) Ah, had not seen the 4.4.0_r1 yet! Thanks
Created attachment 64517 [details] ebuild for subversion-1.2.1 works with apache-2.0.54-r8 Sorry for chiming in, but I also have a need for subversion 1.2.x which runs on that stable apache2 (I run some production servers, and need to provide that service.) And I've created an ebuild for 1.2.1. Would you mind if you re-open the bug and take a look of them?
I think an ebuild for subversion 1.2.1 for a STABLE apache is a good idea
(In reply to comment #4) > I think an ebuild for subversion 1.2.1 for a STABLE apache is a good idea Uhm, subversion-1.1.3 works with stable apache. Moreover, the plan is to get rid of dual apache layouts as soon as possible.
(In reply to comment #5) My current repository (running svn 1.2.1) is filled with active projects and I prefer (don't know if it's even possible) to downgrade it to 1.1.3. > (In reply to comment #4) > > I think an ebuild for subversion 1.2.1 for a STABLE apache is a good idea > > Uhm, subversion-1.1.3 works with stable apache. Moreover, the plan is to get rid > of dual apache layouts as soon as possible.
(In reply to comment #5) > Uhm, subversion-1.1.3 works with stable apache. Moreover, the plan is to get rid > of dual apache layouts as soon as possible. Yes, I know you're working really, REALLY hard to improve the whole distro for free. But the lack of file locking of 1.1.3 is preventing our devs from doing any serious work on binary files (here at Monolith Works Co.) Thanks in advance.
There should be a new release (1.2.3) out soon. For that one I'll create two versions, one with the new apache support, and one without.
Please try the (masked) 1.2.3 version I just committed, and report on whether it works. I don't have an environment with a stable apache at hand, so I didn't test it.
After doing a sync yesterday (which was very big...) the now stable svn 1.2.3 is blocking apache >=2.0.54-r30 But Portage wants to upgrade apache as it is stable now... Marking subversion-1.2.3-r1 stable would solve this.
(In reply to comment #10) > Marking subversion-1.2.3-r1 stable would solve this. It's fixed! Thanks.
Yeah, I knew apache would get stable yesterday, but I had guests yesterday to celebrate the middle autumn festival. But as you said svn is stable on x86 now.
(In reply to comment #9) > Please try the (masked) 1.2.3 version I just committed, and report on whether it > works. I don't have an environment with a stable apache at hand, so I didn't > test it. (Ugh. I'm sorry for not watching here for a while.) Thanks, it works with apache-2.0.54-r8. Anyways things changed quite a lot... now the new apache layout is stable. Keep up good work!
