Has anyone converted from using the “from tarball” RT to the Debianized
RT package? If so, could you share any gotchas you found along the way,
since I’m considering doing that in the future.
D
| Derek J. Balling | “You can get more with a kind |
| dredd@megacity.org | word and a two-by-four, than |
| www.megacity.org/blog/ | you can with just a kind |
| | word.” - Marcus |
Has anyone converted from using the “from tarball” RT to the Debianized
RT package? If so, could you share any gotchas you found along the way,
since I’m considering doing that in the future.
are you asking about going from tarball of rt to a deb package, for
use on a debian system? I don’t have any experience with it, but that
seems like a bad idea for several reasons.
jesse has a debian package for rt already. (it’s for rt version
2.0.13, and is in unstable and testing. If you try it, make sure
you’re getting jesse’s package and not the older one)
rt is distributed as source, and the build/install process does a
variety of stuff. You’d have to download the source; build;
install to a temp directory; tar the temp directory; and convert
that tar to a deb. even so, you’re deb would lack the various
scripts that get run on make install (stuff like setting up the
database)
Or are you asking about going from the rt deb, to a tarball for
installation on other systems? I’d avoid that as you’d lose
dependencies, and again, all those scripts.
seph
are you asking about going from tarball of rt to a deb package, for
use on a debian system? I don’t have any experience with it, but that
seems like a bad idea for several reasons.
Nononono.
we have RT installed from Jesse’s tarball.
We’d like to migrate to having RT installed from Jesse’s .deb package.[1]
There are (always) various subtle differences in where “the .deb” wants
stuff as opposed to where the default tarball install would have put it.
THOSE are the kind of things I’m looking for.
d
[1] I almost left out “.deb” in that sentence. Why it cracked me up
during the re-read-before-send process is left as an exercise for the
reader.
we have RT installed from Jesse’s tarball.
We’d like to migrate to having RT installed from Jesse’s .deb package.[1]
ah, that makes much more sense. At some point, I expect I’ll want to
do that. So I’m certainly curious about how it goes 
There are (always) various subtle differences in where “the .deb” wants
stuff as opposed to where the default tarball install would have put it.
THOSE are the kind of things I’m looking for.
assuming all your customisations are in the config file, or the local
part of the install directory, I don’t think the difference between
the 2 is important. When I make the switch, I’m planning on backing up
the old rt install (installed from source), rm’ing it, installing the
package, and coping my configs back into place. I expect the locations
will change to /etc/rt, but it should be easy enough to check with
dpkg -L.
good luck, and tell us how it goes
seph
FWIW, based on several rounds of commentary, I’ve got a set of changes
to make to the .deb installation to improve the filesystem layout and to
make the package somewhat easier to use. I’m hoping to get to it within
the next week.
Best,
J
»|« Request Tracker — Best Practical Solutions – Trouble Ticketing. Free.
- jesse has a debian package for rt already. (it’s for rt version
2.0.13, and is in unstable and testing. If you try it, make sure
you’re getting jesse’s package and not the older one)
Correcting myself here: this is false. jesse’s deb’s are for 2.0.14
and aren’t yet in the archive. You almost certainly don’t want to use
these debs.
seph
- jesse has a debian package for rt already. (it’s for rt version
2.0.13, and is in unstable and testing. If you try it, make sure
you’re getting jesse’s package and not the older one)Correcting myself here: this is false. jesse’s deb’s are for 2.0.14
and aren’t yet in the archive. You almost certainly don’t want to use
these debs.
Debian has working packages, in the archive:
Package: request-tracker
Priority: optional
Section: misc
Installed-Size: 2032
Maintainer: Tollef Fog Heen tfheen@debian.org
Architecture: all
Version: 2.0.13-4
Depends: libdbd-pg-perl | libdbd-mysql-perl, libcgi-pm-perl (>=2.56), libdigest-md5-perl, make, perl, apache | httpd, wwwconfig-common, libapache-request-perl, libmime-perl, libapache-session-perl, libdate-manip-perl, libdbix-datasource-perl, libdbix-searchbuilder-perl, libfreezethaw-perl, liblog-dispatch-perl, libtext-template-perl, libtext-wrapper-perl, libtie-ixhash-perl , libparams-validate-perl, libhtml-mason-perl, libmldbm-perl, libapache-mod-perl, libapache-dbi-perl, libdbix-dbschema-perl
Filename: pool/main/r/request-tracker/request-tracker_2.0.13-4_all.deb
Size: 428066
MD5sum: dd1a502d1fe4044455a5283fad1c89f2
Description: Request Tracker, a GPL’d Trouble Ticket System
Request Tracker helps you handle and track problem reports, it features
web interfaces for queue administration and report submitting and sends out
email with replies and comments to those reports.
.
Be sure to read /usr/share/doc/request-tracker/README.Debian for installation
instructions.
John Goerzen jgoerzen@complete.org GPG: 0x8A1D9A1F www.complete.org