I'm not sure it's correct to do this for stable releases - at least not separately from the bash-completion update. The bash-completion update was submitted only for Rawhide. If we drop the completion from tmux but don't ship the new bash-completion for stable releases, we've lost the completion entirely.
If we're going to do this, there should be one combined update with both the tmux update that drops the completion and the bash-completion update that adds it there. Please co-ordinate with @svashisht on this. If svashisht does not intend to ship the new bash-completion to stable releases, this update should be revoked.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update has been submitted for testing by filiperosset.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'passed'.
This update has been pushed to testing.
I'm not sure it's correct to do this for stable releases - at least not separately from the bash-completion update. The bash-completion update was submitted only for Rawhide. If we drop the completion from tmux but don't ship the new bash-completion for stable releases, we've lost the completion entirely.
If we're going to do this, there should be one combined update with both the tmux update that drops the completion and the bash-completion update that adds it there. Please co-ordinate with @svashisht on this. If svashisht does not intend to ship the new bash-completion to stable releases, this update should be revoked.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
This update has been unpushed.