Re: Bug#666816: mod-proxy-html: sourceful transition towards Apache 2.4
On 04/05/2012 20:45, Stefan Fritsch wrote: On Thursday 19 April 2012, Emmanuel Lacour wrote: On Tue, Apr 03, 2012 at 04:13:45PM +0200, Arno Töll wrote: there is probably no reason to ship your module once apache2 2.4 is in Testing and thus it should be removed as an individual package. I'd suggest you to make it a transitional package towards apache2-bin in Wheezy and drop it entirely for Wheezy+1. What is the recommended way? Convert this package to a dummy one, which version should I use (lintian complain about that this is a native debian package as sources are now empty)? Or maybe better, add libapache2-mod-proxy-html as a dummy transitional package in apache2 control file? I think adding the transitional package to the apache2 source package would be best. If you agree, I will do that with the next upload. I agree. Thaks. -- Emmanuel LACOUR - elac...@home-dn.net -- To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4fa42a10.1080...@home-dn.net
Bug#308648: apache2-mpm-prefork: Childs segfaults
On Thu, May 12, 2005 at 01:08:31PM +0200, Emmanuel Lacour wrote: On Thu, May 12, 2005 at 03:42:44PM +1000, Adam Conrad wrote: So now I just installed your packages (2.0.54-4) with the original MaxRequestsPerChild of 0, waiting... No more segfaults, all seems to be ok! Thx, you can upload to close this bug :) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308648: apache2-mpm-prefork: Childs segfaults
Package: apache2-mpm-prefork Version: 2.0.54-3 Severity: important I'm using it with auth_ldap, ssl and php4 under sarge. After my last upgrade, I saw some segfaults. I looked in the BTS and found some segfault with auth_ldap fixed in sid version (2.0.54-3), so I did an aptitude install apache2-mpm-prefork/unstable and I always have segfaults: [Tue May 10 21:17:21 2005] [notice] Apache configured -- resuming normal operations [Tue May 10 22:21:29 2005] [notice] child pid 20946 exit signal Segmentation fault (11) [Tue May 10 22:22:47 2005] [notice] child pid 24299 exit signal Segmentation fault (11) [Wed May 11 00:05:02 2005] [notice] child pid 5187 exit signal Segmentation fault (11) free(): invalid pointer 0x83bafe8! free(): invalid pointer 0x83bafe8! free(): invalid pointer 0x83bafe8! free(): invalid pointer 0x83bafe8! free(): invalid pointer 0x83bafe8! I don't no how to gdb apache and don't now how to reproduce this, it happens, that's all... -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages apache2-mpm-prefork depends on: ii apache2-common2.0.54-3 next generation, scalable, extenda ii libapr0 2.0.54-2 the Apache Portable Runtime ii libc6 2.3.2.ds1-21 GNU C Library: Shared libraries an ii libdb4.2 4.2.52-18 Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.8-3 XML parsing C library - runtime li ii libldap2 2.1.30-6 OpenLDAP libraries ii libpcre3 4.5-1.1+woody0 Perl 5 Compatible Regular Expressi ii libssl0.9.7 0.9.7e-3 SSL shared libraries ii zlib1g1:1.2.2-4 compression library - runtime -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Informations for packaging apache(2) third party modules
On Wed, Sep 15, 2004 at 07:25:11PM +0100, Thom May wrote: u-a-m is a work in process, which will be the standard way of handling modules. It's pretty close, but not there yet. I'm hoping to have some time the next couple of days to work on it and test it etc. I'd really ask you *not* to go off developing your own solution to the problem though. Of course, so I compared a lot of other apache modules and mix what I think the best wayi, because they all use a different approach (auto enabling, doing nothink, asking, ...) I'm not a DD, just a new maintainer so I can't help directly to put officials docs online, but I ask someone who want to work with me on an official apache module packaging webpage. Once a standard skeleton for postinst/prerm scripts, we can talk to each already packaged modules maintainers for adopting this universal way. :) -- Emmanuel LACOUR - [EMAIL PROTECTED]
Re: Informations for packaging apache(2) third party modules
On Wed, Sep 15, 2004 at 02:52:28AM +0100, Thom May wrote: libapache2-mod-macro is pretty much the simplest possible case for an apache2 module. get the source for that, and run with it. I'm not looking for the easiest package example, I already looked at many, but I wan't to find the best way for postinst/prerm scripts. I think it's a good idea to provide a choice for the user to enable/disable the module via debconf at install time and via dpkg-reconfigure. If there isn't a standard way like with apache1.x, I will do my debconf template myself (enable/disable modue? yes/no, then use a2enmod or a2dismod). There is also a script called update-apache2-modules. Should I use this one instead of a2*mod. Is there a standard way for looking if a module is enabled (other than -e /etc/apache2/mods-enabled/load). All I wanted to say in my email is that we should have a standard way for handling modules with apache2 and we have to document it ... and I'm ok to help doing this of course:) -- Emmanuel LACOUR - [EMAIL PROTECTED]
Informations for packaging apache(2) third party modules
Hi everybody, I'm working on packaging a new apache module for apache/apache2 (www.suphp.org), and I try to find the best way for my postinsts/prerms scripts. I found the README.modules in apache-dev, but nothing for apache2-dev. So I looked at some other packages and saw that often they simply a2enmod without asking the user... AW, is there a place where I can find informations on packaging tools with dependendies on apache like apache modules. If there isn't such a place I would suggest to set up a simple page or wiki (I can do this) and add a link to Packaging section on Developers' Corner at www.debian.org. Regards, -- Emmanuel LACOUR - [EMAIL PROTECTED]
