FS#57814 - [tmuxp] "tmux" set as group, which causes odd behaviour in Ansible and seems unnecessary

Attached to Project: Community Packages
Opened by Chris Down (cdown) - Tuesday, 13 March 2018, 04:30 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Tuesday, 13 March 2018, 07:02 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To David Runge (dvzrv)
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

In https://git.archlinux.org/svntogit/community.git/commit/trunk?h=packages/tmuxp&id=11104eb2240f5dda30bec40c3b07ec0f0cb092f9, tmuxp was added verbatim from AUR. However, for some reason this PKGBUILD contains `groups=('tmux')`, which causes odd behaviour with configuration management tools like Ansible, where they detect it as a group and therefore try to install tmuxp instead of tmux, which is weird:

% pacman -Sqg tmux
tmuxp

I've filed a bug with them -- see https://github.com/ansible/ansible/issues/37334 for more information -- but it seems there's no real reason to have a tmux group, especially when it doesn't contain tmux. It would be nice to have a new build without groups=('tmux').
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Tuesday, 13 March 2018, 07:02 GMT
Reason for closing:  Fixed
Additional comments about closing:  tmuxp 1.4.0-2

Loading...