[request-tracker-maintainers] Bug#518692: Bug#518692: request-tracker3.8: Fails to start if request-tracker3.6 is also installed
andrew at etc.gen.nz
Mon Mar 9 19:57:21 UTC 2009
On Mon, 2009-03-09 at 17:47 +0000, Dominic Hargreaves wrote:
> On Sun, Mar 08, 2009 at 02:06:59PM +1300, Andrew Ruthven wrote:
> > If request-tracker3.6 is installed then the RT::Config from rt3.6 is
> > loaded by mistake. This causes major fail.
> > In our case apache2 wouldn't start because of it. This is the error
> > message in the Apache2 error.log file:
> > [Sun Mar 08 11:01:36 2009] [error] Can't locate object method "Config" via packa
> > ge "RT" at /usr/share/request-tracker3.8/libexec/webmux.pl line 100.\nBEGIN fail
> > ed--compilation aborted at /usr/share/request-tracker3.8/libexec/webmux.pl line
> > 102.\nCompilation failed in require at (eval 243) line 1.\n
> > Cheers!
> I'm guessing that this is because somewhere in the Apache configuration
> you are already PerlRequire'ing
> /usr/share/request-tracker3.6/libexec/webmux.pl which is in turn pushing
> /usr/share/request-tracker3.6/lib onto @INC.
You are correct, there was.
> We could add a note in the READMEs that you shouldn't do this, but I
> don't think there's anything we could change in the package to stop this
> being a problem (which is a shame, because I suspect that it'll a common
I don't think that'll necessarily help, since there are multiple
versions of the package in the repository it is a natural assumption
that you can use multiple versions. Perhaps webmux.pl needs to have
versioned depends on the RT and RT::Config modules? If it gets the
wrong version then it can abort with a suitable error message? Rather
than just dying.
> The rt3.8-apache2 package provides not only modperl2 configuration but
> also fastcgi and speedycgi, which *can* be used in parallel with
> multiple versions
> If that wasn't the case, I'd consider Conflicts: rt3.6-apache2, but
> even that would only be a clue as to where the problem was since the
> conffile could still be there, being included by mistake.
> Have I missed anything?
I don't think conflicting with rt3.6-apache2 would help in this case,
it'd need to conflict with request-tracker3.6 to remove the modules that
are causing issues.
Andrew Ruthven, Wellington, New Zealand
At home: andrew at etc.gen.nz | linux.conf.au 2010
| Follow the signs. Visit Wellington!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: This is a digitally signed message part
Url : http://lists.alioth.debian.org/pipermail/pkg-request-tracker-maintainers/attachments/20090310/6f781716/attachment.pgp
More information about the pkg-request-tracker-maintainers