Re: 1.3.0-rc2 tarballs up for testing/signing

On 10/30/05, Sigfred Håversen <bsdlist@mumak.com> wrote:
> David James wrote:
> > On 10/29/05, Sigfred Håversen <bsdlist@mumak.com> wrote:
> >
> >>David James wrote:
> >>
> >>>On 10/28/05, Sigfred Håversen <bsdlist@mumak.com> wrote:
> >>>[...]
> >>>
> >>>
> >>>>I had to use GNUmake to compile the SWIG bindings, while for earlier
> >>>>versions of Subversion, the BSDmake worked fine. When doing
> >>>>"make swig-py" (part of the port Makefile), the compiling
> >>>>stops with:
> [snip]
> >
> > Subversion 1.2.0rc2 should contain a fix for this issue. Get
> > Subversion 1.2.0rc2 at:
> > http://lolut.utbm.info/pub/subversion-1.3.0/rc2/
>
> Subversion 1.3.0-rc2 now builds the SWIG bindings using BSD make
> on OpenBSD 3.8-current for i386.
>
> The check FSTYPE=bdb and check-swig-pl passes.
>
> The previous reported issue of "svn ls svn://localhost" not connecting
> to svnserve seems to be a problem on the test machine since I've the same
> issue now with Subversion 1.2.3. Before testing I did a clean install
> of OpenBSD on the machine, so I'll look into what has happened here.
>
>
> There are a couple of issues.
>
> 1) The locale files subversion.mo are not installed. In previous versions
> these was installed.
Hmm. Can someone take a look at this?

> 2) check-swig-py don't run properly. Installing them and then running
> the regression test makes no difference:
[snip]
> __swig_setmethods__["data"] = _core.svn_string_t_data_set
> AttributeError: 'module' object has no attribute 'svn_string_t_data_set'

After installing the Python bindings, try the following tests:
1) python -c "import libsvn._core"
2) python -c "import libsvn._core; print libsvn._core.svn_pool_create"
3) python -c "import libsvn._core; print libsvn._core.svn_string_t_data_set"

If (1) and (2) pass, but (3) fails, it is likely that Subversion 1.3.x
has found your Subversion 1.2.x bindings and is being confused by
them. Subversion 1.3.x ships with svn_string_t_data_set, but
Subversion 1.2.x does not.

Any ideas on how to fix this or debug this? Probably, the best idea is
to retry the Subversion 1.3.x install, after removing /usr/lib/libsvn*
and /usr/local/lib/libsvn*

Cheers,

David

--
David James -- http://www.cs.toronto.edu/~james