current repository, or with an almost clean one?
( this should be easier to test, and if it confirms a problem, you can use it
to move back and forth between 1.4 and 1.5...i suspect they wont be
compatible...
Someone on the subversion-ports find a solution. I'm not sure it's really
the reason
Hi all
I don't known if the problem is with subversion or the ports or between
subversion and FreeBSD. So I just post this message on subversion-list.
Regards.
JAS
--
Albert SHIH
SIO batiment 15
Observatoire de Paris Meudon
5 Place Jules Janssen
92195 Meudon Cedex
Heure local/Local time:
Ven 4
On Fri, 4 Jul 2008 18:35:07 +0200
Albert Shih [EMAIL PROTECTED] wrote:
Hi all
I don't known if the problem is with subversion or the ports or between
subversion and FreeBSD. So I just post this message on subversion-list.
Hi Albert,
what exactly is your setup, on both client and server ?
On Tue, Jun 03, 2008 at 11:25:06AM -0400, Coleman Kane wrote:
Hello,
Since www/neon28 was moved into ports, subversion still depends upon
www/neon26 (which conflicts w/ 2.8). I have been able to tell subversion
to use neon 2.8 by modifying the subversion Makefile appropriately. Is
there any
(Seen on [EMAIL PROTECTED])
On Tue, Jun 03, 2008 at 11:25:06AM -0400, Coleman Kane wrote:
Since www/neon28 was moved into ports, subversion still depends upon
www/neon26 (which conflicts w/ 2.8). I have been able to tell subversion
to use neon 2.8 by modifying the subversion Makefile
On Wed, Jun 04, 2008 at 11:02:34AM +0200, Stefan Sperling wrote:
Since www/neon28 was moved into ports, subversion still depends upon
www/neon26 (which conflicts w/ 2.8). I have been able to tell subversion
to use neon 2.8 by modifying the subversion Makefile appropriately. Is
there any
Hello,
Since www/neon28 was moved into ports, subversion still depends upon
www/neon26 (which conflicts w/ 2.8). I have been able to tell subversion
to use neon 2.8 by modifying the subversion Makefile appropriately. Is
there any specific reason to not move subversion to default to use
www/neon28
