Hide Forgot
Latest upstream release: 1.5 Current version in Fedora Rawhide: 1.4 URL: http://sourceforge.net/api/file/index/project-name/tmux/mtime/desc/limit/20/rss Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
Any chance of also pushing updated packages to EPEL 6 (as well as Fedora) - tmux being a leaf package should be upgradeable without disruption, and 1.5 fixes a couple of annoying crasher bugs in 1.4.
(In reply to comment #1) > Any chance of also pushing updated packages to EPEL 6 (as well as Fedora) - > tmux being a leaf package should be upgradeable without disruption, and 1.5 > fixes a couple of annoying crasher bugs in 1.4. Could you please try this EL6 Build and give feedback? http://koji.fedoraproject.org/koji/taskinfo?taskID=3477611 tmux is no longer run as segid tmux now so I'd appreciate some feedback before pushing the update out to f15/f16 and el6 Builds for F16 and F15 are available too: http://koji.fedoraproject.org/koji/buildinfo?buildID=271771 http://koji.fedoraproject.org/koji/buildinfo?buildID=271774 Thanks.
Thanks for the new builds. Well, I've installed the x86_64 package and have been using it for ~ 5 hours today without problem. Was there any particular functionality you were concerned about?
tmux-1.5-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/tmux-1.5-1.fc16
Package tmux-1.5-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing tmux-1.5-1.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-15519 then log in and leave karma (feedback).
tmux-1.5-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.