You are not logged in.
I'm currently attempting to build mastodon, but am hitting an issue with ruby-bundler. I have ruby-bundler-2.7.2 installed, but running bundle --version returns 2.7.1 which blows up the mastodon build.
[root@bslxenvy64 tmp]# pacman -U ruby-bundler-2.7.2-1-any.pkg.tar.zst
loading packages...
warning: ruby-bundler-2.7.2-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) ruby-bundler-2.7.2-1
Total Installed Size: 1.66 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n]
(1/1) checking keys in keyring [#####################################################################] 100%
(1/1) checking package integrity [#####################################################################] 100%
(1/1) loading package files [#####################################################################] 100%
(1/1) checking for file conflicts [#####################################################################] 100%
(1/1) checking available disk space [#####################################################################] 100%
:: Processing package changes...
(1/1) reinstalling ruby-bundler [#####################################################################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Refreshing PackageKit...
[root@bslxenvy64 tmp]# bundle --version
Bundler version 2.7.1
==> Starting build()...
Fetching https://github.com/mastodon/webpush.git
Fetching gem metadata from https://rubygems.org/........
The running version of Bundler (2.7.1) does not match the version of the specification installed for it (2.7.2). This can be caused by reinstalling Ruby without removing previous
installation, leaving around an upgraded default version of Bundler. Reinstalling Ruby from scratch should fix the problem.
==> ERROR: A failure occurred in build().
Aborting...
Is there some reason bundle is returning the wrong version???
Last edited by jghodd (2025-09-27 18:03:23)
Offline
What does `type -a bundle` show?
Online
[root@bslxenvy64 tmp]# type -a bundle
bundle is /bin/bundle
bundle is /usr/bin/bundle
[root@bslxenvy64 tmp]# /usr/bin/bundle --version
Bundler version 2.7.1
[root@bslxenvy64 tmp]# /bin/bundle --version
Bundler version 2.7.1
Offline
/bin should be a symlink to usr/bin, and should NOT be in your PATH. It's caused some strange issues, but not this one.
This is going to have to be someone who knows ruby, as /usr/lib/bundle is a ruby script and I don't know enough to know where it's pulling the old version from.
Online
well, I don't see any way that the missing symlink is causing this issue. /usr/bin/bundle produces the same version error. They could be hard-linked...
yeah, it might have to be someone who knows ruby. I don't. So, I guess I wait for a ruby developer to come along...?
Offline
$ pacman -Qi ruby-bundler
Name : ruby-bundler
Version : 2.7.2-1
Description : Manages an application's dependencies through its entire life,
across many machines, systematically and repeatably
Architecture : any
URL : https://bundler.io
Licenses : MIT
Groups : None
Provides : None
Depends On : ruby
Optional Deps : None
Required By : None
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 1704.33 KiB
Packager : George Rawlinson <grawlinson@archlinux.org>
Build Date : Thu 11 Sep 2025 07:53:21 UTC
Install Date : Thu 25 Sep 2025 16:58:22 UTC
Install Reason : Explicitly installed
Install Script : No
Validated By : Signature
$ bundler --version
Bundler version 2.7.2
$ bundle --version
Bundler version 2.7.2
So works for me.
Offline
[root@bslxenvy64 out]# pacman -Qi ruby-bundler
Name : ruby-bundler
Version : 2.7.2-1
Description : Manages an application's dependencies through its entire life, across many machines, systematically and repeatably
Architecture : any
URL : https://bundler.io
Licenses : MIT
Groups : None
Provides : None
Depends On : ruby
Optional Deps : None
Required By : ruby-default-gems
Optional For : None
Conflicts With : None
Replaces : None
Installed Size : 1704.33 KiB
Packager : George Rawlinson <grawlinson@archlinux.org>
Build Date : Thu 11 Sep 2025 03:53:21 AM EDT
Install Date : Thu 25 Sep 2025 12:37:32 PM EDT
Install Reason : Installed as a dependency for another package
Install Script : No
Validated By : None
[root@bslxenvy64 out]# bundler --version
Bundler version 2.7.1
[root@bslxenvy64 out]# bundler --version
Bundler version 2.7.1
But not for me
Offline
$ pacman -Qkk ruby-bundler
If that shows nothing, if you create a new user can you reproduce the issue with that user?
Offline
That gives me:
$ pacman -Qkk ruby-bundler
ruby-bundler: 515 total files, 0 altered files
I have no idea what that means, not being a ruby developer.
Offline
pacman.8.en QUERY OPTIONS (APPLY TO -Q)
-k, --check
Check that all files owned by the given package(s) are present on the system. If packages are not specified or filter flags are not provided, check all installed packages. Specifying this option twice will perform more detailed file checking (including permissions, file sizes, and modification times) for packages that contain the needed mtree file.
Edit:
No altered files means that is not the cause. What about with the new user?
Last edited by loqs (2025-09-25 21:31:19)
Offline
This isn't a package issue or anything like that. The 'bundle' script just loads the gem, so there's something wrong in the ruby environment that there is an older gem taking priority. We see this kind of thing with python when people use pip or leave a venv/pyenv active. So this is about knowing where to look for that kind of thing with ruby.
Online
This isn't a package issue or anything like that.
bundle-2.7.2 returns wrong version 2.7.1 #8991
The 'bundle' script just loads the gem
`pacman -Qkk ruby-bundler` confirmed /usr/bin/bundle has not been modified.
So this is about knowing where to look for that kind of thing with ruby.
Could be `GEM_PATH` `GEM_HOME` `RUBYLIB` switching to the new user was intended to remove such settings.
Last edited by loqs (2025-09-25 23:12:13)
Offline
gem install bundler
It'd be nice if this was done in the post_install script. Not everyone who needs and uses ruby is a ruby developer. And this, it seems to me, is something only a ruby developer would know.
Offline
gem install bundler
Your solution is to keep mixing ruby provided by pacman and provided by gem?
Offline
Yeah, this is what CAUSED the problem in the first place, and will cause problems again on the next update.
Online