Bug #11413 “apache: FTBFS - x86/testing (31mrule: command not fo...” : Bugs : apache package : Debian

Revision history for this message

In Debian Bug tracker #286975, Jon Dowland (jon-dowland) wrote on 2004-12-23: additional information

#1

Building with debuild as appose to dpkg-buildpackage seems to work.
Attached is the output of a successful debuild run.

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-12-23:

#2

Automatically imported from Debian bug report #286975 http://bugs.debian.org/286975

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-12-23:

#3

Download full text (20.4 KiB)

Message-Id: <email address hidden>
Date: Thu, 23 Dec 2004 11:33:19 +0000
From: Jon Dowland <email address hidden>
To: Debian Bug Tracking System <email address hidden>
Subject: apache: FTBFS - x86/testing (31mrule: command not found)

--===============1051110579==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: apache
Version: 1.3.33-2
Severity: serious
Justification: no longer builds from source

Hi, I'm sorry to be filing this as I'm finding it hard to believe that
this could be a problem for anyone but me. However a fresh apt-get
source of apache, with the build-depends installed and no customisation
at all fails. Nobody in #debian had experienced this when I asked and
there's no match for 'apache FTBFS' on -devel or -user archives for the
last couple of months.

SUMMARY

$ apt-get source apache
# apt-get build-dep apache
$ cd apache-1.3.33
apache-1.3.33$ dpkg-buildpackage -rfakeroot -b
....
./configure: line 1: 31mrule: command not found
+ using installation path layout: Debian (config.layout)
configure:Error: No such rule named 'SHARED_CHAIN'
make: *** [debian/stampdir/configure-stamp-apache] Error 1

DETAILED

Full output of dpkg-buildpackage is attached. I note that the first line
of every file named 'configure' in the source dir is a standard
hash-bang.

-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages apache depends on:
ii apache-common 1.3.33-2 Support files for all Apache webse
ii debconf 1.4.30.10 Debian configuration management sy
ii dpkg 1.10.25 Package maintenance system for Deb
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libdb4.2 4.2.52-17 Berkeley v4.2 Database Libraries [
ii libexpat1 1.95.8-1 XML parsing C library - runtime li
ii libmagic1 4.12-1 File type determination library us
ii logrotate 3.7-2 Log rotation utility
ii mime-support 3.28-1 MIME files 'mime.types' & 'mailcap
ii perl 5.8.4-3 Larry Wall's Practical Extraction

-- debconf information:
  apache/server-name: localhost
  apache/document-root: /var/www
  apache/server-port: 80
* apache/enable-suexec: false
  apache/init: true
  apache/server-admin: webmaster@localhost

--===============1051110579==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="output"

dpkg-buildpackage: source package is apache
dpkg-buildpackage: source version is 1.3.33-2
dpkg-buildpackage: source maintainer is Fabio M. Di Nitto <email address hidden>
dpkg-buildpackage: host architecture is i386
fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f debian/apache{,-ssl,-perl}.{presubj,init,conffiles,config,dirs,docs,examples,lintian,intro.html}
rm -f debian/apache{,...

Message-Id: <200412231133.LAA29039@burnmoor.ncl.ac.uk>
Date: Thu, 23 Dec 2004 11:33:19 +0000
From: Jon Dowland <bugs@alcopop.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: apache: FTBFS - x86/testing (31mrule: command not found)

--===============1051110579==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Package: apache
Version: 1.3.33-2
Severity: serious
Justification: no longer builds from source

Hi, I'm sorry to be filing this as I'm finding it hard to believe that
this could be a problem for anyone but me. However a fresh apt-get
source of apache, with the build-depends installed and no customisation
at all fails. Nobody in #debian had experienced this when I asked and
there's no match for 'apache FTBFS' on -devel or -user archives for the
last couple of months.

SUMMARY

$ apt-get source apache
# apt-get build-dep apache
$ cd apache-1.3.33
apache-1.3.33$ dpkg-buildpackage -rfakeroot -b
....
./configure: line 1: 31mrule: command not found
 + using installation path layout: Debian (config.layout)
 configure:Error: No such rule named 'SHARED_CHAIN'
 make: *** [debian/stampdir/configure-stamp-apache] Error 1

DETAILED

Full output of dpkg-buildpackage is attached. I note that the first line
of every file named 'configure' in the source dir is a standard
hash-bang.

-- System Information:
Debian Release: 3.1
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-1-686
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1)

Versions of packages apache depends on:
ii  apache-common               1.3.33-2     Support files for all Apache webse
ii  debconf                     1.4.30.10    Debian configuration management sy
ii  dpkg                        1.10.25      Package maintenance system for Deb
ii  libc6                       2.3.2.ds1-18 GNU C Library: Shared libraries an
ii  libdb4.2                    4.2.52-17    Berkeley v4.2 Database Libraries [
ii  libexpat1                   1.95.8-1     XML parsing C library - runtime li
ii  libmagic1                   4.12-1       File type determination library us
ii  logrotate                   3.7-2        Log rotation utility
ii  mime-support                3.28-1       MIME files 'mime.types' & 'mailcap
ii  perl                        5.8.4-3      Larry Wall's Practical Extraction

-- debconf information:
  apache/server-name: localhost
  apache/document-root: /var/www
  apache/server-port: 80
* apache/enable-suexec: false
  apache/init: true
  apache/server-admin: webmaster@localhost

--===============1051110579==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="output"

dpkg-buildpackage: source package is apache
dpkg-buildpackage: source version is 1.3.33-2
dpkg-buildpackage: source maintainer is Fabio M. Di Nitto <fabbione@fabbione.net>
dpkg-buildpackage: host architecture is i386
 fakeroot debian/rules clean
dh_testdir
dh_testroot
rm -f debian/apache{,-ssl,-perl}.{presubj,init,conffiles,config,dirs,docs,examples,lintian,intro.html}
rm -f debian/apache{,-ssl,-perl}.{logrotate,postinst,postrm,preinst,prerm,httpd.conf}
rm -f debian/apaci{,-ssl,-perl,.append{,-ssl,-perl}}
rm -f debian/{apache-common.examples,apache-dev.docs,libapache-mod-perl.docs}
rm -f debian/{*.gz,local-apxs*,apxs*} o debian/o debian/buildinfo.Debian
rm -rf debian/logos debian/logos.ssl
chmod +x debian/{ubersed,modules-config,sys-build.mk,scripts/*.*,scripts/modchk}
/usr/bin/make -f debian/sys-build.mk source.clean
make[1]: Entering directory `/home/jon/code/apache-1.3.33'
make[1]: Leaving directory `/home/jon/code/apache-1.3.33'
rm -rf build-tree-*
rm -rf debian.diff debian/stampdir
rm -rf libapache-mod-perl-1.29
dh_clean
 debian/rules build

*** unpacking/patching common tree ***

/usr/bin/make -f debian/sys-build.mk source.make
make[1]: Entering directory `/home/jon/code/apache-1.3.33'
Extracting upstream tarball upstream/tarballs/apache_1.3.33.tar.gz successful.
Extracting upstream tarball upstream/tarballs/apache-contrib-1.0.8a-nomodcvs.tar.gz successful.
Extracting upstream tarball upstream/tarballs/pkg.eapi-2.8.22-1.3.33.tar.gz successful.
Applying patch 001_ab_overzealous_connections successful.
Applying patch 002_apxs_assumes_dso successful.
Applying patch 003_apxs_wrong_prefix successful.
Applying patch 005_mime_type_fix successful.
Applying patch 006_phf_dot_log successful.
Applying patch 007_regex_must_conform_to_posix_for_LFS_to_work successful.
Applying patch 008_suexec_combined successful.
Applying patch 009_suexec_of_death successful.
Applying patch 010_dbm_part_2_the_revenge successful.
Applying patch 011_find_dbm_libdb41_fix successful.
Applying patch 012_hurd_compile_fix_for_upstream successful.
Applying patch 013_hurd_libdb_fix successful.
Applying patch 014_mod_auth_db_libdb41_fix successful.
Applying patch 015_suexec_uid_min successful.
Applying patch 017_uncrack_proxy_ftp_eapi_bit successful.
Applying patch 018_suexec_reopenlog successful.
Applying patch 019_apxs_dont_extra_libs successful.
Applying patch 030_autoindex_studly successful.
Applying patch 031_autoindex_indexes successful.
Applying patch 032_autoindex_generator successful.
Applying patch 033_-F_NO_SETSID successful.
Applying patch 034_ab.8_formatting_error successful.
Applying patch 100_proxy_content_base successful.
Applying patch 101_httpd_manpage successful.
Applying patch 102_inetdfix successful.
Applying patch 500_configure_hashbang successful.
Applying patch 501_debian_config_layout successful.
Applying patch 503_debian_requires_fPIC successful.
Applying patch 504_mod_bandwidth_paths successful.
Applying patch 505_limit_my_servers_hard successful.
Applying patch 506_thetarget_unquoted successful.
Applying patch 507_usr_bin_perl_owns_you successful.
Applying patch 509_lpthread successful.
Applying patch 510_dpkg_exclude successful.
Applying patch 511_log_files_permission successful.
Applying patch 512_htpasswd_do_not_trash_extra_fields successful.
Applying patch 513_GNU_xargs successful.
Applying patch 514_nice_proxy_cache_cleanup successful.
Applying patch 515_dbm_read_hash_or_btree successful.
Applying patch 901_security_htdigest_tempfiles successful.
Applying patch 902_security_htpasswd_tempfiles successful.
Applying patch 903_security_htdigest_local_buffer_overflow successful.
Applying patch 904_security_htpasswd_user_buffer_overflow successful.
make[1]: Leaving directory `/home/jon/code/apache-1.3.33'
cp -a build-tree/apache_1.3.33/src/os/unix/{*.h,*inline.c} \
	build-tree/apache_1.3.33/src/include/
cp build-tree/pkg.eapi/*.h build-tree/apache_1.3.33/src/include/
cp build-tree/pkg.eapi/*.c build-tree/apache_1.3.33/src/ap/
cp build-tree/apache-contrib-1.0.8a/mod_macro/mod_macro.c build-tree/apache_1.3.33/src/modules/extra
mv build-tree build-tree-apache

*** creating -ssl and -perl trees ***

mv build-tree-apache/apache-contrib-* .
cp -rp build-tree-apache build-tree-apache-ssl
cp -rp build-tree-apache build-tree-apache-perl
mv apache-contrib-* build-tree-apache/

*** unpackaing mod_perl ***

tar zxvf upstream/flavours/mod_perl-1.29.tar.gz > /dev/null
mv mod_perl-1.29 libapache-mod-perl-1.29

*** applying extra patches to specific trees ***

#-apache
patch -d build-tree-apache/apache_1.3.33 -p0 < build-tree-apache/pkg.eapi/eapi.patch
patching file src/Configuration.tmpl
patching file src/Configure
Hunk #1 succeeded at 1868 (offset 13 lines).
patching file src/ap/Makefile.tmpl
patching file src/ap/ap.mak
patching file src/include/ap_mmn.h
patching file src/include/ap_alloc.h
patching file src/include/buff.h
patching file src/include/http_config.h
patching file src/include/http_conf_globals.h
patching file src/include/httpd.h
patching file src/main/alloc.c
patching file src/main/buff.c
patching file src/main/http_config.c
Hunk #4 succeeded at 1504 (offset 30 lines).
Hunk #5 succeeded at 1619 (offset 30 lines).
patching file src/main/http_main.c
Hunk #7 succeeded at 3667 (offset 1 line).
Hunk #8 succeeded at 4195 (offset 1 line).
Hunk #9 succeeded at 4378 (offset 1 line).
Hunk #10 succeeded at 4895 (offset 1 line).
Hunk #11 succeeded at 4926 (offset 1 line).
Hunk #12 succeeded at 4939 (offset 1 line).
Hunk #13 succeeded at 5725 (offset 11 lines).
Hunk #14 succeeded at 5897 (offset 11 lines).
Hunk #15 succeeded at 6277 (offset 11 lines).
Hunk #16 succeeded at 6290 (offset 11 lines).
Hunk #17 succeeded at 7868 (offset 11 lines).
Hunk #18 succeeded at 7912 (offset 11 lines).
patching file src/main/http_request.c
Hunk #1 succeeded at 1372 (offset 9 lines).
patching file src/main/http_protocol.c
Hunk #1 succeeded at 1172 (offset 12 lines).
Hunk #2 succeeded at 1332 (offset 12 lines).
patching file src/modules/standard/mod_so.c
Hunk #1 succeeded at 266 (offset 40 lines).
patching file src/modules/standard/mod_log_config.c
patching file src/modules/standard/mod_rewrite.c
Hunk #1 succeeded at 3863 (offset 15 lines).
patching file src/modules/standard/mod_status.c
patching file src/modules/proxy/mod_proxy.c
patching file src/modules/proxy/proxy_http.c
patching file src/support/apxs.pl
Hunk #1 succeeded at 754 (offset 2 lines).
patching file src/support/httpd.exp
patching file src/ApacheCore.def
#-perl
patch -d build-tree-apache-perl/apache_1.3.33 -p0 < build-tree-apache-perl/pkg.eapi/eapi.patch
patching file src/Configuration.tmpl
patching file src/Configure
Hunk #1 succeeded at 1868 (offset 13 lines).
patching file src/ap/Makefile.tmpl
patching file src/ap/ap.mak
patching file src/include/ap_mmn.h
patching file src/include/ap_alloc.h
patching file src/include/buff.h
patching file src/include/http_config.h
patching file src/include/http_conf_globals.h
patching file src/include/httpd.h
patching file src/main/alloc.c
patching file src/main/buff.c
patching file src/main/http_config.c
Hunk #4 succeeded at 1504 (offset 30 lines).
Hunk #5 succeeded at 1619 (offset 30 lines).
patching file src/main/http_main.c
Hunk #7 succeeded at 3667 (offset 1 line).
Hunk #8 succeeded at 4195 (offset 1 line).
Hunk #9 succeeded at 4378 (offset 1 line).
Hunk #10 succeeded at 4895 (offset 1 line).
Hunk #11 succeeded at 4926 (offset 1 line).
Hunk #12 succeeded at 4939 (offset 1 line).
Hunk #13 succeeded at 5725 (offset 11 lines).
Hunk #14 succeeded at 5897 (offset 11 lines).
Hunk #15 succeeded at 6277 (offset 11 lines).
Hunk #16 succeeded at 6290 (offset 11 lines).
Hunk #17 succeeded at 7868 (offset 11 lines).
Hunk #18 succeeded at 7912 (offset 11 lines).
patching file src/main/http_request.c
Hunk #1 succeeded at 1372 (offset 9 lines).
patching file src/main/http_protocol.c
Hunk #1 succeeded at 1172 (offset 12 lines).
Hunk #2 succeeded at 1332 (offset 12 lines).
patching file src/modules/standard/mod_so.c
Hunk #1 succeeded at 266 (offset 40 lines).
patching file src/modules/standard/mod_log_config.c
patching file src/modules/standard/mod_rewrite.c
Hunk #1 succeeded at 3863 (offset 15 lines).
patching file src/modules/standard/mod_status.c
patching file src/modules/proxy/mod_proxy.c
patching file src/modules/proxy/proxy_http.c
patching file src/support/apxs.pl
Hunk #1 succeeded at 754 (offset 2 lines).
patching file src/support/httpd.exp
patching file src/ApacheCore.def
#-ssl
cd build-tree-apache-ssl && \
	tar zxvf ../upstream/flavours/apache_1.3.29+ssl_1.55.tar.gz > /dev/null && \
	for i in `export LC_COLLATE=C && ls ../debian/patches/ssl/0*`; do patch -p1 < $i; done
patching file apache_1.3.33/src/support/apachectl
Hunk #1 succeeded at 121 (offset 15 lines).
Hunk #2 succeeded at 145 (offset 15 lines).
patching file apache_1.3.33/configure
patching file apache_1.3.33/Makefile.tmpl
patching file apache_1.3.33/src/ap/Makefile.tmpl
patching file apache_1.3.33/src/Configuration
patching file apache_1.3.33/src/Configuration.tmpl
patching file apache_1.3.33/src/Configure
Hunk #1 succeeded at 873 (offset 4 lines).
Hunk #2 succeeded at 1834 (offset 8 lines).
Hunk #3 succeeded at 2156 (offset 12 lines).
Hunk #4 succeeded at 2376 (offset 12 lines).
patching file apache_1.3.33/src/include/ap_config.h
Hunk #1 succeeded at 432 (offset -1 lines).
Hunk #2 succeeded at 1471 (offset -38 lines).
patching file apache_1.3.33/src/include/ap_mmn.h
patching file apache_1.3.33/src/include/buff.h
patching file apache_1.3.33/src/include/http_config.h
patching file apache_1.3.33/src/include/httpd.h
patching file apache_1.3.33/src/include/http_main.h
patching file apache_1.3.33/src/main/buff.c
patching file apache_1.3.33/src/main/http_config.c
patching file apache_1.3.33/src/main/http_log.c
patching file apache_1.3.33/src/main/http_main.c
Hunk #4 succeeded at 5802 (offset 10 lines).
Hunk #5 succeeded at 6123 (offset 10 lines).
patching file apache_1.3.33/src/main/Makefile.tmpl
patching file apache_1.3.33/src/main/util_script.c
patching file apache_1.3.33/src/Makefile.tmpl
patching file apache_1.3.33/src/modules/standard/Makefile.tmpl
patching file apache_1.3.33/src/modules/standard/mod_log_config.c
patching file apache_1.3.33/src/modules/standard/mod_so.c
Hunk #1 succeeded at 266 (offset 40 lines).
patching file apache_1.3.33/src/os/unix/Makefile.tmpl
patching file apache_1.3.33/src/support/apachectl
patching file apache_1.3.33/src/support/suexec.c
Hunk #1 succeeded at 95 (offset -4 lines).
patching file src/modules/ssl/apache_ssl.c
Hunk #1 succeeded at 2362 (offset 3 lines).
patching file pkg.eapi/eapi.patch
patching file apache_1.3.33/src/include/pass_cb.h
patching file apache_1.3.33/src/main/http_main.c
Hunk #4 succeeded at 8159 (offset 10 lines).
patching file src/modules/ssl/apache_ssl.c
Hunk #6 succeeded at 1609 (offset 1 line).
Hunk #7 succeeded at 1620 (offset 1 line).
patching file src/modules/ssl/Makefile.tmpl
patching file src/modules/ssl/pass_cb.c
patching file apache_1.3.33/src/support/Makefile.tmpl
cp -vpr build-tree-apache-ssl/src build-tree-apache-ssl/apache_1.3.33/
`build-tree-apache-ssl/src/modules/ssl' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl'
`build-tree-apache-ssl/src/modules/ssl/apache_ssl.c' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl/apache_ssl.c'
`build-tree-apache-ssl/src/modules/ssl/gcacheclient.c' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl/gcacheclient.c'
`build-tree-apache-ssl/src/modules/ssl/gcache.c' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl/gcache.c'
`build-tree-apache-ssl/src/modules/ssl/gcachecommon.c' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl/gcachecommon.c'
`build-tree-apache-ssl/src/modules/ssl/splashcache.c' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl/splashcache.c'
`build-tree-apache-ssl/src/modules/ssl/crlutil.c' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl/crlutil.c'
`build-tree-apache-ssl/src/modules/ssl/Makefile.tmpl' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl/Makefile.tmpl'
`build-tree-apache-ssl/src/modules/ssl/Makefile.libdir' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl/Makefile.libdir'
`build-tree-apache-ssl/src/modules/ssl/apache_ssl.c.orig' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl/apache_ssl.c.orig'
`build-tree-apache-ssl/src/modules/ssl/pass_cb.c' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl/pass_cb.c'
`build-tree-apache-ssl/src/modules/ssl-keynote' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl-keynote'
`build-tree-apache-ssl/src/modules/ssl-keynote/apache_ssl_keynote.c' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl-keynote/apache_ssl_keynote.c'
`build-tree-apache-ssl/src/modules/ssl-keynote/apache_ssl_keynote.module' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl-keynote/apache_ssl_keynote.module'
`build-tree-apache-ssl/src/modules/ssl-keynote/Makefile.tmpl' -> `build-tree-apache-ssl/apache_1.3.33/src/modules/ssl-keynote/Makefile.tmpl'
`build-tree-apache-ssl/src/include/gcache.h' -> `build-tree-apache-ssl/apache_1.3.33/src/include/gcache.h'
rm -fr build-tree-apache-ssl/src
patch -d build-tree-apache-ssl/apache_1.3.33 -p0 < build-tree-apache-ssl/pkg.eapi/eapi.patch
patching file src/ap/ap.mak
patching file src/ap/Makefile.tmpl
patching file src/ApacheCore.def
patching file src/Configuration.tmpl
patching file src/Configure
Hunk #1 succeeded at 1872 (offset 12 lines).
patching file src/include/ap_alloc.h
patching file src/include/ap_mmn.h
patching file src/include/buff.h
patching file src/include/http_conf_globals.h
patching file src/include/http_config.h
patching file src/include/httpd.h
patching file src/main/alloc.c
patching file src/main/buff.c
patching file src/main/http_config.c
Hunk #4 succeeded at 1524 (offset 4 lines).
Hunk #5 succeeded at 1639 (offset 4 lines).
patching file src/main/http_main.c
Hunk #1 succeeded at 246 (offset 4 lines).
Hunk #2 succeeded at 445 (offset 4 lines).
Hunk #3 succeeded at 1575 (offset 4 lines).
Hunk #4 succeeded at 1587 (offset 4 lines).
Hunk #5 succeeded at 1905 (offset 4 lines).
Hunk #6 succeeded at 2613 (offset 4 lines).
Hunk #7 succeeded at 3687 (offset 4 lines).
Hunk #8 succeeded at 4215 (offset 4 lines).
Hunk #9 succeeded at 4400 (offset 6 lines).
Hunk #10 succeeded at 4927 (offset 6 lines).
Hunk #11 succeeded at 4958 (offset 6 lines).
Hunk #12 succeeded at 4971 (offset 6 lines).
Hunk #13 succeeded at 5757 (offset 16 lines).
Hunk #14 succeeded at 5939 (offset 16 lines).
Hunk #15 succeeded at 6329 (offset 16 lines).
Hunk #16 succeeded at 6342 (offset 16 lines).
Hunk #17 succeeded at 7920 (offset 16 lines).
Hunk #18 succeeded at 7964 (offset 16 lines).
patching file src/main/http_protocol.c
Hunk #1 succeeded at 1172 (offset 12 lines).
Hunk #2 succeeded at 1332 (offset 12 lines).
patching file src/main/http_request.c
Hunk #1 succeeded at 1372 (offset 9 lines).
patching file src/modules/proxy/mod_proxy.c
patching file src/modules/proxy/proxy_http.c
patching file src/modules/standard/mod_log_config.c
patching file src/modules/standard/mod_rewrite.c
Hunk #1 succeeded at 3863 (offset 15 lines).
patching file src/modules/standard/mod_so.c
Hunk #1 succeeded at 266 (offset 40 lines).
patching file src/modules/standard/mod_status.c
patching file src/support/apxs.pl
patching file src/support/httpd.exp
#libapache-mod-perl
patch -d libapache-mod-perl-1.29 -p1 < debian/patches/mod-perl/DBD::Pg_mem_leak_workaround.diff
patching file lib/Apache/Resource.pm
patching file src/modules/perl/mod_perl.c
patch -d libapache-mod-perl-1.29 -p1 < debian/patches/mod-perl/debian_libperl_debug_fix.diff
patching file apaci/mod_perl.config.sh
Hunk #1 succeeded at 156 (offset 1 line).
patching file Makefile.PL
Hunk #1 succeeded at 543 (offset 13 lines).
patch -d libapache-mod-perl-1.29 -p1 < debian/patches/mod-perl/r_dir_config_fix.diff
patching file src/modules/perl/Apache.xs

*** Configuring apache ***

cd build-tree-apache/apache_1.3.33 && LDFLAGS="" CFLAGS="-O1  -g -Wall -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64" ./configure --suexec-logfile=/var/log/apache/suexec.log --target=apache --with-layout=Debian --enable-suexec --suexec-caller=www-data --suexec-docroot=/var/www --includedir=/usr/include/apache-1.3 --without-confadjust --without-execstrip --enable-shared=max --enable-rule=SHARED_CHAIN --enable-module=most --enable-module=status --enable-module=auth_digest --enable-module=log_referer --enable-module=log_agent --enable-module=auth_db  --activate-module=src/modules/extra/mod_macro.c
Configuring for Apache, Version 1.3.33
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
./configure: line 1: rule_[01: command not found
./configure: line 1: 31mrule[00m: command not found
 + using installation path layout: Debian (config.layout)
configure:Error: No such rule named 'SHARED_CHAIN'
make: *** [debian/stampdir/configure-stamp-apache] Error 1

--===============1051110579==--

Revision history for this message

In Debian Bug tracker #286975, Fabio Massimo Di Nitto (fabbione) wrote on 2004-12-23: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)

#4

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jon,

Unfortunatly i cannot reproduce it here at all, neither on sarge or sid.

|
| cd build-tree-apache/apache_1.3.33 && LDFLAGS="" CFLAGS="-O1 -g -Wall -D_LARGEFILE_SOURCE
- -D_FILE_OFFSET_BITS=64" ./configure --suexec-logfile=/var/log/apache/suexec.log --target=apache
- --with-layout=Debian --enable-suexec --suexec-caller=www-data --suexec-docroot=/var/www
- --includedir=/usr/include/apache-1.3 --without-confadjust --without-execstrip --enable-shared=max
- --enable-rule=SHARED_CHAIN --enable-module=most --enable-module=status --enable-module=auth_digest
- --enable-module=log_referer --enable-module=log_agent --enable-module=auth_db
- --activate-module=src/modules/extra/mod_macro.c
| Configuring for Apache, Version 1.3.33
| ../configure: line 1: rule_[01: command not found

I know for sure that configure explicitly requires bash, did you replace /bin/bash with another
shell? Can you verify the bash md5sum?

This is my best guess atm.. otherwise would it be possible for you to test the same
in a fresh sarge/sid chroot? that would really help to isolate the problem
between your installed system and my build-test env.

Thanks
Fabio

- --
Self-Service law:
The last available dish of the food you have decided to eat, will be
inevitably taken from the person in front of you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFByrd8hCzbekR3nhgRAnyMAJ9oj0YrLvR9q/e/yPTbxEp/FmFPLQCgjsCZ
nqqFxdUNeMKZrnq5c2qq7vo=
=LhWo
-----END PGP SIGNATURE-----

Revision history for this message

In Debian Bug tracker #286975, Jon Dowland (jond) wrote on 2004-12-23:

#5

On Thu, Dec 23, 2004 at 01:18:06PM +0100, Fabio Massimo Di Nitto wrote:

> I know for sure that configure explicitly requires bash, did you replace
> /bin/bash with another
> shell? Can you verify the bash md5sum?

~$ md5sum `which sh` `which bash`
6a01accdaa1baad9b2af1bcda2d80769 /bin/sh
6a01accdaa1baad9b2af1bcda2d80769 /bin/bash

> This is my best guess atm.. otherwise would it be possible for you to test
> the same
> in a fresh sarge/sid chroot? that would really help to isolate the problem
> between your installed system and my build-test env.

I'd be happy to help in any way possible, although things might be
delayed over the christmas break as my machine will most likely be off.
Can I achieve this using pbuilder?

Revision history for this message

In Debian Bug tracker #286975, Fabio Massimo Di Nitto (fabbione) wrote on 2004-12-23:

#6

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jon Dowland wrote:

|>This is my best guess atm.. otherwise would it be possible for you to test
|>the same
|>in a fresh sarge/sid chroot? that would really help to isolate the problem
|>between your installed system and my build-test env.
|
|
| I'd be happy to help in any way possible, although things might be
| delayed over the christmas break as my machine will most likely be off.
| Can I achieve this using pbuilder?

Yes. I did test with pbuilder too and i still can't reproduce the bug. Perhaps
something related to your user environment?

Fabio

PS i will leave for xmas holydays in a few hours too... so if we don't manage to
figure out the problem, don't worry.. we will work on it on monday.

- --
Self-Service law:
The last available dish of the food you have decided to eat, will be
inevitably taken from the person in front of you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFByrxhhCzbekR3nhgRAi13AJ9YCnU7i3MG/8MuscUHCWhkEV9P5ACggS21
7zDLuTqmzp81QLhc88NIgN0=
=q/mw
-----END PGP SIGNATURE-----

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-12-23:

#7

Message-ID: <email address hidden>
Date: Thu, 23 Dec 2004 13:18:06 +0100
From: Fabio Massimo Di Nitto <email address hidden>
To: Jon Dowland <email address hidden>, <email address hidden>
Subject: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not
found)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jon,

Unfortunatly i cannot reproduce it here at all, neither on sarge or sid.

|
| cd build-tree-apache/apache_1.3.33 && LDFLAGS="" CFLAGS="-O1 -g -Wall -D_LARGEFILE_SOURCE
- -D_FILE_OFFSET_BITS=64" ./configure --suexec-logfile=/var/log/apache/suexec.log --target=apache
- --with-layout=Debian --enable-suexec --suexec-caller=www-data --suexec-docroot=/var/www
- --includedir=/usr/include/apache-1.3 --without-confadjust --without-execstrip --enable-shared=max
- --enable-rule=SHARED_CHAIN --enable-module=most --enable-module=status --enable-module=auth_digest
- --enable-module=log_referer --enable-module=log_agent --enable-module=auth_db
- --activate-module=src/modules/extra/mod_macro.c
| Configuring for Apache, Version 1.3.33
| ../configure: line 1: rule_[01: command not found

I know for sure that configure explicitly requires bash, did you replace /bin/bash with another
shell? Can you verify the bash md5sum?

This is my best guess atm.. otherwise would it be possible for you to test the same
in a fresh sarge/sid chroot? that would really help to isolate the problem
between your installed system and my build-test env.

Thanks
Fabio

- --
Self-Service law:
The last available dish of the food you have decided to eat, will be
inevitably taken from the person in front of you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFByrd8hCzbekR3nhgRAnyMAJ9oj0YrLvR9q/e/yPTbxEp/FmFPLQCgjsCZ
nqqFxdUNeMKZrnq5c2qq7vo=
=LhWo
-----END PGP SIGNATURE-----

Message-ID: <41CAB77E.2060706@fabbione.net>
Date: Thu, 23 Dec 2004 13:18:06 +0100
From: Fabio Massimo Di Nitto <fabbione@fabbione.net>
To: Jon Dowland <bugs@alcopop.org>, 286975@bugs.debian.org
Subject: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not
 found)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jon,

Unfortunatly i cannot reproduce it here at all, neither on sarge or sid.

|
| cd build-tree-apache/apache_1.3.33 && LDFLAGS="" CFLAGS="-O1  -g -Wall -D_LARGEFILE_SOURCE
- -D_FILE_OFFSET_BITS=64" ./configure --suexec-logfile=/var/log/apache/suexec.log --target=apache
- --with-layout=Debian --enable-suexec --suexec-caller=www-data --suexec-docroot=/var/www
- --includedir=/usr/include/apache-1.3 --without-confadjust --without-execstrip --enable-shared=max
- --enable-rule=SHARED_CHAIN --enable-module=most --enable-module=status --enable-module=auth_digest
- --enable-module=log_referer --enable-module=log_agent --enable-module=auth_db
- --activate-module=src/modules/extra/mod_macro.c
| Configuring for Apache, Version 1.3.33
| ../configure: line 1: rule_[01: command not found

I know for sure that configure explicitly requires bash, did you replace /bin/bash with another
shell? Can you verify the bash md5sum?

This is my best guess atm.. otherwise would it be possible for you to test the same
in a fresh sarge/sid chroot? that would really help to isolate the problem
between your installed system and my build-test env.

Thanks
Fabio

- --
Self-Service law:
The last available dish of the food you have decided to eat, will be
inevitably taken from the person in front of you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFByrd8hCzbekR3nhgRAnyMAJ9oj0YrLvR9q/e/yPTbxEp/FmFPLQCgjsCZ
nqqFxdUNeMKZrnq5c2qq7vo=
=LhWo
-----END PGP SIGNATURE-----

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-12-23:

#8

Message-ID: <email address hidden>
Date: Thu, 23 Dec 2004 12:24:11 +0000
From: Jon Dowland <email address hidden>
To: Fabio Massimo Di Nitto <email address hidden>, <email address hidden>
Subject: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)

On Thu, Dec 23, 2004 at 01:18:06PM +0100, Fabio Massimo Di Nitto wrote:

> I know for sure that configure explicitly requires bash, did you replace
> /bin/bash with another
> shell? Can you verify the bash md5sum?

~$ md5sum `which sh` `which bash`
6a01accdaa1baad9b2af1bcda2d80769 /bin/sh
6a01accdaa1baad9b2af1bcda2d80769 /bin/bash

> This is my best guess atm.. otherwise would it be possible for you to test
> the same
> in a fresh sarge/sid chroot? that would really help to isolate the problem
> between your installed system and my build-test env.

I'd be happy to help in any way possible, although things might be
delayed over the christmas break as my machine will most likely be off.
Can I achieve this using pbuilder?

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2004-12-23:

#9

Message-ID: <email address hidden>
Date: Thu, 23 Dec 2004 13:38:58 +0100
From: Fabio Massimo Di Nitto <email address hidden>
To: Jon Dowland <email address hidden>
Cc: <email address hidden>
Subject: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not
found)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jon Dowland wrote:

|>This is my best guess atm.. otherwise would it be possible for you to test
|>the same
|>in a fresh sarge/sid chroot? that would really help to isolate the problem
|>between your installed system and my build-test env.
|
|
| I'd be happy to help in any way possible, although things might be
| delayed over the christmas break as my machine will most likely be off.
| Can I achieve this using pbuilder?

Yes. I did test with pbuilder too and i still can't reproduce the bug. Perhaps
something related to your user environment?

Fabio

PS i will leave for xmas holydays in a few hours too... so if we don't manage to
figure out the problem, don't worry.. we will work on it on monday.

- --
Self-Service law:
The last available dish of the food you have decided to eat, will be
inevitably taken from the person in front of you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFByrxhhCzbekR3nhgRAi13AJ9YCnU7i3MG/8MuscUHCWhkEV9P5ACggS21
7zDLuTqmzp81QLhc88NIgN0=
=q/mw
-----END PGP SIGNATURE-----

Revision history for this message

Matt Zimmerman (mdz) wrote on 2004-12-25:

#10

apache 1.3.x is in universe

Revision history for this message

In Debian Bug tracker #286975, Frank Lichtenheld (djpig) wrote on 2005-01-02: tagging 286975

#11

# Automatically generated email from bts, devscripts version 2.8.5
tags 286975 unreproducible

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-02:

#12

Message-Id: <email address hidden>
Date: Sun, 2 Jan 2005 02:06:23 +0100
From: Frank Lichtenheld <email address hidden>
To: <email address hidden>
Subject: tagging 286975

# Automatically generated email from bts, devscripts version 2.8.5
tags 286975 unreproducible

Revision history for this message

In Debian Bug tracker #286975, Fabio Massimo Di Nitto (fabbione) wrote on 2005-01-02: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)

#13

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jon Dowland wrote:
| On Thu, Dec 23, 2004 at 01:18:06PM +0100, Fabio Massimo Di Nitto wrote:
|
|
|>I know for sure that configure explicitly requires bash, did you replace
|>/bin/bash with another
|>shell? Can you verify the bash md5sum?
|
|
| ~$ md5sum `which sh` `which bash`
| 6a01accdaa1baad9b2af1bcda2d80769 /bin/sh
| 6a01accdaa1baad9b2af1bcda2d80769 /bin/bash
|
|
|>This is my best guess atm.. otherwise would it be possible for you to test
|>the same
|>in a fresh sarge/sid chroot? that would really help to isolate the problem
|>between your installed system and my build-test env.
|
|
| I'd be happy to help in any way possible, although things might be
| delayed over the christmas break as my machine will most likely be off.
| Can I achieve this using pbuilder?
|
|

Jon, nobody has been able to reproduce this problem. Can you kindly test again
as we agreed?

Fabio

- --
Self-Service law:
The last available dish of the food you have decided to eat, will be
inevitably taken from the person in front of you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB14yxhCzbekR3nhgRAgywAJ9QuodnPZLwaiSI4IH2iriqnBKzMQCfYKIN
BPJcrxMtmbUBGKXv8zUR1qc=
=0Jbt
-----END PGP SIGNATURE-----

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-02:

#14

Message-ID: <email address hidden>
Date: Sun, 02 Jan 2005 06:54:58 +0100
From: Fabio Massimo Di Nitto <email address hidden>
To: Jon Dowland <email address hidden>, <email address hidden>
Subject: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not
found)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jon Dowland wrote:
| On Thu, Dec 23, 2004 at 01:18:06PM +0100, Fabio Massimo Di Nitto wrote:
|
|
|>I know for sure that configure explicitly requires bash, did you replace
|>/bin/bash with another
|>shell? Can you verify the bash md5sum?
|
|
| ~$ md5sum `which sh` `which bash`
| 6a01accdaa1baad9b2af1bcda2d80769 /bin/sh
| 6a01accdaa1baad9b2af1bcda2d80769 /bin/bash
|
|
|>This is my best guess atm.. otherwise would it be possible for you to test
|>the same
|>in a fresh sarge/sid chroot? that would really help to isolate the problem
|>between your installed system and my build-test env.
|
|
| I'd be happy to help in any way possible, although things might be
| delayed over the christmas break as my machine will most likely be off.
| Can I achieve this using pbuilder?
|
|

Jon, nobody has been able to reproduce this problem. Can you kindly test again
as we agreed?

Fabio

- --
Self-Service law:
The last available dish of the food you have decided to eat, will be
inevitably taken from the person in front of you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB14yxhCzbekR3nhgRAgywAJ9QuodnPZLwaiSI4IH2iriqnBKzMQCfYKIN
BPJcrxMtmbUBGKXv8zUR1qc=
=0Jbt
-----END PGP SIGNATURE-----

Revision history for this message

In Debian Bug tracker #286975, Steve Langasek (vorlon) wrote on 2005-01-04: unreproducible bug, weird user environment -- not RC

#15

severity 286975 important
thanks

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-04:

#16

Message-ID: <email address hidden>
Date: Tue, 4 Jan 2005 01:42:58 -0800
From: Steve Langasek <email address hidden>
To: <email address hidden>
Subject: unreproducible bug, weird user environment -- not RC

severity 286975 important
thanks

Revision history for this message

In Debian Bug tracker #286975, Jon Dowland (jon-dowland-dunelm) wrote on 2005-01-12: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)

#17

On Sun, Jan 02, 2005 at 06:54:58AM +0100, Fabio Massimo Di Nitto wrote:
> Jon, nobody has been able to reproduce this problem. Can you kindly test
> again as we agreed?

Worked out what it is, my GREP_OPTIONS environment variable contains the
following
GREP_OPTIONS="--colour=always"

The build process is passed some colour escape characters and chokes.
apache isn't the only program which suffers (from memory, 'at' too) and
a great deal of software programs go haywire also.

Not sure which program responsibility would lie with, but I'd guess that
there should be no assumptions made as to user preferences for programs
like grep, perhaps the environment variable should be ignored.

I note that --colour=auto makes grep selectively colour and I presume it
only does it for interactive terminals: apache builds ok with this set.

Revision history for this message

In Debian Bug tracker #286975, Matthew Wilcox (matthew-wil) wrote on 2005-01-12:

#18

On Wed, Jan 12, 2005 at 02:24:21PM +0000, Jon Dowland wrote:
> On Sun, Jan 02, 2005 at 06:54:58AM +0100, Fabio Massimo Di Nitto wrote:
> > Jon, nobody has been able to reproduce this problem. Can you kindly test
> > again as we agreed?
>
> Worked out what it is, my GREP_OPTIONS environment variable contains the
> following
> GREP_OPTIONS="--colour=always"
>
> The build process is passed some colour escape characters and chokes.
> apache isn't the only program which suffers (from memory, 'at' too) and
> a great deal of software programs go haywire also.
>
> Not sure which program responsibility would lie with, but I'd guess that
> there should be no assumptions made as to user preferences for programs
> like grep, perhaps the environment variable should be ignored.

The trouble is that to fix this would require not just looking at the
manpage for grep to work out which variables to unset, but also the
manpages for every other tool that we use, looking at each variable the
user *might* set, and seeing if it could be harmful.

I don't think this is a reasonable thing for us to do.

> I note that --colour=auto makes grep selectively colour and I presume it
> only does it for interactive terminals: apache builds ok with this set.

Yes, --color=auto is a much more reasonable approach.

--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-12:

#19

Message-ID: <email address hidden>
Date: Wed, 12 Jan 2005 14:24:21 +0000
From: Jon Dowland <email address hidden>
To: <email address hidden>
Subject: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)

On Sun, Jan 02, 2005 at 06:54:58AM +0100, Fabio Massimo Di Nitto wrote:
> Jon, nobody has been able to reproduce this problem. Can you kindly test
> again as we agreed?

Worked out what it is, my GREP_OPTIONS environment variable contains the
following
GREP_OPTIONS="--colour=always"

The build process is passed some colour escape characters and chokes.
apache isn't the only program which suffers (from memory, 'at' too) and
a great deal of software programs go haywire also.

Not sure which program responsibility would lie with, but I'd guess that
there should be no assumptions made as to user preferences for programs
like grep, perhaps the environment variable should be ignored.

I note that --colour=auto makes grep selectively colour and I presume it
only does it for interactive terminals: apache builds ok with this set.

Revision history for this message

In Debian Bug tracker #286975, Jon Dowland (jon-dowland-dunelm) wrote on 2005-01-12:

#20

On Wed, Jan 12, 2005 at 02:54:05PM +0000, Matthew Wilcox wrote:

> The trouble is that to fix this would require not just looking at the
> manpage for grep to work out which variables to unset, but also the
> manpages for every other tool that we use, looking at each variable the
> user *might* set, and seeing if it could be harmful.
>
> I don't think this is a reasonable thing for us to do.

No, I agree- that is overkill. Some of the people I have discussed this
with would rather see GREP_OPTIONS dropped from GNU grep ;)

> > I note that --colour=auto makes grep selectively colour and I presume it
> > only does it for interactive terminals: apache builds ok with this set.
>
> Yes, --color=auto is a much more reasonable approach.

The grep docs say that you can use 'always', 'never', 'auto', but don't
actually explain what they are (all but auto of course are fairly
self-explanatory). Perhaps this could be a reassign minor doc bug on
grep? Something I'd work on patching myself. (must remember to see where
debian stands with the gnu documentation these days, could be letting
myself into a bigger job than I realise ;))

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-12:

#21

Message-ID: <email address hidden>
Date: Wed, 12 Jan 2005 14:54:05 +0000
From: Matthew Wilcox <email address hidden>
To: Jon Dowland <email address hidden>, <email address hidden>
Subject: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)

On Wed, Jan 12, 2005 at 02:24:21PM +0000, Jon Dowland wrote:
> On Sun, Jan 02, 2005 at 06:54:58AM +0100, Fabio Massimo Di Nitto wrote:
> > Jon, nobody has been able to reproduce this problem. Can you kindly test
> > again as we agreed?
>
> Worked out what it is, my GREP_OPTIONS environment variable contains the
> following
> GREP_OPTIONS="--colour=always"
>
> The build process is passed some colour escape characters and chokes.
> apache isn't the only program which suffers (from memory, 'at' too) and
> a great deal of software programs go haywire also.
>
> Not sure which program responsibility would lie with, but I'd guess that
> there should be no assumptions made as to user preferences for programs
> like grep, perhaps the environment variable should be ignored.

The trouble is that to fix this would require not just looking at the
manpage for grep to work out which variables to unset, but also the
manpages for every other tool that we use, looking at each variable the
user *might* set, and seeing if it could be harmful.

I don't think this is a reasonable thing for us to do.

> I note that --colour=auto makes grep selectively colour and I presume it
> only does it for interactive terminals: apache builds ok with this set.

Yes, --color=auto is a much more reasonable approach.

--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain

Message-ID: <20050112145405.GX27371@parcelfarce.linux.theplanet.co.uk>
Date: Wed, 12 Jan 2005 14:54:05 +0000
From: Matthew Wilcox <matthew@wil.cx>
To: Jon Dowland <jon.dowland@dunelm.org.uk>, 286975@bugs.debian.org
Subject: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)

On Wed, Jan 12, 2005 at 02:24:21PM +0000, Jon Dowland wrote:
> On Sun, Jan 02, 2005 at 06:54:58AM +0100, Fabio Massimo Di Nitto wrote:
> > Jon, nobody has been able to reproduce this problem. Can you kindly test 
> > again as we agreed?
> 
> Worked out what it is, my GREP_OPTIONS environment variable contains the
> following
> 	GREP_OPTIONS="--colour=always"
> 
> The build process is passed some colour escape characters and chokes.
> apache isn't the only program which suffers (from memory, 'at' too) and
> a great deal of software programs go haywire also.
> 
> Not sure which program responsibility would lie with, but I'd guess that
> there should be no assumptions made as to user preferences for programs
> like grep, perhaps the environment variable should be ignored.

The trouble is that to fix this would require not just looking at the
manpage for grep to work out which variables to unset, but also the
manpages for every other tool that we use, looking at each variable the
user *might* set, and seeing if it could be harmful.

I don't think this is a reasonable thing for us to do.

> I note that --colour=auto makes grep selectively colour and I presume it
> only does it for interactive terminals: apache builds ok with this set.

Yes, --color=auto is a much more reasonable approach.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-01-12:

#22

Message-ID: <email address hidden>
Date: Wed, 12 Jan 2005 15:08:17 +0000
From: Jon Dowland <email address hidden>
To: <email address hidden>
Subject: Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)

On Wed, Jan 12, 2005 at 02:54:05PM +0000, Matthew Wilcox wrote:

> The trouble is that to fix this would require not just looking at the
> manpage for grep to work out which variables to unset, but also the
> manpages for every other tool that we use, looking at each variable the
> user *might* set, and seeing if it could be harmful.
>
> I don't think this is a reasonable thing for us to do.

No, I agree- that is overkill. Some of the people I have discussed this
with would rather see GREP_OPTIONS dropped from GNU grep ;)

> > I note that --colour=auto makes grep selectively colour and I presume it
> > only does it for interactive terminals: apache builds ok with this set.
>
> Yes, --color=auto is a much more reasonable approach.

The grep docs say that you can use 'always', 'never', 'auto', but don't
actually explain what they are (all but auto of course are fairly
self-explanatory). Perhaps this could be a reassign minor doc bug on
grep? Something I'd work on patching myself. (must remember to see where
debian stands with the gnu documentation these days, could be letting
myself into a bigger job than I realise ;))

Revision history for this message

In Debian Bug tracker #286975, Jon Dowland (jon-dowland-name) wrote on 2005-04-20: reassigning

#23

package apache
reassign 286975 grep

package grep
retitle 286975 grep/docs: --color argument, what does 'auto' do?
severity 286975 minor

thanks

In summary: the --color argument to grep, which takes 'always', 'none'
(somewhat self-explanatory) and 'auto' arguments. The documentation does
not describe what 'auto' does.

--
Jon Dowland
http://jon.dowland.name/
PGP fingerprint: 7032F238

Revision history for this message

In Debian Bug tracker #286975, Jon Dowland (jon-dowland-name) wrote on 2005-04-20: grep documentation bug reassigned

#24

package grep
tags 286975 -unreproducible
thanks

Hello, CCing <email address hidden> as I believe that's the thing to do
when reassigning a bug to a different package. In short this bug is now
a minor documentation issue regarding what --color=auto does.

--
Jon Dowland
http://jon.dowland.name/
PGP fingerprint: 7032F238

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-04-21:

#25

Message-ID: <email address hidden>
Date: Wed, 20 Apr 2005 17:23:48 +0100
From: Jon Dowland <email address hidden>
To: <email address hidden>
Subject: reassigning

package apache
reassign 286975 grep

package grep
retitle 286975 grep/docs: --color argument, what does 'auto' do?
severity 286975 minor

thanks

In summary: the --color argument to grep, which takes 'always', 'none'
(somewhat self-explanatory) and 'auto' arguments. The documentation does
not describe what 'auto' does.

--
Jon Dowland
http://jon.dowland.name/
PGP fingerprint: 7032F238

Revision history for this message

Debian Bug Importer (debzilla) wrote on 2005-04-21:

#26

Message-ID: <email address hidden>
Date: Wed, 20 Apr 2005 17:38:37 +0100
From: Jon Dowland <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: grep documentation bug reassigned

package grep
tags 286975 -unreproducible
thanks

Hello, CCing <email address hidden> as I believe that's the thing to do
when reassigning a bug to a different package. In short this bug is now
a minor documentation issue regarding what --color=auto does.

--
Jon Dowland
http://jon.dowland.name/
PGP fingerprint: 7032F238

Revision history for this message

In Debian Bug tracker #286975, Jon Dowland (jond) wrote on 2008-03-03: submitter 286975

#27

# Automatically generated email from bts, devscripts version 2.10.13
submitter 286975 <email address hidden>

Revision history for this message

In Debian Bug tracker #286975, Martin Weis (martin-weis-newsadress) wrote on 2009-01-13: grep: (german translation of) man page is missing option color

#28

Package: grep
Version: 2.5.1.ds2-6
Followup-For: Bug #286975

The german man page is missing the option color, here is my translation:

[en]
--colour[=WHEN], --color[=WHEN]
Surround the matching string with the marker find in GREP_COLOR environment variable. WHEN may be `never', `always', or `auto'

[de]
--colour[=WANN], --color[=WANN]
Umgibt den passenden String mit der Markierung, die in der Umgebungsvariable GREP_COLOR definiert ist. WANN kann `never' (niemals), `always'
(immer), oder `auto' (-matisch) sein.

-- System Information:
Debian Release: 4.0
APT prefers stable
APT policy: (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-6-686
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)

Versions of packages grep depends on:
ii libc6 2.3.6.ds1-13etch8 GNU C Library: Shared libraries

grep recommends no packages.

-- no debconf information

Affects		Status	Importance	Assigned to	Milestone
	apache (Debian)	New	Unknown	debbugs #286975
	apache (Ubuntu)	Invalid	High	Unassigned

Debian
apache package

apache: FTBFS - x86/testing (31mrule: command not found)

Bug Description

Other bug subscribers

Remote bug watches

Debianapache package

apache: FTBFS - x86/testing (31mrule: command not found)

Bug Description

Other bug subscribers

Remote bug watches

Debian
apache package