Hi, On Mon, May 4, 2020 at 10:15 AM Julien Cristau <jcris...@debian.org> wrote: > I don't think that's acceptable. Running upgrades inside screen or > tmux is a best practice, so IMO it needs to work, and people need to be > able to re-attach to existing sessions across the upgrade.
The tmux authors make no promise about the compatibility between new clients and old servers, and some versions break the protocol. That's just how it is. However: in this specific instance, I lazily copied the same NEWS blurb I always use when the protocol version changes, but upstream made a deliberate decision *not* to bump the protocol version this time because the incompatibility issue in 3.1 only affects some commands (the ones that send data on stdout from the client). It's possible to attach to an old server from the new client and terminate it properly, and even if that wasn't the case you could use the old binary from /proc/pid/exe (which, as I discovered in 2012 in the bug you linked, is not possible with screen because it's setgid). So with that in mind, I rephrased the NEWS entry as follows: https://salsa.debian.org/rfrancoise/tmux/-/commit/15dd27614d659b8cae53c9e5acb54d70f321fcb4 That's the best I can do about this, and I will therefore close this bug with the upload. Also, the entire point of adding entries like this to NEWS.Debian is that apt-listchanges will prompt for confirmation before starting the upgrade if it's configured properly. Perhaps that configuration should be more widely documented and encouraged. Thanks.
