| View previous topic :: View next topic |
| Author |
Message |
Carel
n00b
Joined: 26 Jun 2010
Posts: 18
|
 Posted: Thu Mar 04, 2021 10:57 am Post subject: [SOLVED] Ruby woes and GitlabHQ version bump |
 |
|
I am having trouble upgrading my GitlabHq package. I was a tad slack and left it on version 12.8 or so for a while. The package maintainer changed the e-build structure around version 13.8.2 and one must now install "gitlab" rather then "gitlabhq' going forwards.
My rational is bump the old version from 12.8 to version 13.8.2 on the "old" e-builds and then bump across to the newer structure as the maintainer has instructed within a recent news item. To do this I have unmasked the 13.8.2 version but am having trouble actually installing it. Presently my emerge commands are locked with the following block which I'm not sure how to resolve at this point in time :
| Code: |
emerge: there are no ebuilds to satisfy ">=dev-ruby/net-telnet-0.2.0[ruby_targets_ruby27]".
(dependency required by "dev-lang/ruby-2.7.2::gentoo" [ebuild])
(dependency required by "dev-vcs/gitlab-gitaly-13.8.2::gitlab" [ebuild])
(dependency required by "www-apps/gitlabhq-13.8.2::gitlab" [ebuild])
(dependency required by "@selected" [set])
(dependency required by "@world" [argument])
|
Previously I had set the Ruby version explicitly to `ruby25` and `ruby26` in `make.conf` and I believe I have now limited this to `ruby26`, one is never too certain with ruby. While trying to resolve this I also tried including `ruby27` in the mix to no avail. My `eselect ruby list` currently lists version 2.5 and 2.6 with 2.6 being the system ruby, 2.7 is not mentioned. I can't seem to change the ruby version with out running up against the above block so I figure I'm stuck with 2.6 for now.
My emerge --info is available here https://dpaste.com/GFAS4ZA2Q
If I must furnish any additional information please let me know otherwise if you have a hint as to how to break this block short of removing everything and starting afresh I would be interested to know it. I will try blocking net-telnet-0.2.0 (Supports Ruby 2.4/2.5/2.6/2.7) now quickly, reverting to 0.1.1-r1 (Supports Ruby 2.2/2.3/2.4/2.5), in the hopes that this resolves the issue but I don't think it will; if that fails I will try and intermediate GitbalHq, but I seem to run across the above block no matter what I do for the moment.
Last edited by Carel on Thu Mar 04, 2021 12:16 pm; edited 1 time in total |
|
| Back to top |
|
 |
fedeliallalinea
Administrator
Joined: 08 Mar 2003
Posts: 31267
Location: here
|
| Posted: Thu Mar 04, 2021 11:27 am Post subject: |
|
|
This happens because ruby27 is a masked use flag in a stable system.
You can unmask use flag using /etc/portage/profile/use.mask, but I don't know the situation for ruby27 and if is ready for production.
_________________
Questions are guaranteed in life; Answers aren't. |
|
| Back to top |
|
|
Carel
n00b
Joined: 26 Jun 2010
Posts: 18
|
| Posted: Thu Mar 04, 2021 12:15 pm Post subject: Thanks ! |
|
|
@fedeliallalinea Thanks for the help, I added the following line to `/etc/portage/profile/use.stable.mask` and unblocked `dev-ruby/net-telnet-0.2.0`. Portage was only happy to proceed again once these amendments were made.
| Code: |
-ruby_targets_ruby27
|
My mistake was assuming that Ruby 3.0 should be considered unstable; and that I had better bump to Ruby 2.7 once I had a working system again. I had enabled ruby_25/26/27 all over my `package.accept_keywords|use` files to no avail.
Interested parties reading my original post might need to know that rolling back to `dev-ruby/net-telnet-0.1.1-r1` simply returned the same error after portage asked me to enable a bunch of Ruby25/27 flags. I didn't manage to try an intermediate GitlabHQ version in the interim.
Thanks once again @fedeliallalinea |
|
| Back to top |
|
|
|
Portage & Programming
