After an update of tmuxinator, it started failing saying that it couldn't find the erubis
gem, which I did have installed. Turns out the erubis
gem was located in /usr/lib/ruby/gems/2.5.0
while my GEM_PATH
only included /usr/lib/ruby/gems/2.6.0
. I'm not sure how one would solve this, but as a temporary fix you can just add the line export GEM_PATH="$GEM_PATH:/usr/lib/ruby/gems/2.5.0"
to your .bashrc
or whatever shell rc file you have.
Search Criteria
Package Details: tmuxinator 3.3.4-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/tmuxinator.git (read-only, click to copy) |
---|---|
Package Base: | tmuxinator |
Description: | Manage complex tmux sessions easily |
Upstream URL: | https://github.com/aziz/tmuxinator |
Licenses: | MIT |
Submitter: | lucacesari |
Maintainer: | fryfrog (flipee) |
Last Packager: | fryfrog |
Votes: | 76 |
Popularity: | 0.000851 |
First Submitted: | 2013-06-26 07:49 (UTC) |
Last Updated: | 2025-03-24 20:43 (UTC) |
Dependencies (7)
- ruby
- ruby-erb
- ruby-erubi
- ruby-thor
- ruby-xdgAUR
- ruby-bundler (make)
- zsh-completions (zsh-completions-gitAUR) (optional) – for ZSH completion
Required by (1)
- tdrop-git (optional)
Sources (2)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 Next › Last »
deathsbreed commented on 2019-01-14 12:05 (UTC)
marceljoseph commented on 2018-11-13 23:01 (UTC)
Is it possible to add the completion plugins to ~/.bin
as stated in the readme upstream?
asermax commented on 2018-10-21 00:10 (UTC) (edited on 2018-10-21 00:13 (UTC) by asermax)
@slav if you want to disable the message until the mantainer's update their code, you can go into /usr/lib/ruby/gems/2.5.0/gems/tmuxinator-0.12.0/lib and modify the tmuxinator.rb file to include 2.8 as a valid version.
@deathsbreed you could auto apply that change through a patch on the PKGBUILD, but it's probably more work than it's worth, it's probably gonna get update soon anyways :P
slav commented on 2018-10-19 19:57 (UTC) (edited on 2018-10-19 20:00 (UTC) by slav)
@deathsbreed Thanks for letting know. Yes I ignore it. I just would like to report that it happen after Tmux upgrade to last version.
deathsbreed commented on 2018-10-19 08:47 (UTC)
slav, this happen because of how tmuxinator is written. They have it programmed to recognize deprecation, but only by comparing it to a list of supported version strings instead of trying to see if the version of tmux is later than v1.5. I'd say you should simply ignore it until tmuxinator updates itself. There might also be an option to omit that message, but I am not aware of it.
slav commented on 2018-10-17 20:10 (UTC)
Hi,
After last update to tmux v2.8 unfortunately come everytime below message before running tmuxinator:
DEPRECATION: You are running tmuxinator with an unsupported version of tmux. Please consider using a supported version: (1.5, 1.6, 1.7, 1.8, 1.9, 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7)
Pinned Comments
FrederickZh commented on 2021-04-15 13:37 (UTC)
@lewiji You need to rebuild AUR ruby gems after major ruby upgrades:
paru -Qqo /usr/lib/ruby/gems/2.7.0 | paru -S -- -