Bug#272476: apache2: %b size is wrong for partial downloads
On Oct 04, Adam Conrad [EMAIL PROTECTED] wrote: I leave it up to you whether you'd prefer to downgrade this to wishlish on the off chance that some kind soul will provide a Debian-only patch, or just close it, since that seems to be upstream's response. I do not advocate debian-specific changes, especially if they they may confuse people as it appears to be in this case. OTOH, maybe the LogFormat entries in the default apache.conf should use %O instead of %b. If you do not think this is viable then just close the bug. -- ciao, | Marco | [8341 di5qeZBynSq4w]
Need some help to package apache-lingerd
Hello there. I'm pretty interested in trying to package apache-lingerd, which has been requested for more than 500 days now : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=187460 Could someone point me to some piece of docs on how the Debian Apache Maintainers team bild their package ? The fact is that lignerd needs the following steps to be packaged : First step : building lingerd : - tuning of config.h file - user creation : 'lingerd' - directory creation for hosting pidfile and unix domain socket (/var/run/lingerd). - compilation of lingerd binary and installation of it. Second step : patching Apache. - add some files to the apache src source tree - patch some apache native files - compile apache Third step : - update the init.d startup script for apache : lingerd must be launched before apache to work properly. I'm sure that the team has a lot of guidelines to build such a package but I cannont find any docs about this. Help will be welcome :) -- Alexis Sukrieh [EMAIL PROTECTED] * Another Linux Debian Geek Enthusiast * http://www.sukria.net
Bug#274891: apache2-mpm-worker: mod_autoindex listings show incorrect last-modified date
Package: apache2-mpm-worker Version: 2.0.52-1 Severity: normal mod_autoindex in Apache2 shows incorrect datestamps for last-modified when displaying directory names as part of a directory index. Files appear to display with the correct last-modified, but many directories on my system all just show up with 11-Aug-2004 23:40, including new ones created today (4-October-2004). -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.7 Locale: LANG=C, LC_CTYPE=C Versions of packages apache2-mpm-worker depends on: ii apache2-common 2.0.52-1 Next generation, scalable, extenda ii libapr0 2.0.52-1 The Apache Portable Runtime ii libc6 2.3.2.ds1-16 GNU C Library: Shared libraries an ii libdb4.24.2.52-17Berkeley v4.2 Database Libraries [ ii libexpat1 1.95.6-8 XML parsing C library - runtime li ii libldap22.1.30-3 OpenLDAP libraries ii libssl0.9.7 0.9.7d-5 SSL shared libraries ii zlib1g 1:1.2.1.1-7 compression library - runtime -- no debconf information
Re: Need some help to package apache-lingerd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexis Sukrieh wrote: | Hello there. | | I'm pretty interested in trying to package apache-lingerd, which has | been requested for more than 500 days now : | http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=187460 | | Could someone point me to some piece of docs on how the Debian Apache | Maintainers team bild their package ? eheh the truth is that our documentation is our debian/rules file. | | The fact is that lignerd needs the following steps to be packaged : | | First step : building lingerd : | | - tuning of config.h file | - user creation : 'lingerd' | - directory creation for hosting pidfile and unix domain socket | (/var/run/lingerd). | - compilation of lingerd binary and installation of it. This can be done easily afaict. | | Second step : patching Apache. | | - add some files to the apache src source tree | - patch some apache native files | - compile apache Amen.. this is a pain. I really suggest you to look at how we build apache. Take as example the fact that from the same source we create binaries for apache, apache-perl and apache-ssl, but if you really really need to create a patched apache i sugget to prepare everything carefully and coordinate with us. It is easier to build a new apache flavour from the same sources than having to upload a new one. The security team would have serious problems to handle (again) more than one apache source. | | Third step : | | - update the init.d startup script for apache : lingerd must be launched | before apache to work properly. if you start from the apache package check debian/pkgtemplates and the script that creates the final scripts. | | I'm sure that the team has a lot of guidelines to build such a package | but I cannont find any docs about this. as above.. read the source luke ;) | | Help will be welcome :) | | Fabio - -- user fajita: step one fajita Whatever the problem, step one is always to look in the error log. user fajita: step two fajita When in danger or in doubt, step two is to scream and shout. -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBYYiRhCzbekR3nhgRAn9kAKCV8jPp0iU20wmuEvipphiOQeZIjQCdGDOT qJXBQPpDRJnmyzN8+9REP/A= =ktLr -END PGP SIGNATURE-
Re: Need some help to package apache-lingerd
* Fabio Massimo Di Nitto ([EMAIL PROTECTED]) disait : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexis Sukrieh wrote: | Hello there. | | I'm pretty interested in trying to package apache-lingerd, which has | been requested for more than 500 days now : | http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=187460 | | Could someone point me to some piece of docs on how the Debian Apache | Maintainers team bild their package ? eheh the truth is that our documentation is our debian/rules file. lol :) Ok. So I'll enable my debian-patched brain to extract doc from the debian/ stuff ;) | The fact is that lignerd needs the following steps to be packaged : | | First step : building lingerd : | | - tuning of config.h file | - user creation : 'lingerd' | - directory creation for hosting pidfile and unix domain socket | (/var/run/lingerd). | - compilation of lingerd binary and installation of it. This can be done easily afaict. Yep, that is definitely not the most difficult part, I agree. | Second step : patching Apache. | | - add some files to the apache src source tree | - patch some apache native files | - compile apache Amen.. this is a pain. I really suggest you to look at how we build apache. Take as example the fact that from the same source we create binaries for apache, apache-perl and apache-ssl, Yes, I think so, the best way is to start from the main debian-apache source. I will first look deeply inside in order to see what to do for a 'apche-lingerd'. | | Third step : | | - update the init.d startup script for apache : lingerd must be launched | before apache to work properly. if you start from the apache package check debian/pkgtemplates and the script that creates the final scripts. Ok, I'll take a look at that script. | I'm sure that the team has a lot of guidelines to build such a package | but I cannont find any docs about this. as above.. read the source luke ;) Hehe, I'll do it, and maybe the force bla bla ... :) -- Alexis Sukrieh [EMAIL PROTECTED] * Another Linux Debian Geek Enthusiast * http://www.sukria.net
