> From: Martin Pool [mailto:mbp@sourcefrog.net]
> Sent: 09 July 2002 11:53
> On 8 Jul 2002, Ben Collins-Sussman <sussman@collab.net> wrote:
>
> > Martin, all of these bugs should now be fixed as of r2435.
>
> Sorry, I think they're not.
>
> > And thanks for finding them!
>
> My pleasure. The sooner Subversion is ready to go, the better.
>
> I will try to write a Python test case around this later on. The
> testing framework is really clever.
>
> > A bugfix (from me and cmpilato) for what I now dub the "the *reverse*
> > ghudson bug". Versioning trees is Hard.
>
> I suppose it's a bit late to mention this, but: have you considered
> making commits always tree-wide? It seems to me like that would avoid
> some of the "ghudson" problems, and would not significantly reduce
> usefulness. If this area has been such a cause of problems in the
> past it will continue in the future; if you perform a featurectomy
> before 1.0 perhaps noone will miss it. (Just my 2c, etc.)
>
> Using Subversion r2441 (./autogen.sh; ./config.status --recheck; make
> clean; make all; make install) tonight:
[...]
> By the way, is that sequence (svnadmin create; svn mkdir; svn co) the
> typical way to start a new repository?
Yes. You could however leave out the mkdir step and do that in your
working copy. I personally use a shell script that does something like:
svnadmin create ${REPOS}
svn co file:///${REPOS} -d ${REPOS}-wc
cd ${REPOS}-wc
mkdir trunk tags branches
svn add trunk tags branches
svn commit -m "Add standard hierarchy."
cd ..
rm -rf ${REPOS}-wc
> jerenkrantz(?) expressed concern that my svn binary was dynamically
> linked against Berkeley db1. It seems very unlikely to me that such a
> library problem would have this kind of symptom, as opposed to say
> just failing to compile altogether. Looking at the configure output,
> I am pretty sure that Subversion itself links against the db4
> distribution in a source subdirectory, but APR links against the
> system's -ldb and -lgdbm for reasons best know to itself.
Justin voiced this concern because it wouldn't be the first time that
httpd/apr/apr-util were linked against a different db than libsvn_fs.
This has caused quite some grief in the past where people couldn't
get their servers to work. For the sake of prevention, please try
to get all components to consistently link to the same db. If they
are not on your system (are you passing --with-berkeley-db=<path> to
configure?), could you track down why not?
Thanks,
Sander
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jul 9 12:43:05 2002