https://bugs.exim.org/show_bug.cgi?id=2833
Bug ID: 2833
Summary: Need munging for dumpdb of "seen"
Product: Exim
Version: 4.95
Hardware: All
OS: FreeBSD
Status: NEW
Severity: bug
Priority: medium
Component: Test harness
Assignee: unallocated@exim.org
Reporter: jgh146exb@wizmail.org
CC: exim-dev@exim.org
The recently-introduced "seen" DB can have different dump orders on different
platforms, so needs munging in similar fashion to "retry" (where a
"map-sort-map: Schwartz's transformation" is used to keep 127.0.0.1
sorting first.
The situation differs slightly in that keys are not always, or only pure,
ipv4 addresses. The current testcase (0626) always uses an ipv4 *prefix*.
0626 fails on FreeBSD due to this.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
Bug ID: 2833
Summary: Need munging for dumpdb of "seen"
Product: Exim
Version: 4.95
Hardware: All
OS: FreeBSD
Status: NEW
Severity: bug
Priority: medium
Component: Test harness
Assignee: unallocated@exim.org
Reporter: jgh146exb@wizmail.org
CC: exim-dev@exim.org
The recently-introduced "seen" DB can have different dump orders on different
platforms, so needs munging in similar fashion to "retry" (where a
"map-sort-map: Schwartz's transformation" is used to keep 127.0.0.1
sorting first.
The situation differs slightly in that keys are not always, or only pure,
ipv4 addresses. The current testcase (0626) always uses an ipv4 *prefix*.
0626 fails on FreeBSD due to this.
--
You are receiving this mail because:
You are on the CC list for the bug.
--
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##