Bug 472749
Summary: | Conflict with cherokee | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Michael Schwendt <bugs.michael> |
Component: | lighttpd | Assignee: | Matthias Saou <matthias> |
Status: | CLOSED NEXTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | el5 | CC: | matthias |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 1.4.20-6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-12-26 14:09:49 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 472747 | ||
Bug Blocks: |
Description
Michael Schwendt
2008-11-24 11:42:19 UTC
From what somebody already wrote in an email to me, apparently cherokee copied the spawn-fcgi helper as-is from lighttpd. We need to decide what to do. I can think of two clean solutions : * Split out the spawn-fcgi in a lighttpd sub-package which can be required by cherokee * Patch both lighttpd and cherokee to have them include their name in the helper's file name I've fixed this in Fedora devel by prefixing the spawn-fastcgi binary and man page with "lighttpd-". This *will* break home made scripts which call spawn-fastcgi, so it's probably not the best fix for EPEL. Thoughts? I'm scared to deploy this change, especially to EPEL. I've put back a "spawn-fastcgi" symlink for now, since the 1.4.20 update is required to fix some security issues. What I would suggest for the long term is to create a "spawn-fastcgi" sub-package (the "-n" type, to not have "lighttpd" in the name) from the lighttpd package, since lighttpd is the upstream for that program, and have cherokee require that, or leave it up to the end users to install it (as it is not mandatory for fastcgi to work anyway). I'll probably make that change in devel once 1.4.20 is deployed. In the end, I've split out the "spawn-fcgi" package on all supported branches, as this is what makes most sense to me. |