Bug 224781 - file collisions between www-servers/cherokee-0.7.0 and www-servers/lighttpd-1.4.19-r2
|
Bug#:
224781
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: qa@gentoo.org
|
Reported By: gapon@nano.cz
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: file collisions between www-servers/cherokee-0.7.0 and www-servers/lighttpd-1.4.19-r2
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2008-06-03 16:24 0000
|
* package www-servers/cherokee-0.7.0 NOT merged
*
* Detected file collision(s):
*
* /var/www/localhost/htdocs/index.html
* /usr/bin/spawn-fcgi
* /usr/share/man/man1/spawn-fcgi.1.bz2
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* www-servers/lighttpd-1.4.19-r2
* /usr/bin/spawn-fcgi
* /usr/share/man/man1/spawn-fcgi.1.bz2
Reproducible: Always
* CC'ing bass for cherokee, www-servers for both.
* Assigning to qa. Tell me if that isn't alright.
cherokee ships a patched version of lighty's spawn-fcgi. We could try to make
spawn-fcgi an independent package again and patch in the additional features of
cherokee based on a USE flag. Or we could introduce a "spawn-fcgi" USE flag for
both lighty and cherokee and die in the ebuild if the other web server was
installed with USE=spawn-fcgi as well. Any ideas?
hoffie: yeah, others have requested such a change as well. lighty's spawn-fcgi
is quite popular. also the problems surrounding its startup script could be
solved as well.
*** Bug 248486 has been marked as a duplicate of this bug. ***
Same collision on www-servers/cherokee-0.98.1
* Detected file collision(s):
*
* /usr/share/man/man1/spawn-fcgi.1.bz2
* /usr/bin/spawn-fcgi
*
* Searching all installed packages for file collisions...
*
* Press Ctrl-C to Stop
*
* www-servers/lighttpd-1.4.20
* /usr/bin/spawn-fcgi
* /usr/share/man/man1/spawn-fcgi.1.bz2
*
* Package 'www-servers/cherokee-0.98.1' NOT merged due to file
* collisions. If necessary, refer to your elog messages for the whole
* content of the above message.
does cherokee just use spawn-fcgi from lighttpd, or does it include local
changes? if so, the cherokee package should probably install spawn-fcgi as
cherokee-spawn-fcgi or similar.
if not, we should create a spawn-fcgi package, which installs spawn-fcgi from
lighttpd (or possibly cherokee).
As there has been no proper resolution for now, I added blockers so that users
will at least be notified before the build instead after it fails.
this is fixed for cherokee-0.99.8
only affected version left is cherokee-0.98.1 (as well as all versions of
lighttpd)
this is fixed. recent versions of cherokee dont install the spawn-fcgi binary
anymore. the only version left still block lighttpd...
the next version of lighttpd will likewise cease to install the spawn-fcgi
binary - its progess is being tracked at bug #260174. meanwhile the block is
still in effect.
thanks for the reports.