Re: Stanislav Sinyagin 2010-02-23 <ac352a801002231154s6ea7c4c7r4275ed54b4f50...@mail.gmail.com> > here's the upstream software maintainer. Torrus is incompatible with > apache2-mpm-worker: Multithreading in Apache causes Torrus database > corruption. > > The package must depend on apache2-mpm-prefork > > The fix has been tested, and the system runs stable since two weeks.
Re: Marc Haber 2010-03-05 <e1nnsfk-00068t...@alioth.debian.org>
> --- trunk/debian/control 2010-03-05 08:11:05 UTC (rev 131)
> +++ trunk/debian/control 2010-03-05 08:13:39 UTC (rev 132)
> -Depends: torrus-common (= ${source:Version}), apache2-mpm-worker | apache2,
> libapache2-mod-perl2 (>= 2.0.0), libapache2-request-perl (>= 2.05-dev-6)
> +Depends: torrus-common (= ${source:Version}), apache2-mpm-prefork | apache2,
> libapache2-mod-perl2 (>= 2.0.0), libapache2-request-perl (>= 2.05-dev-6)
> +Conflicts: apache2-mpm-worker
Hi,
is that the right fix? There are two other MPMs, namely
apache2-mpm-event and apache2-mpm-itk in Debian. If Torrus is only
incompatible with -worker, I agree, but what about the others?
PHP does it like that:
Package: libapache2-mod-php5
Depends: [...] apache2-mpm-prefork (>> 2.0.52) | apache2-mpm-itk
Depending on what the problem internally is, an "include" list of MPMs
would probably be better on the safe side.
Christoph
--
c...@df7cb.de | http://www.df7cb.de/
signature.asc
Description: Digital signature
