Hi
Has anyone got rt going of Debian - Sarge. I am using apache2 and
compiling from soure and including modules:
so
mod_perl
mod_rewrite
mod_actions
mod_ssl
the error I get is:
[Sat Jan 01 22:00:55 2005] [error] Can’t load Perl module RT::Mason for
server www.triumph2004.com:0, exiting…
Regards
Chris
Chris Robinson
Sent: Sunday, January 02, 2005 11:14 AMHas anyone got rt going of Debian - Sarge. I am using apache2 and
compiling from soure and including modules:
Yes, and I’m sure not the only one. there’re debian packages available
running right away from “apt-get install request-tracker3” but I use
apache 1.3 not apache2;
might be at least a point to start… I remember there were some problems
with apache2.
Michael
Hi All,
-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf
Of Michael Markstaller
Sent: Monday, 3 January 2005 19:34Chris Robinson
Sent: Sunday, January 02, 2005 11:14 AMHas anyone got rt going of Debian - Sarge. I am
using apache2 and compiling from soure and
including modules:Yes, and I’m sure not the only one. there’re debian
packages available running right away from “apt-get
install request-tracker3” but I use apache 1.3 not
apache2; might be at least a point to start… I
remember there were some problems with apache2.
Joel Johnson pointed out to me earlier that there’s a
“request-tracker3.2” package for Sarge that would be more appropriate.
At least until 3.4 gets released, that is. 
Personally, I’m waiting for the 3.4 package as I’m in no mad rush to
implement RT here just yet. If the RT 3.4 package is in RC stage, I’m
happy to wait until it is released before installing here. I can see
RT being a useful tool for us. (Eventum is the other package I am
considering.)
Regards,
Hilton Travis Phone: +61 (0)7 3344 3889
(Brisbane, Australia) Phone: +61 (0)419 792 394
Manager, Quark IT http://www.quarkit.com.au
Quark AudioVisual http://www.quarkav.net
http://www.threatcode.com/ ← its now time to shame poor coders
into writing code that is acceptable for use on today’s networks
War doesn’t determine who is right. War determines who is left.
This document and any attachments are for the intended recipient
only. It may contain confidential, privileged or copyright
material which must not be disclosed or distributed.
Yes, and I’m sure not the only one. there’re debian
packages available running right away from “apt-get
install request-tracker3” but I use apache 1.3 not
apache2; might be at least a point to start… I
remember there were some problems with apache2.Joel Johnson pointed out to me earlier that there’s a
“request-tracker3.2” package for Sarge that would be more appropriate.
At least until 3.4 gets released, that is.
request-tracker3.2 is only in unstable/sid, not testing/sarge, though.
I have successfully installed the request-tracker3 package (RT 3.0.12)
on debian sarge using the regular (1.3) apache package. The install
was smoother than installing RT from source, which I have done a few
times on Mac OS X. That being said, it seems that the debian install
could be automated a bit more (but maybe there are good reasons why it
hasn’t been?)
I’d be psyched to use request-tracker3.2, but I’d rather wait until it
is in sarge.
The official package dependencies at debian.org indicate that
request-tracker3 can use either apache or apache2, but
request-tracker3.2 doesn’t show the optional apache2 dependency for
some reason.
Kevin Murphy
P.S. Thanks to the RT Debian package, I just received an e-mail from
my home RT instance indicating that my wife says it’s time for an oil
change. Oh, yes, and the back door bell needs installing. 
Yes, and I’m sure not the only one. there’re debian
packages available running right away from “apt-get
install request-tracker3” but I use apache 1.3 not
apache2; might be at least a point to start… I
remember there were some problems with apache2.
I am not aware of there being any problems with apache2 currently.
Joel Johnson pointed out to me earlier that there’s a
“request-tracker3.2” package for Sarge that would be more appropriate.
At least until 3.4 gets released, that is.request-tracker3.2 is only in unstable/sid, not testing/sarge, though.
It is very easy to take the request-tracker3.2 package from sid and
put it onto a sarge box if you wish. All the dependencies will be
satisfied, you will just need to install rt3.2-clients along with it
using dpkg.
I have successfully installed the request-tracker3 package (RT 3.0.12)
on debian sarge using the regular (1.3) apache package. The install
was smoother than installing RT from source, which I have done a few
times on Mac OS X. That being said, it seems that the debian install
could be automated a bit more (but maybe there are good reasons why it
hasn’t been?)
The main reason the install/config process has not been more automated
with something like debconf is a lack of spare time. It’s not too hard
to write a debconf script, it’s harder to write a good one that doesn’t
break anyone’s system.
I’d be psyched to use request-tracker3.2, but I’d rather wait until it
is in sarge.
My current plan is that request-tracker3.2 will never go into
Sarge. Once RT3.4 is out I will package and upload that and aim for
RT3.2 to be removed completely from the archive. There will be a
smooth upgrade path from 3.0 to 3.4 provided. That way I will still
only be maintaining two packages.
The official package dependencies at debian.org indicate that
request-tracker3 can use either apache or apache2, but
request-tracker3.2 doesn’t show the optional apache2 dependency for
some reason.
The request-tracker3 package depends on “apache | httpd” and apache2
satisfies the virtual package ‘httpd’ part. request-tracker3 is more
explicit about its dependencies.
Stephen
signature.asc (189 Bytes)