[request-tracker-maintainers] [RFR] templates://request-tracker3.8/{templates}
Justin B Rye
jbr at edlug.org.uk
Fri Mar 20 13:44:16 UTC 2009
Christian Perrier wrote:
> Your review should be sent as an answer to this mail.
> Template: request-tracker3.8/webbaseurl
> Type: string
> +_Description: Base URL to the RT web interface:
> Please specify the scheme, server and (optionally) port for constructing
> URLs to the RT web interface.
>
> I'm unsure about "URL to <something>"
Me too:
_Description: Base URL for the RT web interface:
Please specify the scheme, server and (optionally) port for constructing
RT web interface URLs.
> Type: string
> _Description: Path to the RT web interface:
> If the RT web interface is going to be installed somewhere other than at
> + the root of the server, you should specify the path to it here.
Given that it's asking for a "path", "the root of my server" might
mean /; I'd suggest "other than at the docroot of the web server".
> Template: request-tracker3.8/warn-sqlite-file
> +Type: error
> +_Description: Broken SQLite file
> + Due to a bug in earlier versions of this package, the RT database appears
> to live in /var/lib/dbconfig-common/sqlite3/request-tracker3.8/_DBC_DBNAME_
The bug isn't that it appears to be living, it's that "the RT
database has been placed in..."
> + After this installation completes, you will need to manually move the file to its correct location
> + (see /etc/request-tracker3.8/RT_SiteConfig.d/51-dbconfig-common). RT will
> + not work until this action is done.
Either "s/action //" or probably "s/done/taken/".
> Package: request-tracker3.8
> Depends: rt3.8-clients (= ${source:Version}),
(http://lintian.debian.org/tags/substvar-source-version-is-deprecated.html)
> -Description: Extensible trouble-ticket tracking system
> +Description: trouble-ticket tracking system
>
> I'm not sure what "extensible" adds here...and synopsis are supposed
> to be neutral..:-)
It means that it's a heap of Perl modules that local admins are
encouraged to add to. This is a feature, but may also serve as a
warning to anyone looking for a lightweight, low-maintenance
issue-tracking app. Given that it only goes in this one line
(rather than bloating the synopses of all its related packages) I'd
vote to keep it.
> - Request Tracker (RT) is an enterprise-grade ticketing system which
> + Request Tracker (RT) is a ticketing system which
>
> I'm not sure what "enterprise-grade" means and I don't think it adds
> much value.
There's a mention of "enterprise-critical" applications later in the
long description anyway.
> enables a group of people to intelligently and efficiently manage
> tasks, issues, and requests submitted by a community of users. It
(All these "enterprise" references make me think this should say
"enables a group of people to *boldly* manage tasks, issues, and
requests"...)
> features a web, email and command-line interfaces (see the package
> rt3.8-clients).
s/a web/web/, and Harvard comma after "email" (to match the one
after "issues" in the previous sentence).
> - Written in object-oriented Perl, RT is a high-level, portable,
> + RT is a high-level, portable,
> platform independent system that eases collaboration within
> organizations and makes it easy for them to take care of their
> customers.
>
> The DevRef discourages mentioning information that doesn't really help
> users choosing this or that package, which is generally the case of
> mentions of the language they're written with.
If site admins are going to need to write plugins, they may well
select the issue-tracking system they install on the basis of
whether they'll be doing that in Lisp or Python. Still, there are
debtags, and it's not hard to guess from that Depends line.
> assignment, resolution and notification required by
> enterprise-critical applications including project management, help
> desk, NOC ticketing, CRM and software development.
(Some opportunities for extra commas.)
> Other changes seem invasive, but this is mostly about adding the
> boilerplate to ev ery binary package.
Yes, only a couple of things to comment on in rt3.8-clients:
> Description: Mail gateway and command-line interface to request-tracker3.8
m
[...]
> This package provides the needed setup and tools intended for a
> mail server so it can inject tickets into
> request-tracker3.8 using rt-mailgate. It should be installed onto any
> machine on which you want to use the "rt"
> command-line interface.
Is that "(needed setup [files]) and (tools intended for [...])" or
"needed (setup and tools) intended for [...]"? Does it "provide the
setup" in the sense of autoconfiguring? The READMEs say not, so cut
it down to:
This package provides support for injecting tickets into Request Tracker
from a mail server via rt-mailgate. It should be installed onto any
machine where you want to use the "rt" command-line interface.
--
JBR with qualifications in linguistics, experience as a Debian
sysadmin, and probably no clue about this particular package
-------------- next part --------------
Template: request-tracker3.8/rtname
Type: string
_Description: Name for this Request Tracker (RT) instance:
Every installation of Request Tracker must have a unique name.
The domain name or an abbreviation of the organization name are
usually good candidates.
.
Please note that once you start using a name, you should probably never
change it. Otherwise, mail for existing tickets won't get put in the right
place.
.
This setting corresponds to the $rtname configuration variable.
Template: request-tracker3.8/organization
Type: string
_Description: Identifier for this RT instance:
In addition to its name, every installation of Request Tracker must also have
a unique identifier. It is used when linking between RT installations.
.
Using this machine's fully qualified hostname (including the DNS domain name)
is recommended.
.
This setting corresponds to the $Organization configuration variable.
Template: request-tracker3.8/correspondaddress
Type: string
_Description: Default email address for RT correspondence:
Please choose the address that will be listed in From: and Reply-To: headers of
emails tracked by RT, unless overridden by a queue-specific
address.
.
This setting corresponds to the $CorrespondAddress configuration variable.
Template: request-tracker3.8/commentaddress
Type: string
_Description: Default email address for RT comments:
Please choose the address that will be listed in From: and Reply-To: headers of comment
emails, unless overridden by a queue-specific address. Comments can be
used for adding ticket information that is not visible to the client.
.
This setting corresponds to the $CommentAddress configuration variable.
Template: request-tracker3.8/webbaseurl
Type: string
_Description: Base URL for the RT web interface:
Please specify the scheme, server and (optionally) port for constructing
RT web interface URLs.
.
The value should not have a trailing slash (/).
.
This setting corresponds to the $WebBaseURL configuration variable.
Template: request-tracker3.8/webpath
Type: string
_Description: Path to the RT web interface:
If the RT web interface is going to be installed somewhere other than at
the docroot of the web server, you should specify the path to it here.
.
The value requires a leading slash (/) but not a trailing one.
.
This setting corresponds to the $WebPath configuration variable.
Template: request-tracker3.8/handle-siteconfig-permissions
Type: boolean
_Description: Handle RT_SiteConfig.pm permissions?
The RT web interface needs access to the database password, stored in the
main RT configuration file. Because of this, the file is made readable by
the www-data group in normal setups. This may have security implications.
.
If you reject this option, the file will be readable only by root, and
you will have to set up appropriate access controls yourself.
.
With the SQLite backend, this choice will also affect the
permissions of automatically-generated local database files.
Template: request-tracker3.8/warn-sqlite-file
Type: error
_Description: Broken SQLite file
Due to a bug in earlier versions of this package, the RT database has been
placed in /var/lib/dbconfig-common/sqlite3/request-tracker3.8/_DBC_DBNAME_
rather than its intended location.
.
After this installation completes, you
will need to manually move the file to its correct location
(see /etc/request-tracker3.8/RT_SiteConfig.d/51-dbconfig-common). RT will
not work until this action is taken.
-------------- next part --------------
Source: request-tracker3.8
Section: misc
Priority: optional
Maintainer: Debian Request Tracker Group <pkg-request-tracker-maintainers at lists.alioth.debian.org>
Uploaders: Niko Tyni <ntyni at debian.org>, Jacob Helwig <jacob at technosorcery.net>, Toni Mueller <toni at debian.org>, Ivan Kohler <ivan-debian at 420.am>, Gerardo Curiel <gcuriel at debian.org.ve>, Dominic Hargreaves <dom at earth.li>
Build-Depends: debhelper (>= 5), dpatch (>= 2.0.9)
Build-Depends-Indep: perl (>= 5.8.3), po-debconf
Standards-Version: 3.8.0
Vcs-Svn: svn://svn.debian.org/svn/pkg-request-tracker/packages/request-tracker3.8/trunk
Vcs-Browser: http://svn.debian.org/wsvn/pkg-request-tracker/packages/request-tracker3.8/trunk
Package: request-tracker3.8
Architecture: all
Depends: rt3.8-clients (= ${source:Version}),
rt3.8-apache2 (= ${source:Version}),
rt3.8-db-sqlite (= ${source:Version})
| rt3.8-db-postgresql (= ${source:Version})
| rt3.8-db-mysql (= ${source:Version}),
exim4 | mail-transport-agent,
sysklogd | system-log-daemon, ${perl:Depends},
libhtml-mason-perl (>= 1:1.36-1), libapache-session-perl (>= 1.53),
libregexp-common-perl, libdbi-perl (>= 1.37),
libclass-returnvalue-perl (>= 0.40), libdbix-searchbuilder-perl (>= 1.53),
libcache-simple-timedexpiry-perl, libtext-template-perl (>= 1.44),
liblog-dispatch-perl (>= 2.0), libhtml-parser-perl,
liblocale-maketext-fuzzy-perl, liblocale-maketext-lexicon-perl (>= 0.32),
libmime-tools-perl (>= 5.108) | libmime-perl (>= 5.108), libmime-types-perl,
libmailtools-perl (>= 1.57), libtext-wrapper-perl,
libtime-modules-perl, libtext-autoformat-perl, libtext-wikiformat-perl,
libhtml-scrubber-perl, libmodule-versions-report-perl (>= 1.03),
libtree-simple-perl (>= 1.04), libxml-rss-perl (>= 1.05), libxml-simple-perl,
libcalendar-simple-perl, libgd-graph-perl, libuniversal-require-perl,
libgd-text-perl, libtimedate-perl, dbconfig-common (>= 1.8.38),
ucf (>= 0.28), libcss-squish-perl (>= 0.06),
libdevel-stacktrace-perl (>= 1.19),libfile-sharedir-perl,
libemail-address-perl, libperlio-eol-perl,
libdata-ical-perl, libtext-quoted-perl (>= 2.02),
libhtml-rewriteattributes-perl (>= 0.02),
libgraphviz-perl, libgnupg-interface-perl,
libjs-scriptaculous, libjs-prototype, libipc-run-safehandles-perl
${misc:Depends}
Recommends: speedy-cgi-perl
Suggests: rt3.8-rtfm
Conflicts: request-tracker, request-tracker3.2 (<< 3.2.2-3)
Replaces: request-tracker
Description: extensible trouble-ticket tracking system
Request Tracker (RT) is a ticketing system which
enables a group of people to intelligently and efficiently manage
tasks, issues, and requests submitted by a community of users. It
features web, email, and command-line interfaces (see the package
rt3.8-clients).
.
This package provides the 3.8 series of RT. It can be installed alongside the 3.4
and 3.6 series without any problems.
.
RT is a high-level, portable,
platform independent system that eases collaboration within
organizations and makes it easy for them to take care of their
customers.
.
RT manages key tasks such as the identification, prioritization,
assignment, resolution, and notification required by
enterprise-critical applications, including project management, help
desk, NOC ticketing, CRM, and software development.
.
This package provides the core of RT.
Package: rt3.8-clients
Architecture: all
Depends: ${perl:Depends}, exim4 | mail-transport-agent,
libhtml-tree-perl, libhtml-format-perl, libwww-perl, libterm-readkey-perl,
libterm-readline-perl-perl | libterm-readline-gnu-perl,
${misc:Depends}
Recommends: libio-socket-ssl-perl
Description: mail gateway and command-line interface to request-tracker3.8
Request Tracker (RT) is a ticketing system which
enables a group of people to intelligently and efficiently manage
tasks, issues, and requests submitted by a community of users. It
features web, email, and command-line interfaces (see the package
rt3.8-clients).
.
This package provides the 3.8 series of RT. It can be installed alongside the 3.4
and 3.6 series without any problems.
.
RT is a high-level, portable,
platform independent system that eases collaboration within
organizations and makes it easy for them to take care of their
customers.
.
RT manages key tasks such as the identification, prioritization,
assignment, resolution, and notification required by
enterprise-critical applications, including project management, help
desk, NOC ticketing, CRM, and software development.
.
This package provides support for injecting tickets into Request Tracker
from a mail server via rt-mailgate. It should be installed onto any
machine where you want to use the "rt" command-line interface.
Package: rt3.8-apache2
Architecture: all
Depends: apache2,
libapache2-mod-perl2 (>= 2.0.0) | speedy-cgi-perl | libapache2-mod-fcgid
| libapache2-mod-fastcgi,
libapache2-mod-perl2 (>= 2.0.0) | speedy-cgi-perl | libcgi-fast-perl,
libapache-dbi-perl (>= 0.92) | speedy-cgi-perl | libapache2-mod-fcgid
| libapache2-mod-fastcgi,
${misc:Depends}
Suggests: libapache2-mod-speedycgi
Description: Apache 2 specific files for request-tracker3.8
Request Tracker (RT) is a ticketing system which
enables a group of people to intelligently and efficiently manage
tasks, issues, and requests submitted by a community of users. It
features web, email, and command-line interfaces (see the package
rt3.8-clients).
.
This package provides the 3.8 series of RT. It can be installed alongside the 3.4
and 3.6 series without any problems.
.
RT is a high-level, portable,
platform independent system that eases collaboration within
organizations and makes it easy for them to take care of their
customers.
.
RT manages key tasks such as the identification, prioritization,
assignment, resolution, and notification required by
enterprise-critical applications, including project management, help
desk, NOC ticketing, CRM, and software development.
.
This package provides various configuration files and manages the
necessary dependencies for running request tracker (RT) version 3.8
on the Apache 2 web server.
Package: rt3.8-db-postgresql
Architecture: all
Depends: ${misc:Depends}, libdbd-pg-perl (>= 1.41),
postgresql-client-8.3 | postgresql-client (>= 7.4)
Suggests: postgresql-8.3 | postgresql (>= 7.4)
Description: PostgreSQL database backend for request-tracker3.8
Request Tracker (RT) is a ticketing system which
enables a group of people to intelligently and efficiently manage
tasks, issues, and requests submitted by a community of users. It
features web, email, and command-line interfaces (see the package
rt3.8-clients).
.
This package provides the 3.8 series of RT. It can be installed alongside the 3.4
and 3.6 series without any problems.
.
RT is a high-level, portable,
platform independent system that eases collaboration within
organizations and makes it easy for them to take care of their
customers.
.
RT manages key tasks such as the identification, prioritization,
assignment, resolution, and notification required by
enterprise-critical applications, including project management, help
desk, NOC ticketing, CRM, and software development.
.
This package provides dependencies and dbconfig-common support for
using Request Tracker version 3.8 with a PostgreSQL database.
Package: rt3.8-db-mysql
Architecture: all
Depends: ${misc:Depends}, libdbd-mysql-perl (>= 2.1018),
mysql-client-5.0 | mysql-client (>= 4.0.13)
Suggests: mysql-server-5.0 | mysql-server (>= 4.0.13)
Description: MySQL database backend for request-tracker3.8
Request Tracker (RT) is a ticketing system which
enables a group of people to intelligently and efficiently manage
tasks, issues, and requests submitted by a community of users. It
features web, email, and command-line interfaces (see the package
rt3.8-clients).
.
This package provides the 3.8 series of RT. It can be installed alongside the 3.4
and 3.6 series without any problems.
.
RT is a high-level, portable,
platform independent system that eases collaboration within
organizations and makes it easy for them to take care of their
customers.
.
RT manages key tasks such as the identification, prioritization,
assignment, resolution, and notification required by
enterprise-critical applications, including project management, help
desk, NOC ticketing, CRM, and software development.
.
This package provides dependencies and dbconfig-common support for
using Request Tracker version 3.8 with a MySQL database.
Package: rt3.8-db-sqlite
Architecture: all
Depends: ${misc:Depends}, libdbd-sqlite3-perl, sqlite3
Description: SQLite database backend for request-tracker3.8
Request Tracker (RT) is a ticketing system which
enables a group of people to intelligently and efficiently manage
tasks, issues, and requests submitted by a community of users. It
features web, email, and command-line interfaces (see the package
rt3.8-clients).
.
This package provides the 3.8 series of RT. It can be installed alongside the 3.4
and 3.6 series without any problems.
.
RT is a high-level, portable,
platform independent system that eases collaboration within
organizations and makes it easy for them to take care of their
customers.
.
RT manages key tasks such as the identification, prioritization,
assignment, resolution, and notification required by
enterprise-critical applications, including project management, help
desk, NOC ticketing, CRM, and software development.
.
This package provides dependencies and dbconfig-common support for
using Request Tracker version 3.8 with a local SQLite (version 3) database.
-------------- next part --------------
--- ../request-tracker3.8.old/debian/templates 2009-03-15 09:54:31.000000000 +0000
+++ debian/templates 2009-03-20 12:14:42.000000000 +0000
@@ -1,8 +1,8 @@
Template: request-tracker3.8/rtname
Type: string
-_Description: Name for this RT instance:
+_Description: Name for this Request Tracker (RT) instance:
Every installation of Request Tracker must have a unique name.
- The domain name or an abbreviation of the name of your organization are
+ The domain name or an abbreviation of the organization name are
usually good candidates.
.
Please note that once you start using a name, you should probably never
@@ -25,7 +25,7 @@
Template: request-tracker3.8/correspondaddress
Type: string
_Description: Default email address for RT correspondence:
- This address will be listed in From: and Reply-To: headers of
+ Please choose the address that will be listed in From: and Reply-To: headers of
emails tracked by RT, unless overridden by a queue-specific
address.
.
@@ -34,17 +34,17 @@
Template: request-tracker3.8/commentaddress
Type: string
_Description: Default email address for RT comments:
- This address will be listed in From: and Reply-To: headers of comment
- emails, unless overridden by a queue-specific address. (Comments can be
- used for adding ticket information that is not visible to the client.)
+ Please choose the address that will be listed in From: and Reply-To: headers of comment
+ emails, unless overridden by a queue-specific address. Comments can be
+ used for adding ticket information that is not visible to the client.
.
This setting corresponds to the $CommentAddress configuration variable.
Template: request-tracker3.8/webbaseurl
Type: string
-_Description: Base URL to the web interface:
+_Description: Base URL for the RT web interface:
Please specify the scheme, server and (optionally) port for constructing
- URLs to the RT web interface.
+ RT web interface URLs.
.
The value should not have a trailing slash (/).
.
@@ -54,7 +54,7 @@
Type: string
_Description: Path to the RT web interface:
If the RT web interface is going to be installed somewhere other than at
- the root of your server, you should specify the path to it here.
+ the docroot of the web server, you should specify the path to it here.
.
The value requires a leading slash (/) but not a trailing one.
.
@@ -70,15 +70,17 @@
If you reject this option, the file will be readable only by root, and
you will have to set up appropriate access controls yourself.
.
- Note: with the SQLite backend, your answer will also affect the
- permissions of automatically generated local database files.
+ With the SQLite backend, this choice will also affect the
+ permissions of automatically-generated local database files.
Template: request-tracker3.8/warn-sqlite-file
-Type: note
-_Description: Broken SQLite file found
- Due to a bug in earlier versions of this package, your RT database appears
- to live in /var/lib/dbconfig-common/sqlite3/request-tracker3.8/_DBC_DBNAME_
- rather than its intended location. After this installation completes, you
+Type: error
+_Description: Broken SQLite file
+ Due to a bug in earlier versions of this package, the RT database has been
+ placed in /var/lib/dbconfig-common/sqlite3/request-tracker3.8/_DBC_DBNAME_
+ rather than its intended location.
+ .
+ After this installation completes, you
will need to manually move the file to its correct location
- (see /etc/request-tracker3.8/RT_SiteConfig.d/51-dbconfig-common) before
- RT will work again.
+ (see /etc/request-tracker3.8/RT_SiteConfig.d/51-dbconfig-common). RT will
+ not work until this action is taken.
--- ../request-tracker3.8.old/debian/control 2009-03-15 09:54:34.000000000 +0000
+++ debian/control 2009-03-20 13:06:11.000000000 +0000
@@ -43,25 +43,27 @@
Suggests: rt3.8-rtfm
Conflicts: request-tracker, request-tracker3.2 (<< 3.2.2-3)
Replaces: request-tracker
-Description: Extensible trouble-ticket tracking system
- Request Tracker (RT) is an enterprise-grade ticketing system which
+Description: extensible trouble-ticket tracking system
+ Request Tracker (RT) is a ticketing system which
enables a group of people to intelligently and efficiently manage
tasks, issues, and requests submitted by a community of users. It
- features a web, email and command-line interfaces (see the package
+ features web, email, and command-line interfaces (see the package
rt3.8-clients).
.
- This is the 3.8 series of RT, it can be installed alongside the 3.4
+ This package provides the 3.8 series of RT. It can be installed alongside the 3.4
and 3.6 series without any problems.
.
- Written in object-oriented Perl, RT is a high-level, portable,
+ RT is a high-level, portable,
platform independent system that eases collaboration within
organizations and makes it easy for them to take care of their
customers.
.
RT manages key tasks such as the identification, prioritization,
- assignment, resolution and notification required by
- enterprise-critical applications including project management, help
- desk, NOC ticketing, CRM and software development.
+ assignment, resolution, and notification required by
+ enterprise-critical applications, including project management, help
+ desk, NOC ticketing, CRM, and software development.
+ .
+ This package provides the core of RT.
Package: rt3.8-clients
Architecture: all
@@ -70,14 +72,29 @@
libterm-readline-perl-perl | libterm-readline-gnu-perl,
${misc:Depends}
Recommends: libio-socket-ssl-perl
-Description: Mail gateway and command-line interface to request-tracker3.8
- Install this package onto the mail server so it can inject tickets into
- request-tracker3.8 using rt-mailgate.
+Description: mail gateway and command-line interface to request-tracker3.8
+ Request Tracker (RT) is a ticketing system which
+ enables a group of people to intelligently and efficiently manage
+ tasks, issues, and requests submitted by a community of users. It
+ features web, email, and command-line interfaces (see the package
+ rt3.8-clients).
.
- Install it onto any machine on which you want to use the 'rt'
- command-line interface.
+ This package provides the 3.8 series of RT. It can be installed alongside the 3.4
+ and 3.6 series without any problems.
.
- See the 'request-tracker3.8' package for further information.
+ RT is a high-level, portable,
+ platform independent system that eases collaboration within
+ organizations and makes it easy for them to take care of their
+ customers.
+ .
+ RT manages key tasks such as the identification, prioritization,
+ assignment, resolution, and notification required by
+ enterprise-critical applications, including project management, help
+ desk, NOC ticketing, CRM, and software development.
+ .
+ This package provides support for injecting tickets into Request Tracker
+ from a mail server via rt-mailgate. It should be installed onto any
+ machine where you want to use the "rt" command-line interface.
Package: rt3.8-apache2
Architecture: all
@@ -90,11 +107,28 @@
${misc:Depends}
Suggests: libapache2-mod-speedycgi
Description: Apache 2 specific files for request-tracker3.8
+ Request Tracker (RT) is a ticketing system which
+ enables a group of people to intelligently and efficiently manage
+ tasks, issues, and requests submitted by a community of users. It
+ features web, email, and command-line interfaces (see the package
+ rt3.8-clients).
+ .
+ This package provides the 3.8 series of RT. It can be installed alongside the 3.4
+ and 3.6 series without any problems.
+ .
+ RT is a high-level, portable,
+ platform independent system that eases collaboration within
+ organizations and makes it easy for them to take care of their
+ customers.
+ .
+ RT manages key tasks such as the identification, prioritization,
+ assignment, resolution, and notification required by
+ enterprise-critical applications, including project management, help
+ desk, NOC ticketing, CRM, and software development.
+ .
This package provides various configuration files and manages the
necessary dependencies for running request tracker (RT) version 3.8
on the Apache 2 web server.
- .
- See the 'request-tracker3.8' package for further information.
Package: rt3.8-db-postgresql
Architecture: all
@@ -102,6 +136,25 @@
postgresql-client-8.3 | postgresql-client (>= 7.4)
Suggests: postgresql-8.3 | postgresql (>= 7.4)
Description: PostgreSQL database backend for request-tracker3.8
+ Request Tracker (RT) is a ticketing system which
+ enables a group of people to intelligently and efficiently manage
+ tasks, issues, and requests submitted by a community of users. It
+ features web, email, and command-line interfaces (see the package
+ rt3.8-clients).
+ .
+ This package provides the 3.8 series of RT. It can be installed alongside the 3.4
+ and 3.6 series without any problems.
+ .
+ RT is a high-level, portable,
+ platform independent system that eases collaboration within
+ organizations and makes it easy for them to take care of their
+ customers.
+ .
+ RT manages key tasks such as the identification, prioritization,
+ assignment, resolution, and notification required by
+ enterprise-critical applications, including project management, help
+ desk, NOC ticketing, CRM, and software development.
+ .
This package provides dependencies and dbconfig-common support for
using Request Tracker version 3.8 with a PostgreSQL database.
@@ -111,6 +164,25 @@
mysql-client-5.0 | mysql-client (>= 4.0.13)
Suggests: mysql-server-5.0 | mysql-server (>= 4.0.13)
Description: MySQL database backend for request-tracker3.8
+ Request Tracker (RT) is a ticketing system which
+ enables a group of people to intelligently and efficiently manage
+ tasks, issues, and requests submitted by a community of users. It
+ features web, email, and command-line interfaces (see the package
+ rt3.8-clients).
+ .
+ This package provides the 3.8 series of RT. It can be installed alongside the 3.4
+ and 3.6 series without any problems.
+ .
+ RT is a high-level, portable,
+ platform independent system that eases collaboration within
+ organizations and makes it easy for them to take care of their
+ customers.
+ .
+ RT manages key tasks such as the identification, prioritization,
+ assignment, resolution, and notification required by
+ enterprise-critical applications, including project management, help
+ desk, NOC ticketing, CRM, and software development.
+ .
This package provides dependencies and dbconfig-common support for
using Request Tracker version 3.8 with a MySQL database.
@@ -118,6 +190,24 @@
Architecture: all
Depends: ${misc:Depends}, libdbd-sqlite3-perl, sqlite3
Description: SQLite database backend for request-tracker3.8
+ Request Tracker (RT) is a ticketing system which
+ enables a group of people to intelligently and efficiently manage
+ tasks, issues, and requests submitted by a community of users. It
+ features web, email, and command-line interfaces (see the package
+ rt3.8-clients).
+ .
+ This package provides the 3.8 series of RT. It can be installed alongside the 3.4
+ and 3.6 series without any problems.
+ .
+ RT is a high-level, portable,
+ platform independent system that eases collaboration within
+ organizations and makes it easy for them to take care of their
+ customers.
+ .
+ RT manages key tasks such as the identification, prioritization,
+ assignment, resolution, and notification required by
+ enterprise-critical applications, including project management, help
+ desk, NOC ticketing, CRM, and software development.
+ .
This package provides dependencies and dbconfig-common support for
using Request Tracker version 3.8 with a local SQLite (version 3) database.
-
More information about the pkg-request-tracker-maintainers
mailing list