Hello, I understand your frustration, but there is nothing I can do about this on the Debian side. In every single tmux release, options come and go. You can take this upstream directly if you like, but you're not the first to complain and things are unlikely to change; legacy is infinitely-growing baggage that the upstream authors don't want to carry in the codebase.
I see no value in duplicating the upstream changelog in NEWS.Debian, the only exception is protocol changes because they make it difficult to reattach to a running session when upgrading. Also, I make an effort to package upcoming upstream releases well ahead of time in experimental, in this case tmux 2.2 has been available in Debian since the beginning of February. I do this to give people time to test their configs or add-ons before the version becomes widely available. Apparently the powerline maintainers don't care enough to do so. I'm going to close this bug. Regards, -- Romain Francoise <rfranco...@debian.org> http://people.debian.org/~rfrancoise/
