Bug#479501: [pkg-lighttpd] Bug#479501: file conflicts between packages
On Mon, May 05, 2008 at 07:22:17AM +, Michael Ablassmeier wrote:
Package: cherokee, lighttpd
Severity: serious
Justification: policy violation
hi,
both cherokee and lighttpd ship
`/usr/share/man/man1/spawn-fcgi.1.gz'
but do neither conflict, nor add a diversion, thus fail to be installed in the
same environment:
Unpacking lighttpd (from .../lighttpd_1.4.19-2_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/lighttpd_1.4.19-2_amd64.deb
(--unpack):
trying to overwrite `/usr/share/man/man1/spawn-fcgi.1.gz', which is also
in package cherokee
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/lighttpd_1.4.19-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
bye,
- michael
Hmm for all I can see, both spawn-fcgi seem to come from the very
same implementation, they are totally compatible wrt arguments on the
CLI, and their usage is almost the same (except for version and
copyright informations, which suggest abuse from one of both binaries,
if not both, but that's not the question here).
Given that, I assume alternative is the best way to deal with this,
and cherokee's man page is better, so I'd suggest the cherokee
spawn-fcgi{,.1.gz} to be the highest priority.
Gunnar: If you agree, I'll fix that in a lighttpd 1.4.19-3 upload, so
you'd have to conflict with lighttpd 1.4.19-3 and I'll probably have
to conflict with cherokee 0.6.1-2 so that one is forced to migrate to
a package that uses alternatives before trying to coinstall.
Cheers,
--
·O· Pierre Habouzit
··O[EMAIL PROTECTED]
OOOhttp://www.madism.org
pgpr9aCwe6dvp.pgp
Description: PGP signature
Bug#479501: [pkg-lighttpd] Bug#479501: file conflicts between packages
Pierre, I am certain that spawn-fcgi comes from the Lighttpd team. Also
check out this source snippet from the cherokee:
http://svn.cherokee-project.com/browser/cherokee/trunk/contrib/spawn-fcgi.c
* File borrowed from lighttpd. I have only cleaned up the headers
* inclusion mess. Its original license follows:
*Alvaro Lopez Ortega [EMAIL PROTECTED]
So given that it's really from Lighttpd, and that it's likely that
future version will come from Lighttpd as well, not cherokee, shouldn't
we give Lighttpd priority?
Pierre Habouzit wrote:
On Mon, May 05, 2008 at 07:22:17AM +, Michael Ablassmeier wrote:
Package: cherokee, lighttpd
Severity: serious
Justification: policy violation
hi,
both cherokee and lighttpd ship
`/usr/share/man/man1/spawn-fcgi.1.gz'
but do neither conflict, nor add a diversion, thus fail to be installed in the
same environment:
Unpacking lighttpd (from .../lighttpd_1.4.19-2_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/lighttpd_1.4.19-2_amd64.deb
(--unpack):
trying to overwrite `/usr/share/man/man1/spawn-fcgi.1.gz', which is also in
package cherokee
Processing triggers for man-db ...
Errors were encountered while processing:
/var/cache/apt/archives/lighttpd_1.4.19-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
bye,
- michael
Hmm for all I can see, both spawn-fcgi seem to come from the very
same implementation, they are totally compatible wrt arguments on the
CLI, and their usage is almost the same (except for version and
copyright informations, which suggest abuse from one of both binaries,
if not both, but that's not the question here).
Given that, I assume alternative is the best way to deal with this,
and cherokee's man page is better, so I'd suggest the cherokee
spawn-fcgi{,.1.gz} to be the highest priority.
Gunnar: If you agree, I'll fix that in a lighttpd 1.4.19-3 upload, so
you'd have to conflict with lighttpd 1.4.19-3 and I'll probably have
to conflict with cherokee 0.6.1-2 so that one is forced to migrate to
a package that uses alternatives before trying to coinstall.
Cheers,
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479501: [pkg-lighttpd] Bug#479501: file conflicts between packages
On Mon, May 05, 2008 at 10:44:54AM +, Alexander Turcic wrote: Pierre, I am certain that spawn-fcgi comes from the Lighttpd team. Also check out this source snippet from the cherokee: http://svn.cherokee-project.com/browser/cherokee/trunk/contrib/spawn-fcgi.c * File borrowed from lighttpd. I have only cleaned up the headers * inclusion mess. Its original license follows: *Alvaro Lopez Ortega [EMAIL PROTECTED] So given that it's really from Lighttpd, and that it's likely that future version will come from Lighttpd as well, not cherokee, shouldn't we give Lighttpd priority? Well so maybe I'll take gunnar's manual page then :) Anyways, I don't care much. I'll use a priority of 20, the cherokee maintainer can use whatever he thinks is best. -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpt2BBqRUNVe.pgp Description: PGP signature
Bug#479501: [pkg-lighttpd] Bug#479501: file conflicts between packages
Pierre Habouzit dijo [Mon, May 05, 2008 at 03:44:15PM +0200]: So given that it's really from Lighttpd, and that it's likely that future version will come from Lighttpd as well, not cherokee, shouldn't we give Lighttpd priority? Well so maybe I'll take gunnar's manual page then :) Glad to be of use Anyways, I don't care much. I'll use a priority of 20, the cherokee maintainer can use whatever he thinks is best. FWIW, I think we can set them even at the same level. I'll put mine a bit lower than yours - say, 15. I'll prepare and upload soon - I want to check another bug with the same upload. -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#479501: [pkg-lighttpd] Bug#479501: file conflicts between packages
Pierre Habouzit dijo [Mon, May 05, 2008 at 03:44:15PM +0200]: So given that it's really from Lighttpd, and that it's likely that future version will come from Lighttpd as well, not cherokee, shouldn't we give Lighttpd priority? Well so maybe I'll take gunnar's manual page then :) Anyways, I don't care much. I'll use a priority of 20, the cherokee maintainer can use whatever he thinks is best. I'm using a slave alternative for the manpage, and I will be shipping both the binary and the manpage as spawn-fcgi.cherokee - Even if the manpage is the same today, nothing guarantees it will stay so. How should we close the bug? In rigor, the bug should be open until we _both_ upload the changed packages... So, should our changelogs refer to this bug, or should we close it manually later? Greetings, -- Gunnar Wolf - [EMAIL PROTECTED] - (+52-55)5623-0154 / 1451-2244 PGP key 1024D/8BB527AF 2001-10-23 Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
