/usr/bin/spawn-fcgi -n -s /run/fastcgi-graph.sock-1 -P /run/spawn-fcgi/munin-cgi-graph-1.pid -u munin -g nginx -M 660 -- /usr/libexec/munin/cgi/munin-cgi-graph Can't locate CGI/Fast.pm in @INC (you may need to install the CGI::Fast module) (@INC contains: /etc/perl /usr/local/lib64/perl5/5.22.0/x86_64-linux-thread-multi /usr/local/lib64/perl5/5.22.0 /usr/lib64/perl5/vendor_perl/5.22.0/x86_64-linux-thread-multi /usr/lib64/perl5/vendor_perl/5.22.0 /usr/lib64/perl5/5.22.0/x86_64-linux-thread-multi /usr/lib64/perl5/5.22.0) at /usr/libexec/munin/cgi/munin-cgi-graph line 36. BEGIN failed--compilation aborted at /usr/libexec/munin/cgi/munin-cgi-graph line 36. Please add missing dependency for cgi usage
Side note: this should probably be a dependency only for >=perl-5.22, (stable) 5.20 has core CGI support (working fine with munin 2.0.25)
@perl, could you please give advice?
I don't consider "FastCGI" and "CGI" the same thing really. Having 'cgi' imply FastCGI is just weird. However, the script "munin-cgi-graph" has an unconditional dependency on CGI::Fast. Thus, anywhere that script is being even *installed*, the CGI::Fast dependency should also be. And people who don't want CGI::Fast installed shouldn't get the bin script. Grepping the source tree also indicates there is no dependency on FCGI.pm, even though the ebuild depends on it. Though CGI-Fast depends on FCGI. The extra confusion comes from the fact a CGI::Fast based code can be either run directly as CGI or FastCGI, ( but running it as CGI doesn't absolve it of the dependency requirements ) And CGI::Fast hard-requires FCGI.pm, regardless of whether or not you are using it in a FastCGI context. === Regardless of whether you want cgi support, or fastcgi, you need both FCGI and CGI::Fast installed. Only if you want neither can you avoid those dependencies, *( and in such a case, the scripts requiring either should not be installed )
Other notes: - Upstream appear to be nuking munin-cgi-graph entirely. https://github.com/munin-monitoring/munin/tree/9faec2ef624e56b58b93ea3d022d4b6d56a98fcd All the HTTP stuff is going into https://github.com/munin-monitoring/munin/blob/devel/script/munin-httpd Which uses HTTP::Server::Simple::CGI This will mean: a) You can daemonize the script directly as an HTTP service b) You can use the script like a CGI-bin somehow As to how you will use that in future with FCGI if you desire it, that part is not clear at all.
Thanks for the long explanation, but how can we solve the current situation? We are missing deps in the ebuild and the munin maintainers need to get a hint when and how to add dev-perl/CGI-Fast.
(In reply to Justin Lecher from comment #5) > We are missing deps in the ebuild and the munin maintainers need to get a > hint when and how to add dev-perl/CGI-Fast. If you are installing munin-cgi-* , then my opinion is: always depend on dev-perl/CGI-Fast If you don't do that, then you will simply be installing things that don't work, and you shouldn't do that.
* commit 6dc75f1006ed62eeadc6916c52f9ff7dd13d4c78 * Author: Justin Lecher <jlec@gentoo.org> * Date: Wed Aug 12 13:17:09 2015 +0200 * * net-analyzer/munin: Add missing dependency, bug #557124 * * Package-Manager: portage-2.2.20.1 * Signed-off-by: Justin Lecher <jlec@gentoo.org>
