summaryrefslogtreecommitdiff
path: root/security/sleuthkit/buildlink3.mk
diff options
context:
space:
mode:
authorryoon <ryoon@pkgsrc.org>2016-03-14 13:16:31 +0000
committerryoon <ryoon@pkgsrc.org>2016-03-14 13:16:31 +0000
commit1dfba5a18d63004ecc0daa216b21fc3a69e6f191 (patch)
treec9df8e966c96a230bb1de79505b89d545627eb33 /security/sleuthkit/buildlink3.mk
parentacd083b0be6a34f627a979aed055306451f21848 (diff)
downloadpkgsrc-1dfba5a18d63004ecc0daa216b21fc3a69e6f191.tar.gz
Update to 2.24
Changelog: * Noteworthy changes in release 2.24 (2016-03-10) [stable] ** Bug fixes grep -z would match strings it should not. To trigger the bug, you'd have to use a regular expression including an anchor (^ or $) and a feature like a range or a backreference, causing grep to forego its DFA matcher and resort to using re_search. With a multibyte locale, that matcher could mistakenly match a string containing a newline. For example, this command: printf 'a\nb\0' | LC_ALL=en_US.utf-8 grep -z '^[a-b]*b' would mistakenly match and print all four input bytes. After the fix, there is no match, as expected. [bug introduced in grep-2.7] grep -Pz now diagnoses attempts to use patterns containing ^ and $, instead of mishandling these patterns. This problem seems to be inherent to the PCRE API; removing this limitation is on PCRE's maint/README wish list. Patterns can continue to match literal ^ and $ by escaping them with \ (now needed even inside [...]). [bug introduced in grep-2.5]
Diffstat (limited to 'security/sleuthkit/buildlink3.mk')
0 files changed, 0 insertions, 0 deletions