Bug#397422: apache2-mpm-itk: Missing build-dependency on libapr1-dev & others
Package: apache2-mpm-itk Version: 2.2.3-01-1+b1 Severity: wishlist -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 While compiling apache2-mpm-itk on sarge, I got a build failure about a missing symbol in libapr. I guess this because I have the older version of libapr from sarge installed. I think that all of apache2's build-dependencies should be added to apache2-mpm-itk's build-dependencies. They are: debhelper (>= 4.1.16), dpatch, lsb-release, libaprutil1-dev, libapr1-dev (>= 1.2.7-6), openssl, libpcre3-dev, libtool - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (530, 'testing'), (520, 'unstable'), (510, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-k7 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFUFwkshl/216gEHgRAq/4AKDqoCVjVhtr+BQFZg2dlUxy9B0gvwCfeM6o It+dZuUlmvTzu9M65o3lvKc= =MsmJ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397422: apache2-mpm-itk: Missing build-dependency on libapr1-dev & others
On Tue, Nov 07, 2006 at 10:12:52AM +, Sam Morris wrote: > While compiling apache2-mpm-itk on sarge How is this even possible? You'd have to at least backport Apache 2.2, then? (Either that, or hack an apache2-src-like tree into place and fetch the Apache 2.0 patches.) Either way, I'm not sure if this is a scenario I'm very likely to be supporting out-of-the-box anytime soon :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#397422: apache2-mpm-itk: Missing build-dependency on libapr1-dev & others
On Tue, 2006-11-07 at 12:13 +0100, Steinar H. Gunderson wrote: > On Tue, Nov 07, 2006 at 10:12:52AM +, Sam Morris wrote: > > While compiling apache2-mpm-itk on sarge > > How is this even possible? You'd have to at least backport Apache 2.2, then? > (Either that, or hack an apache2-src-like tree into place and fetch the > Apache 2.0 patches.) Either way, I'm not sure if this is a scenario I'm very > likely to be supporting out-of-the-box anytime soon :-) Originally I installed apache2-src from unstable and tried to build directly; that's how I ran into this bug. I decided instead to backport apache2, apr and apr-util. It only takes a few minutes since the build-dependencies are all available in either sarge or on http://backports.org/. I think the best way to solve this would be to get the apache2-src package to include a minimal debian/control file including apache2's build-dependencies. Then apache2-mpm-itk could simply call dpkg-checkbuilddeps during the package build process. OTOH, the ITK MPM is not very well known or highly demanded, and Etch will be out soon making this bug obsolete, so feel free to tag as wontfix--I'm sure anyone else brave enough to try to backport it to sarge will also be clever enough to search the BTS if they run into problems. :) -- Sam Morris http://robots.org.uk/ PGP key id 1024D/5EA01078 3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078 signature.asc Description: This is a digitally signed message part
Bug#397422: apache2-mpm-itk: Missing build-dependency on libapr1-dev & others
On Tue, Nov 07, 2006 at 11:41:03AM +, Sam Morris wrote: > OTOH, the ITK MPM is not very well known or highly demanded, and Etch > will be out soon making this bug obsolete, so feel free to tag as > wontfix--I'm sure anyone else brave enough to try to backport it to > sarge will also be clever enough to search the BTS if they run into > problems. :) Well. I'm quite sure that if the demand is high enough, I'll put up a sarge backport on backports.org. My first priority is getting mpm-itk actually into etch, though, so I'm not fixing any non-RC bugs against the package for a while now anyhow :-) /* Steinar */ -- Homepage: http://www.sesse.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
