Bug 485518 - Cherokee should not pull Lighttpd as dependency
Summary: Cherokee should not pull Lighttpd as dependency
Alias: None
Product: Fedora
Classification: Fedora
Component: cherokee
Version: 10
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Pavel Lisý
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2009-02-13 21:19 UTC by Paul Lange
Modified: 2009-02-16 22:02 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2009-02-16 22:02:06 UTC

Attachments (Terms of Use)

Description Paul Lange 2009-02-13 21:19:04 UTC
Description of problem:

When I try to install Cherokee on F10 it pulls 3 more dependencies:
* lighttpd
* lighttpd-fastcgi
* spawn-fcgi

I'm not an expert on this but as far as I know lighttpd is a completely different webserver and should not be pulled.

Comment 1 Pavel Lisý 2009-02-15 17:20:56 UTC
Cherokee uses in source tarbal code from lighttpd source 
(/usr/bin/spawn-fcgi, /usr/share/man/man1/spawn-fcgi.1.gz)

This have made conflict between these two packages (see https://bugzilla.redhat.com/show_bug.cgi?id=472749 and https://bugzilla.redhat.com/show_bug.cgi?id=472747)
and was solved by using spawn-fcgi from lighttpd-fastcgi package. 

We can make lighttpd-fastcgi independent on lighttpd but this is more for lighttpd bugzilla record.

Do you have better solution?

Comment 2 Paul Lange 2009-02-15 20:25:24 UTC
I don't have much knowledge on how to handle such problems. I was only a bit surprised that yum pulls lighttpd when I tried to install cherokee.

So maybe it's the best solution to make lighttpd-fastcgi independent from lighttpd as you said.

Comment 3 Pavel Lisý 2009-02-16 10:59:51 UTC
I've made next research and this is result. 
This bug was solved already (it depends on spawn-fcgi only) but new rpm wasn't pushed to update yet. 

I have made update request in bodhi, see

I am not sure how quick it will be in stable update. You can maybe increase karma for that packages. 

Can I close this bug now?

Comment 4 Paul Lange 2009-02-16 20:54:14 UTC
It's already in stable.

This solves this bug. Thank you!

Note You need to log in before you can comment on or make changes to this bug.