Bug#232946: subversion: tighter apache dependencies needed
On Mon, 2004-02-16 at 21:51, David Kimdon wrote:
> severity 232946 important
> reassign 232946 libapr0
> merge 231659 232946
>
> Thanks for the report. This apparently is a bug in the apache shlibs
> file. I can override it if it isn't fixed in apache2 in the near
> future but it would be better for apache2 to fix it.
>
> -David
While my second report concerned an issue that may be dealt with best by
apache, I wonder if there aren't some subversion packaging issues too.
subversion shows
Version: 0.37.0-2
Depends: libapr0 (>= 2.0.48), libc6 (>= 2.3.2.ds1-4), libdb4.2,
libexpat1 (>= 1.95.6), libldap2 (>= 2.1.17-1), libneon24 (>= 0.24.4),
libssl0.9.7, libsvn0 (= 0.37.0-2), libxml2 (>= 2.6.5), zlib1g (>=
1:1.2.1), patch, db4.2-util
Apparently the libapr0 version should be 2.048-7. Some of the earlier
versions may not have made it out of unstable; I don't know if the
practice is to ignore versioning issues that only affect unstable.
This alone is not enough to affect the apache2 version, since libapr0
depends only on low-level libs:
Version: 2.0.48-7
Replaces: libapr
Provides: libapr
Depends: libc6 (>= 2.3.2.ds1-4), libdb4.2, libexpat1 (>= 1.95.6),
libldap2 (>= 2.1.17-1), libpcre3, libdb4.2, libexpat1
Conflicts: libapr
However, libapache2-svn depends on an *unversioned* apache2. Perhaps
that needs to be versioned? Right now the settings on libapache2-svn
are
Source: subversion
Version: 0.37.0-2
Replaces: libapache-dav-svn, libapache2-dav-svn
Depends: apache2, libc6 (>= 2.3.2.ds1-4), libsvn0 (= 0.37.0-2),
db4.2-util
Conflicts: libapache-dav-svn, libapache2-dav-svn
>
> On Mon, Feb 16, 2004 at 02:08:06PM -0800, Ross Boylan wrote:
> > I upgraded all the relevant apache files to 2.0.48, I thought, and was
> > able to perform read (view through web, use svn log) but not write to
> > the respository. When I attempted an import, the apache2 log showed
> > /usr/sbin/apache2: relocation error: /usr/lib/libaprutil-0.so.0:
> > undefined symbol: db_create_4001
> >
> > libapr0 was at 2.0.48-4.
> >
> > I found that upgrading it to 2.0.48-7 (current one in unstable) and
> > restarting apache solved the problem.
> >
> > If this indicates that other apache2 packages need to tighten their
> > dependencies to force a better libapr0, feel free to clone or whatever
> > this bug.
> >
> > Current dendencies of apache2-mpm-perchild
> > Version: 2.0.48-7
> > Provides: apache2-modules, apache2, httpd
> > Depends: libapr0 (>= 2.0.48), libc6 (>= 2.3.2.ds1-4), libdb4.2,
> > libexpat1 (>= 1.95.6), libldap2 (>= 2.1.17-1), libssl0.9.7, zlib1g (>=
> > 1:1.2.1), apache2-common (= 2.0.48-7)
> > Conflicts: apache2, apache2-mpm-worker, apache2-mpm-prefork,
> > apache2-mpm-threadpoo
> >
> > I.e., apache 2.0.48-7 does not force upgrade of libapr0 to .48-7
> >
> > Changelog for libapr0 since -7 indicate some trouble with libapr0,
> > though I can't tell exactly what. If apr0 had no linking info, I would
> > think it was totally broken.
....
Reply to: