[MacPorts] #56873: Inconsistent behavior between ncurses 6.1.20180127 and ncurses 5.7

[MacPorts]

#56873: Inconsistent behavior between ncurses 6.1.20180127 and ncurses 5.7
----------------------+----------------------
  Reporter:  LiamFry  |      Owner:  jmroot
      Type:  defect   |     Status:  reopened
  Priority:  Normal   |  Milestone:
 Component:  ports    |    Version:  2.5.3
Resolution:           |   Keywords:
      Port:  ncurses  |
----------------------+----------------------
Changes (by LiamFry):

 * status:  closed => reopened
 * resolution:  invalid =>


Comment:

 After more testing, I re-opened the ticket. I downloaded and built the
 ncurses test suite ([https://invisible-island.net/ncurses/ncurses-
 examples.html]) I built it against the macOS-bundled ncurses and the
 MacPorts-installed ncurses. I also built it on a Debian GNU/Linux system.
 I then ran "tclock" in macOS/iTerm2, macOS/iTerm2/tmux,
 macOS/XQuartz/xterm, Debian UXTerm, UXTerm/tmux. Every 5 seconds, the
 clock's background switches between black and blue.

 I'm using the non-macOS system as the exemplar.

 * Debian/UXTerm/ncurses6 (TERM=xterm-256color) --> blue-to-black
 background transition fully resets (OK)
 * Debian/UXTerm/tmux/ncurses6 (TERM=screen) --> blue-to-black resets (OK)

 * macOS/iTerm2/ncurses5 (TERM=xterm-256color) --> blue-to-black background
 transition fully resets (OK)
 * macOS/iTerm2/tmux/ncurses5 (TERM=screen) --> blue-to-black resets (OK)
 * macOS/XQuarts/xterm/ncurses5 (TERM=xterm-256color) --> blue-to-black
 resets (OK)
 * macOS/XQuarts/xterm/tmux/ncurses5 (TERM=screen) --> blue-to-black resets
 (OK)

 * macOS/iTerm2/ncurses6 (TERM=xterm-256color) --> blue-to-black background
 transition lingers on hour digits (ERR)
 * macOS/iTerm2/tmux/ncurses6 (TERM=screen) --> blue-to-black lingers (ERR)
 * macOS/XQuarts/xterm/ncurses6 (TERM=xterm-256color) --> blue-to-black
 lingers (ERR)
 * macOS/XQuarts/xterm/tmux/ncurses6 (TERM=screen) --> blue-to-black
 lingers (ERR)

 The common component in the misbehaving scenarios is the MacPorts-
 installed ncurses 6.1; iTerm2 and TERM are out of the equation for 1/2 of
 these failed tests. If this is '''not''' an iTerm issue - which I believe
 I've demonstrated, then it must either be a macOS issue or a
 MacPorts/ncurses-6.1 issue.

-- 
Ticket URL: <https://trac.macports.org/ticket/56873#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS