Your message dated Mon, 5 May 2008 17:41:23 +0100
with message-id <[EMAIL PROTECTED]>
and subject line bool has been removed from Debian, closing #280101
has caused the Debian Bug report #280101,
regarding bool: the AND operator acts like OR
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
280101: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=280101
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: bool
Version: 0.2.1-5
Severity: important
The AND operator acts like OR:
% man bool | bool -Pn -O0 "a or the" - | wc
283 2772 18687
% man bool | bool -Pn -O0 "a and the" - | wc
283 2772 18687
# how about identical results?
% man bool | bool -Pn -O0 "a and the" - > /tmp/b1
% man bool | bool -Pn -O0 "a or the" - > /tmp/b2
% diff /tmp/b[12]
% echo $?
0 # output of both is the same
...the above isn't coincidental. Here's what 'grep' with
pipes does:
# lines with "a" AND "the"?
% man bool | grep a | grep the | wc -l
42
# lines with "a" OR "the"?
% man bool | grep a > /tmp/g1
% man bool | grep the >> /tmp/g1
% sort < /tmp/g1 | uniq | wc -l
84 # it's not 42.
Hope this helps...
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.26-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)
Versions of packages bool depends on:
ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 0.2.1-6+rm
The bool package has been removed from Debian testing, unstable and
experimental, so I am now closing the bugs that were still opened
against it.
For more information about this package's removal, read
http://bugs.debian.org/463801 . That bug might give the reasons why
this package was removed, and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--
Marco Rodrigues
http://Marco.Tondela.org
--- End Message ---
