Hi Richard, Thank you for looping me in.
On Tue, Dec 24, 2024 at 3:46 PM Richard Lewis <richard.lewis.deb...@googlemail.com> wrote: > Is a tmux client from bookworm able to connect to a server from trixie? The socket protocol has not changed from 3.3a (bookworm) to 3.5a (trixie), so yes. Note that the issue with upgrades is the other way around: you run the system upgrade in a tmux server from bookworm, upgrade your tmux package, and then cannot reconnect to the old server using the new client because of the protocol change. Unless you use your in-memory copy of the old binary via `/proc/nnn/exe` (on Linux). > it was requested that the release notes suggest doing the upgrade in tmux ( > in preference/as an alternagive to screen, which has been suggested for many > years). > In this discussion on salsa it's been queried whether tmux retains enough > compatibility to make this a good idea. > https://salsa.debian.org/rfrancoise/tmux/-/blob/master/debian/NEWS?ref_type=heads > says this was an issue in 2020, but does not have anything recent. > What's your view of this a) for trixie and b) for future releases? Upstream makes no compatibility promises, the socket protocol can change at any time. In fact, the format of the configuration file often also changes in incompatible ways from one release to the next. But tmux has reached some level of maturity and is no longer as actively developed as it once was, so such breaks tend to be less frequent now. I have no strong opinion on the MR; as far as I know, screen doesn't make any compatibility promises either, it was just stagnant for many years. -- Romain Francoise <rfranco...@debian.org> https://people.debian.org/~rfrancoise/
