Bug#263804: increase severity of libapr0-dev: [PATCH] : link coherently with Berkeley DB
On Mon, Aug 09, 2004 at 12:02:11PM +0200, Andreas Metzler wrote: On 2004-08-09 David Kimdon [EMAIL PROTECTED] wrote: severity 263804 serious thanks As indicated earlier in the report aprutil links with DB 4.0 which the rest of the package links with 4.2. That leaves apache linking with two separate versions. In the past a similar multi-version link between subversion and apache of berkeley DB caused segmentation faults in apache. [...] This should not happen, have you got references for this? All versions of BerkeleyDB in Debian use versioned symbols which should make linking against two versions at runtime safe. hmm, well I cannot find a reference. It is possible that the problem I am remembering did not occur on a Debian system. Perhaps I should just fix the subversion build to not get upset with the incoherent linking. . . -David
Bug#263804: libapr0-dev: [PATCH] : link coherently with Berkeley DB
Hi, The build finished on the sparc machine. The packages are at http://people.debian.org/~dwhedon/apache2/ if you want to take a look. I ran ldd on everything and there is only one Berkeley DB linked (libdb-4.2). That convinces me that the patch given earlier in the report is proper. I think this bug may deserve a higher severity since having two Berkeley DB's in the same executable may lead to brokenness. -David
estimate on new apache2 package release?
Back in December thom and I had a conversation that it would be good to coordinate the db4.2 upgrades for subversion and apache2 (libapr actually) Debian packages. The plan was (and still is) to bundle a subversion repository schema update into a berkeley db upgrade so subversion repositories only need to go down once. As a bonus with berkeley db4.2 we will be linking subversion against the berkeley db version recommended upstream and thom had some reasons that I don't recall for wanting to link apache2 to bdb 4.2. I would like to get the new subversion package uploaded sooner rather than later. If you can give me any sort of estimate as to when the apache2/libapr packages that link with bdb 4.2 will be uploaded that would be helpful to me. If I receive no more information on a potential upload date I may end up building new subversion debs and linking them with bdb 4.1, which I really would rather not do. Thanks for all the good work, David
