Summary: | www-servers/nginx-unit: ruby plugin upgrade? | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Anton Bolshakov <anton.bugs> |
Component: | Current packages | Assignee: | Gentoo Ruby Team <ruby> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | CC: | gentoo, proxy-maint, sam |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
See Also: | https://bugs.gentoo.org/show_bug.cgi?id=687762 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Anton Bolshakov
2021-10-18 04:25:00 UTC
The dependency needs to be fixed, I think:
>dev-lang/ruby:*
>dev-ruby/rubygems:*
That first one needs to become := to be rebuilt.
(In reply to Sam James from comment #1) > The dependency needs to be fixed, I think: > >dev-lang/ruby:* > >dev-ruby/rubygems:* > > That first one needs to become := to be rebuilt. (and/or use some ruby eclass) The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=75bb38fbd309593497e946c222c2a8359eb1daf7 commit 75bb38fbd309593497e946c222c2a8359eb1daf7 Author: Mike Pagano <mpagano@gentoo.org> AuthorDate: 2021-10-18 16:28:05 +0000 Commit: Mike Pagano <mpagano@gentoo.org> CommitDate: 2021-10-18 16:28:05 +0000 www-servers/nginx-unit: Rebuild with new ruby when detected Closes: https://bugs.gentoo.org/818769 Package-Manager: Portage-3.0.20, Repoman-3.0.3 Signed-off-by: Mike Pagano <mpagano@gentoo.org> www-servers/nginx-unit/nginx-unit-1.25.0-r2.ebuild | 91 ++++++++++++++++++++++ 1 file changed, 91 insertions(+) I haven't tried the fix, but pretty sure it won't work. The ruby is slotted, it could be two versions of ruby in the system. Ideally, it should be two binaries provided by nginx-unit for both versions (if any). As a workaround, you could introduce USE_RUBY, but again, it won't handle ruby slots. Also, a similar problem was solved in the following bug: https://bugs.gentoo.org/687762 FYI. Regards, Anton (In reply to Anton Bolshakov from comment #4) > I haven't tried the fix, but pretty sure it won't work. I think it's possible it may not work how one would expect, but := guarantees it'll get rebuilt if a new slot appears. The issue is that you can't _pick which_ right now. Please do try it and let us know. Not disagreeing because I think a ruby eclass solution may be needed here (but not sure if the right one exists for this). Just an idea: Use 'ruby-single' eclass, detect ruby using 'ruby_get_use_implementations' (see bug #687762) and specify a correct ruby module in the configure script: ./configure ruby --help --ruby=FILE set ruby executable, default: ruby --module=NAME set unit ruby module name Something like --ruby=/usr/bin/ruby27 --module=ruby27. Ruby project, if you think this can be fixed in the eclass, please review. Otherwise feel free to close FYI, it might be possible to fix it using app-alternatives. Currently, ruby27 and ruby30 are both enabled by default. So the server would stop working if user would switch to ruby30. |