blob: de6991662ea3e531ef4b9c6f3a67491671d6137c (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
|
tmux (3.1~rc1-1) experimental; urgency=medium
Please restart tmux entirely after upgrading to 3.1: an old server and
a new client will not be fully compatible with each other and the new
client may hang.
Note: if necessary the old client can be used via /proc/pid/exe to
talk to the old server, e.g. `/proc/$(pgrep "tmux: server")/exe attach'.
-- Romain Francoise <rfrancoise@debian.org> Tue, 11 Feb 2020 21:15:08 +0100
tmux (1.9-1) experimental; urgency=low
The server protocol version was changed from 7 to 8, we recommend that
you close any open tmux sessions before proceeding with the upgrade.
-- Romain Francoise <rfrancoise@debian.org> Sat, 22 Feb 2014 17:42:35 +0100
tmux (1.7~svn2819-1) experimental; urgency=low
The server protocol version was changed from 6 to 7, we recommend that
you close any open tmux sessions before proceeding with the upgrade.
-- Romain Francoise <rfrancoise@debian.org> Wed, 30 May 2012 19:52:56 +0200
tmux (1.4-7) unstable; urgency=low
Starting with version 1.4-7, tmux is no longer installed setgid utmp and
server sockets are no longer placed under /var/run/tmux, reverting to
the default upstream behavior (sockets in a user directory under /tmp).
We recommend that you close any open tmux sessions before proceeding
with the upgrade. If necessary, old servers can be accessed after the
upgrade with e.g. "tmux -S /var/run/tmux/tmux-`id -u`/default attach".
-- Romain Francoise <rfrancoise@debian.org> Sat, 16 Apr 2011 19:16:23 +0200
tmux (1.3-1) unstable; urgency=low
Due to an update in the server protocol from version 5 to version 6
users need to terminate open tmux sessions before proceeding with
updating tmux 1.2 or older.
-- Karl Ferdinand Ebert <kfebert@gmail.com> Fri, 23 Jul 2010 08:09:03 +0200
|
