Package: grep Version: 2.5.3~dfsg-1 Severity: normal The current version of grep behaves differentls when parsing null terminated data. To reproduce this I created the following directory structure: . ./1 ./dir2 ./dir1 ./dir1/1 ./dir1/2 ./pattern
pattern contains: ^.$ ^./1$ ^./dir1 "find -depth | grep -avf ./pattern" returns the expected output: ./dir2 ./pattern The same command, but this time with null terminated strings returns: find -depth -print0 | grep --null-data -avf ./pattern ./dir2./dir1/1./dir1/2./dir1./pattern As you can see, the output now contains dir1. The version of grep in testing does not show this behaviour. and both results are equal. Has this been intentionally changed with the current version of grep? -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.23-rc3-git1 (PREEMPT) Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages grep depends on: ii libc6 2.6.1-1+b1 GNU C Library: Shared libraries grep recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
