Arch Linux User Repository

@lewiji You need to rebuild AUR ruby gems after major ruby upgrades: paru -Qqo /usr/lib/ruby/gems/2.7.0 | paru -S -- -

https://archlinux.org/packages/community/any/ruby-thor/ << has been updated to 1.2.1

This means the latest version of tmuxinator works again

I can have a look at ruby-thor soon to see if we can easily update it.

Looks like 3.0.2 depends on ruby-thor 1.2.1, but that hasn't been updated in our repos. Don't update... I guess.

@FrederickZh: Done!

@Artalus It's probably unreasonable to ask people to read all the comments given there are pages, but I mean... my comment was literally the latest comment.

@fryfrog Maybe pin a comment about this?

After update I get the same problem @lewiji had:

$ tmuxinator doctor
/usr/lib/ruby/3.0.0/rubygems/specification.rb:1404:in `rescue in block in activate_dependencies': Could not find 'erubis' (~> 2.6) among 80 total gem(s) (Gem::MissingSpecError)

Apparently, erubis package hasn't updated since 2019 and seems to be installed for ruby 2.6 instead of the 3.0 I got from main repos:

$ pacman -Ql ruby-erubis
ruby-erubis /usr/lib/ruby/gems/2.6.0/gems/erubis-2.7.0/
...

I tried clean reinstall of ruby and tmuxinator, but no success :(

@lewiji You need to rebuild AUR ruby gems after major ruby upgrades: paru -Qqo /usr/lib/ruby/gems/2.7.0 | paru -S -- -

A pacman update earlier today upgraded rubygems and some other gems[^1], which prevented tmuxinator from running with the error:

tmuxinator 'rescue in block in activate_dependencies': Could not find 'erubis' (~> 2.6) among 90 total gem(s) (Gem::MissingSpecError)

Doing yay -R tmuxinator && yay -Sc && yay -S tmuxinator fixed it (ie clean build - there's probably a quicker way to do that)

Not familiar enough with ruby to say what exactly is to blame but maybe the info is helpful.

[1]:

[2021-04-15T11:17:19+0100] [ALPM] upgraded rubygems (3.2.13-1 -> 3.2.15-1)
[2021-04-15T11:17:19+0100] [ALPM] upgraded ruby-reline (0.2.4-1 -> 0.2.5-1)
[2021-04-15T11:17:19+0100] [ALPM] upgraded ruby-irb (1.3.4-1 -> 1.3.5-1)
[2021-04-15T11:17:19+0100] [ALPM] upgraded ruby (2.7.2-1 -> 3.0.1-1)
[2021-04-15T11:17:19+0100] [ALPM] upgraded ruby-dbus (0.15.0-3 -> 0.15.0-4)
[2021-04-15T11:17:19+0100] [ALPM] upgraded ruby-ffi (1.15.0-1 -> 1.15.0-2)
[2021-04-15T11:17:20+0100] [ALPM] upgraded ruby-maruku (0.7.3-5 -> 0.7.3-6)
[2021-04-15T11:17:20+0100] [ALPM] upgraded ruby-rake (13.0.3-1 -> 13.0.3-2)
[2021-04-15T11:17:20+0100] [ALPM] upgraded ruby-rb-fsevent (0.10.4-1 -> 0.10.4-2)
[2021-04-15T11:17:20+0100] [ALPM] upgraded ruby-rb-inotify (0.9.10-4 -> 0.9.10-5)
[2021-04-15T11:17:20+0100] [ALPM] upgraded ruby-rdoc (6.3.0-1 -> 6.3.0-3)
[2021-04-15T11:17:20+0100] [ALPM] upgraded ruby-sass-listen (4.0.0-8 -> 4.0.0-9)
[2021-04-15T11:17:20+0100] [ALPM] upgraded ruby-yard (0.9.26-1 -> 0.9.26-2)
[2021-04-15T11:17:20+0100] [ALPM] upgraded ruby-sass (3.7.4-2 -> 3.7.4-3)
[2021-04-15T11:17:20+0100] [ALPM] upgraded ruby-thor (1.1.0-1 -> 1.1.0-2)

thank you for quick update version!

can we make compatible tmuxinator with last tmux 3.2 version please?

It was unintentional, but let's pretend it was for the reason you said. It doesn't seem worth updating everyone's tmuxinator just for this.

Thanks, but you forgot to increase the pkgrel value. Or was that intended to be only pushed to people on the next update?

Hey @Segaja, it built cleanly in a CHROOT w/o ruby-rdoc so I went ahead and punted it from depends. Thanks for the suggestion.

Why is ruby-rdoc a normal depends here? It isn't listed on https://rubygems.org/gems/tmuxinator .

If it is needed for building of the package then it should be ok to list as a makedepends.

@Ghosthree3 Good catch, thanks. Added as optdepend.

The change causes error: failed to commit transaction (conflicting files) tmuxinator: /usr/share/zsh/site-functions/_tmuxinator exists in filesystem (owned by zsh-completions) for me. Seems zsh-completions already supplies this file.

@Segaja Done. Thanks.

Sorry for the inconvenience, but I recently learned that my information about completions was wrong. Completions should be for ZSH in /usr/share/zsh/site-functions/_${pkgname} and for bash in /usr/share/bash-completion/completions/${pkgname} as you can see in my AUR package for stern: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=stern

Would you be so kind as to move them to these locations in the next update? That way they will work out of the box for these shells.

I'm not a too big expert on ruby structure but I agree that it sounds odd for them to be there.

Btw I also contacted you on IRC. That might make this conversation faster ;)

Awesome, thanks for the details. I'll get them there in the next couple updates. I'm thinking I'll move (instead of copy) them out of the gem folder, seems dumb for them to be there.

Yes I think that is the general idea. It even states so in the wiki for example for the "command_not_found" handler: https://wiki.archlinux.org/index.php/Zsh#The_%22command_not_found%22_handler and https://wiki.archlinux.org/index.php/Bash#Command_not_found

How is one meant to load the completion files, just put it in your .bashrc?

Looking at other packages like fzf and pkgfile it seems the commont place would be /usr/share/<package/completion.zsh but the filename at the end seems to vary and is used to split multiple completion files if there are any.

Obviously this is similar for bash and zsh. fzf has them in the same folder /usr/share/fzf with just different file extensions.

@Segaja: Do you know if there is a correct place to put completion files? I'm still researching, but it seems like /usr/share/bash-completion/completions/ for bash.

Hello, could you please install the completions files ( /usr/lib/ruby/gems/2.7.0/gems/tmuxinator-2.0.1/completion/tmuxinator.{bash,fish,zsh} ) to /usr/share/tmuxinator/cmpletion.{bash,fish,zsh} ?

Can you please update it to v2.0.1? https://github.com/tmuxinator/tmuxinator/releases/tag/v2.0.1

It now supports tmux 3.1b

@solatis Thank you

For completeness, the latest version 1.1.5 was released 3 hours ago: https://github.com/tmuxinator/tmuxinator/releases/tag/v1.1.5

it will be nice to update tmuxinator to highest version because seems like 1.1.4-1 is not compatible with new tmux 3.1 which come out recently

WARNING: You are running tmuxinator with an unsupported version of tmux. Please consider using a supported version: (3.0a, 3.0, 2.9a, 2.9, 2.8, 2.7, 2.6, 2.5, 2.4, 2.3, 2.2, 2.1, 2.0, 1.9, 1.8, 1.7, 1.6, 1.5)

@Pitasi, is the below error what you were solving? I've tried re-installing all the dependencies and then tmuxinator, like you suggest... but it doesn't fix it. But a clean install on another system is fine.

Traceback (most recent call last):
        2: from /usr/bin/tmuxinator:23:in `<main>'
        1: from /usr/lib/ruby/2.7.0/rubygems.rb:294:in `activate_bin_path'
/usr/lib/ruby/2.7.0/rubygems.rb:275:in `find_spec_for_exe': can't find gem tmuxinator (>= 0.a) with executable tmuxinator (Gem::GemNotFoundException)

Edit: Ugh, of course I figure it out after posting. It was just yay re-using the already built package... which was for ruby 2.6.0. Punted it and forced a rebuild and its fine of course.

@Pitasi Thank you mate

This morning it stopped working for me, something about missing gems. The only thing to make it works was to manually reinstall all dependencies (yay -S ruby ruby-erubis ruby-thor 'ruby-xdg>=2.2.5' ruby-rdoc) then reinstall tmuxinator (yay -S tmuxinator).

P.S. apparently it's something known and needed after Ruby updates.

Thank you fixing nice app.

Looks like the upstream fix for now is simply disallowing ruby-thor >= 1.0.0.

I don't code in Ruby but out of curiosity, has Ruby got any mechanism in place to handle bundled/local dependencies?

ruby-thor was updated on 2019/12/23 and is now out-of-spec for this package (well, the upstream gemspec).

Thoughts on a resolution?

Tmuxinator has been updated to version 1.1.3 to support tmux 3.0. Please update.

It is the latest version but still out of date (I flagged it) as it is not up to date with the latest tmux version.

/edit: I just saw the package was flagged again out of date today as the upstream tmuxinator project has released a new version but the package is not out of date.

Only the maintainer can do it.

Is there a way to unflag a package marked out of date? This package was flagged out of date, but is currently the latest version.

Can someone update this? The current version triggers a warning with tmux 2.9, and 1.0.0 has been released.

@archerie Had the same problem. Actually reinstalling package ruby-erubis and whatever package tmuxinator is complaining about (for me there was ruby-xdg too) with pacman did the trick

@cgirard What command could I run to rebuild all ruby-* packages?

@deathsbreed: you should rebuild your ruby-* packages after ruby version update.

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.

Is it possible to add the completion plugins to ~/.bin as stated in the readme upstream?

@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

@deathsbreed Thanks for letting know. Yes I ignore it. I just would like to report that it happen after Tmux upgrade to last version.

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.

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)

ruby-rdoc should be added as a dependency.

Installation of 0.10.1-2 is failing for me. Am I missing a dependency or something?

...
Successfully installed tmuxinator-0.10.1
ERROR:  While executing gem ... (Gem::DocumentError)
    RDoc is not installed: cannot load such file -- rdoc/rdoc
==> ERROR: A failure occurred in package().
    Aborting...
==> ERROR: Makepkg was unable to build tmuxinator.
==> Restart building tmuxinator ? [y/N]

with new version all back to normal with ruby and tmuxinator back to life now thank you!

with new version all back to normal with ruby and tmuxinator back to life now thank you!

Also another error when starting tmuxinator

/usr/lib/ruby/2.5.0/rubygems/dependency.rb:310:in to_specs': Could not find 'xdg' (>= 2.2.3, ~> 2.2) among 33 total gem(s) (Gem::MissingSpecError) Checked in 'GEM_PATH=/home/theuser/.gem/ruby/2.5.0:/usr/lib/ruby/gems/2.5.0', executegem env` for more information

Well there's a new version out but with the same error. Maintainer could you please fix this so we don't need to update the pkgbuild manually?

/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- ubygems (LoadError)

Some hints to build which worked for me on the current ruby version:

• On line 19, add an extra line before the rubygems option:

  local _gemdir="$(ruby -rrubygems -e'puts Gem.default_dir')"

• Add ruby-rdoc to makedepends

or you can try with this https://raw.githubusercontent.com/nycko123/ArchLinux/master/tmuxinator/PKGBUILD . Ruby 2.5.0-2, ruby-thor 0.20.0-2, tmuxinator 0.10.1

There is a working version in the [quarry] repository[1]

[1] https://wiki.archlinux.org/index.php/Unofficial_user_repositories#quarry

Forcibly downgrading ruby to 2.4.3-1 and ruby-thor to 0.20.0-1 and preventing updates has been my strategy, but I might just ditch the AUR package and build from source.

It's been flagged out of date for a weeks already and maintainer doesn't seem to be fixing it so does anyone know a workaround so I can still install this?

Already flagged out-of-date, but just noting the failure I see -- package builds/installs fine, but startup error occurs:

$ tmuxinator
Traceback (most recent call last):
    2: from /bin/tmuxinator:23:in `<main>'
    1: from /usr/lib/ruby/2.5.0/rubygems.rb:308:in `activate_bin_path'
/usr/lib/ruby/2.5.0/rubygems.rb:289:in `find_spec_for_exe': can't find gem tmuxinator (>= 0.a) with executable tmuxinator (Gem::GemNotFoundException)

Versions:

pacman -Q | grep tmuxinator
tmuxinator 0.10.0-2

pacman -Q | grep ruby
ruby 2.5.0-1
ruby-diff-lcs 1.3-2
ruby-erubis 2.7.0-1
ruby-paint 2.0.1-2
ruby-rainbow 3.0.0-2
ruby-rspec 3.7.0-2
ruby-rspec-core 3.7.0-2
ruby-rspec-expectations 3.7.0-2
ruby-rspec-mocks 3.7.0-2
ruby-rspec-support 3.7.0-2
ruby-term-ansicolor 1.4.0-3
ruby-thor 0.20.0-2
ruby-tins 1.13.0-3
ruby-trollop 2.1.2-5
ruby-trollop1 1.16.2-1
ruby-xdg 2.2.3-1

Same here as @deatsbreed

Preparing...

Building ruby-erubis...
(...)

==> Starting package()...
Traceback (most recent call last):
    1: from /usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
/usr/lib/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require': cannot load such file -- ubygems (LoadError)
ERROR:  While executing gem ... (Errno::ENOENT)
    No such file or directory @ dir_s_mkdir - /tmp/pamac-build-szymon/ruby-erubis/pkg/ruby-erubis/usr/bin
==> ERROR: A failure occurred in package().
    Aborting...

Same issue here as @deatsbreed

I recently upgraded this package and ran across an error, someone on #ruby pointed out that there's a typo here. Instead of: local _gemdir="$(ruby -rubygems -e'puts Gem.default_dir')" it should be: local _gemdir="$(ruby -rrubygems -e'puts Gem.default_dir')"

Otherwise it tries looking for a file called ubygems instead of rubygems. This is at least what happens with ruby 2.5.0 for me.