Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)
On Wed, Jan 12, 2005 at 02:54:05PM +, 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 ;)) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)
On Wed, Jan 12, 2005 at 02:24:21PM +, 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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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-
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-
Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Jon, Jon Dowland wrote: | 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. 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-
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?
Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found)
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.10Debian configuration management sy
ii dpkg1.10.25 Package maintenance system for Deb
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
ii libdb4.24.2.52-17Berkeley 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-2Log rotation utility
ii mime-support3.28-1 MIME files 'mime.types' & 'mailcap
ii perl5.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: [EMAIL PROTECTED]
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 PROTECTED]>
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 s
