The request-tracker3.8 package introduced new or modified debconf templates. This is the perfect moment for a review to help the package maintainer following the general suggested writing style and track down typos and errors in the use of English language. If someone wants to pick up this review, please answer to this mail, in the mailing list, with an [ITR] (Intent To Review) label. The templates file is attached. To propose the file you reviewed for peer review, please send a [RFR] (Request For Review) mail with the reviewed file attached...then a few days later, when no more contributions come, a summary mail with a [LCFC] (Last Chance For Comments) label. Finally, after no more comments coming to the LCFC mail, you can send the reviewed templates file as a bug report against the package. Then, please notify the list with a last mail using a [BTS] label with the bug number. Helping the package maintainer to deal with induced translation updates at that moment will be nice. If you're not comfortable with that part of the process, please hand it off to a translator. --
Template: request-tracker3.8/rtname Type: string _Description: Name for this 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 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: This address 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: 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.) . This setting corresponds to the $CommentAddress configuration variable. Template: request-tracker3.8/webbaseurl Type: string _Description: Base URL to the web interface: Please specify the scheme, server and (optionally) port for constructing URLs to the RT web interface. . 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 root of your 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. . Note: with the SQLite backend, your answer 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 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.
Source: request-tracker3.8
Section: misc
Priority: optional
Maintainer: Debian Request Tracker Group <pkg-request-tracker-maintainers@lists.alioth.debian.org>
Uploaders: Niko Tyni <ntyni@debian.org>, Jacob Helwig <jacob@technosorcery.net>, Toni Mueller <toni@debian.org>, Ivan Kohler <ivan-debian@420.am>, Gerardo Curiel <gcuriel@debian.org.ve>, Dominic Hargreaves <dom@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 an enterprise-grade 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
rt3.8-clients).
.
This is 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,
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.
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
Install this package onto the mail server so it can inject tickets into
request-tracker3.8 using rt-mailgate.
.
Install it onto any machine on which you want to use the 'rt'
command-line interface.
.
See the 'request-tracker3.8' package for further information.
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
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
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
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
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
This package provides dependencies and dbconfig-common support for
using Request Tracker version 3.8 with a local SQLite (version 3) database.
Attachment:
signature.asc
Description: Digital signature