apache: FTBFS - x86/testing (31mrule: command not found)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apache (Debian) |
New
|
Unknown
|
|||
apache (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
Automatically imported from Debian bug report #286975 http://
In Debian Bug tracker #286975, Jon Dowland (jon-dowland) wrote : additional information | #1 |
Debian Bug Importer (debzilla) wrote : | #2 |
Automatically imported from Debian bug report #286975 http://
Debian Bug Importer (debzilla) wrote : | #3 |
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)
--=====
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-
Content-
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/
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=
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/
apache/
apache/
* apache/
apache/init: true
apache/
--=====
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-
Content-
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/
rm -f debian/apache{,...
In Debian Bug tracker #286975, Fabio Massimo Di Nitto (fabbione) wrote : Re: Bug#286975: apache: FTBFS - x86/testing (31mrule: command not found) | #4 |
-----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-
- -D_FILE_
- --with-
- --includedir=
- --enable-
- --enable-
- --activate-
| 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://
iD8DBQFByrd8hCz
nqqFxdUNeMKZrnq
=LhWo
-----END PGP SIGNATURE-----
In Debian Bug tracker #286975, Jon Dowland (jond) wrote : | #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`
6a01accdaa1baad
6a01accdaa1baad
> 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?
In Debian Bug tracker #286975, Fabio Massimo Di Nitto (fabbione) wrote : | #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://
iD8DBQFByrxhhCz
7zDLuTqmzp81QLh
=q/mw
-----END PGP SIGNATURE-----
Debian Bug Importer (debzilla) wrote : | #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,
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-
- -D_FILE_
- --with-
- --includedir=
- --enable-
- --enable-
- --activate-
| 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://
iD8DBQFByrd8hCz
nqqFxdUNeMKZrnq
=LhWo
-----END PGP SIGNATURE-----
Debian Bug Importer (debzilla) wrote : | #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`
6a01accdaa1baad
6a01accdaa1baad
> 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?
Debian Bug Importer (debzilla) wrote : | #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://
iD8DBQFByrxhhCz
7zDLuTqmzp81QLh
=q/mw
-----END PGP SIGNATURE-----
Matt Zimmerman (mdz) wrote : | #10 |
apache 1.3.x is in universe
In Debian Bug tracker #286975, Frank Lichtenheld (djpig) wrote : tagging 286975 | #11 |
# Automatically generated email from bts, devscripts version 2.8.5
tags 286975 unreproducible
Debian Bug Importer (debzilla) wrote : | #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
In Debian Bug tracker #286975, Fabio Massimo Di Nitto (fabbione) wrote : 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`
| 6a01accdaa1baad
| 6a01accdaa1baad
|
|
|>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://
iD8DBQFB14yxhCz
BPJcrxMtmbUBGKX
=0Jbt
-----END PGP SIGNATURE-----
Debian Bug Importer (debzilla) wrote : | #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`
| 6a01accdaa1baad
| 6a01accdaa1baad
|
|
|>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://
iD8DBQFB14yxhCz
BPJcrxMtmbUBGKX
=0Jbt
-----END PGP SIGNATURE-----
In Debian Bug tracker #286975, Steve Langasek (vorlon) wrote : unreproducible bug, weird user environment -- not RC | #15 |
severity 286975 important
thanks
Debian Bug Importer (debzilla) wrote : | #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
In Debian Bug tracker #286975, Jon Dowland (jon-dowland-dunelm) wrote : 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=
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.
In Debian Bug tracker #286975, Matthew Wilcox (matthew-wil) wrote : | #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=
>
> 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
Debian Bug Importer (debzilla) wrote : | #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=
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.
In Debian Bug tracker #286975, Jon Dowland (jon-dowland-dunelm) wrote : | #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 ;))
Debian Bug Importer (debzilla) wrote : | #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=
>
> 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
Debian Bug Importer (debzilla) wrote : | #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 ;))
In Debian Bug tracker #286975, Jon Dowland (jon-dowland-name) wrote : 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://
PGP fingerprint: 7032F238
In Debian Bug tracker #286975, Jon Dowland (jon-dowland-name) wrote : 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://
PGP fingerprint: 7032F238
Debian Bug Importer (debzilla) wrote : | #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://
PGP fingerprint: 7032F238
Debian Bug Importer (debzilla) wrote : | #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://
PGP fingerprint: 7032F238
In Debian Bug tracker #286975, Jon Dowland (jond) wrote : submitter 286975 | #27 |
# Automatically generated email from bts, devscripts version 2.10.13
submitter 286975 <email address hidden>
In Debian Bug tracker #286975, Martin Weis (martin-weis-newsadress) wrote : 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]
[de]
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=
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
Building with debuild as appose to dpkg-buildpackage seems to work.
Attached is the output of a successful debuild run.