RT is an industrial-grade ticketing system. It lets a group of people
intelligently and efficiently manage requests submitted by a community
of users. RT is used by systems administrators, customer support
staffs, NOCs, developers and even marketing departments at over a
thousand sites around the world.
RT3 significantly revamped the RT codebase, featuring standard-compliant
Web UI, approval-based workflow system, REST-powered RPC mail gateway,
recursive group membership with delegates, autoconf, custom field support,
I18N and L10N framework, web-editable scrips, better documentation and
regression test suite, and more.
WWW: http://www.bestpractical.com/rt/
===> The following configuration options are available for rt40-4.0.24_1:
DEV=off: Configure for Developers
DOCS=on: Build and/or install documentation
GD=on: Enable GD Graphs and Charts
GPG=on: Enable GnuPG support
GRAPHVIZ=off: Graphviz graph drawing support
SSL_MAILGATE=off: Enable HTTPS support for rt-mailgate
====> Options available for the single DB: you have to select exactly one of them
MYSQL=on: MySQL database support
ORACLE=off: Oracle database support
PGSQL=off: PostgreSQL database support
SQLITE=off: SQLite database support
====> Options available for the radio WEB: you can only select none or one of them
AP_MODFASTCGI=on: Deploy with apache and mod_fastcgi
AP_MODPERL=off: Deploy with apache and mod_perl
LIGHTTPD=off: Deploy with lighttpd and mod_fastcgi
SPAWN_FCGI=off: Deploy with spawn_fcgi
===> Use 'make config' to modify these settings
Remove expired ports:
2017-02-15 www/rt40: Upstream support EoL, please migrate to rt44
2017-02-17 devel/m6811-binutils: multiple vulnerabilities, version is years
behind upstream
Remove USE_SQLITE from bsd.databases.mk, replaced by USES=sqlite.
While there replace USE_SQLITE=x by USES=sqlite:x.
PR: 208971
Submitted by: mat
Exp-run by: antoine
With hat: portmgr
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D5951
New port: www/rt44
RT is a battle-tested issue tracking system which thousands of
organizations use for bug tracking, help desk ticketing, customer
service, workflow processes, change management, network operations,
youth counselling and even more. Organizations around the world have
been running smoothly thanks to RT for over 10 years.
WWW: http://www.bestpractical.com/rt/
PR: 208229
Submitted by: mikael.urankar@gmail.com
Prepare for perl-5.22
- Add dependency on www/p5-CGI conditional on perl version. CGI is
no-longer a core module with 5.22.
- Make the default web server interface Apache + FCGI rather than
Apache + mod_perl. Current versions of mod_perl aren't compatible
with perl-5.22
Change the way Perl modules are installed, update the default Perl to 5.18.
Before, we had:
site_perl : lib/perl5/site_perl/5.18
site_perl/perl_arch : lib/perl5/site_perl/5.18/mach
perl_man3 : lib/perl5/5.18/man/man3
Now we have:
site_perl : lib/perl5/site_perl
site_arch : lib/perl5/site_perl/mach/5.18
perl_man3 : lib/perl5/site_perl/man/man3
Modules without any .so will be installed at the same place regardless of the
(Only the first 15 lines of the commit message are shown above )
Update to 4.0.22
- USES_PGSQL -> USES+= pgsql
- Remove Sourceforge from MASTER_SITES: it only ever had rt-4.0.16
available
- Now that the problems with UTF8 in the DB have been solved, switch
back to depending on p5-DBD-Pg rather than p5-DBD-Pg32
Update to 4.0.21
Note: For Postgresql users -- this version of RT requires a
down-graded copy of DBD::Pg which is supplied by the new
databases/p5-DBD-Pg32 port. This may cause conflicts if you have
other consumers of p5-DBD-Pg installed.
ReleaseNotes: http://bestpractical.com/release-notes/rt/4.0.21
Bump more ports that depend on libsqlite3.so:
- ports that set USE_SQLITE with the *_USE option helper
- ports that depend on libsqlite3 indirectly as reported by pkg rquery
Approved by: portmgr (implicit)
- Fix plist to have proper 'rmdir DIR' ordering.
Pkgng will not detect the directory otherwise. This was due to
incorrectly advise in the check-stagedir.sh script, fixed in
r351587
With hat: portmgr
* Since BUILD_DEPENDS is always going to be a super-set of
RUN_DEPENDS, simplfy things by calculating RUN_DEPENDS based on
the OPTIONS settings, then just append that to BUILD_DEPENDS.
No functional change to the generated packaage, so no
PORTREVISION bump.
* OPTIONS helpers
* Install docs unconditionally to stage
* DATADIR should be relative to $PREFIX, not $LOCALBASE
* use CONFLICTS_INSTALL rather than CONFLICTS
* use @exec/@unexec etc. in pkg-plist and update patch-Makefile.in
so that staging no longer needs root
Mark all my architecture independent ports using shell/perl/PHP as
NO_ARCH=yes
While here, fix a few other niggles:
net/phpldapadmin -- remove indefinite article from COMMENT
www/p5-RT* -- fix comments referencing the different versions of RT
x11-fonts/gentium-{basic,plus} -- mention ${STAGEDIR} explicitly in the
install targets; rework the handling of ${FONTPATH}
Convert all my perl-using ports to USES+=perl5
While here:
- add USES+=shebangfix to ports-mgmt/p5-FreeBSD-Portindex
- set $PERL in CONFIGURE_ENV to achieve equivalent to shebangfix
for www/rt40
- upgrade to 0.17 and fix pkg-plist for www/p5-RT-Authen-ExternalAuth
- trim Makefile header for www/p5-RTx-Calendar
- Update to 4.0.15
This is a quick-fix for a regression discovered in the recent 4.0.14
release when upgrading the DB schema from version 3.8.x. Functionally
4.0.14 and 4.0.15 are the same: if you already have 4.0.14 running,
you do not need to upgrade.
- Require p5-Email-Address >= 1.895 as versions 1.893 -- 1.894 have
serious bugs when handling non-ascii characters in addresses
- Remove the mirror at ftp.eu.uu.net which hasn't been updated since
the release of rt-4.0.8
- Add SourceForge as a mirror site
Security Updates
- www/rt40 to 4.0.13
- www/rt38 to 3.8.17 [1]
This is a security fix addressing a number of CVEs:
CVE-2012-4733
CVE-2013-3368
CVE-2013-3369
CVE-2013-3370
CVE-2013-3371
CVE-2013-3372
CVE-2013-3373
CVE-2013-3374
Users will need to update their database schemas as described in
pkg-message
Approved by: flo [1]
Security: 3a429192-c36a-11e2-97a9-6805ca0b3d42
Delete some dead code, left over from pre-OPTIONSNG days.
Clarify comments about choosing a web platform option: you don't need
to choose any of the four options show, but can use the built-in plack
webserver.
Submitted by: G.halse@ru.ac.za
Update to 4.0.12
ChangeLogs: http://www.bestpractical.com/rt/release-notes/4.0.12
Note: There has been a change to the database schema. Administrators
will need to use rt-setup-database to apply the update, as described
in pkg-message.
Use new OPTIONS_RADIO to select 0 or 1 of the web deployment options.
The old 'BUILTIN' PSGI web server option was and remains always
available independent of the web deployment option chosen.
-- Always use += for modifying CONFIGURE_ARGS (1)
-- The ${LOCALBASE}/rt40/share/plugins directory is shared with
various RT plugin ports so don't try and delete it
unconditionally.
Submitted by: Ryan Langseth (1)
Approved by: shaun (mentor)
Feature safe: yes
- new OPTION: SSL_MAILGATE -- enable HTTPS support in rt-mailgate (off by
default)
- remove some pointless quote marks from Makefile
- various pkg-plist fixes in addition to those due to the update -- create some
empty directories so that pkg installs match port installs; as these are for the
use of RT addons, don't remove them unconditionally either.
- fix comments referring to apache13, now it has gone
- remove CONFLICTS with rt-3.6* (not in the tree anumore)
PR: 164738
Submitted by: Matthew Seaman <m.seaman at infracaninophile dot co.uk>
(maintainer)
- Bugfix upgrade to version 4.0.4
- Announce Message:
"RT 4.0.3 contained a serious bug wherein upgrades from any version of
RT 3 to RT 4.0.3 broke template interpolation; please do not use it. If
you had previously upgraded from RT 3 to RT 4.0.0, 4.0.1, or 4.0.2,
before upgrading to RT 4.0.3, you are not affected by this bug.
If you are currently running RT 4.0.3 and are affected by this issue,
upgrading to RT 4.0.4 will resolve it."
Note for users: if you have already successfully installed or upgraded
to rt-4.0.3 then there is no pressing need to upgrade to rt-4.0.4 --
there are no changes to the RT code itself. This upgrade only
provides fixes for people that have upgraded from RT-3.x and are
experiencing problems..
PR: ports/162469
Submitted by: maintainer (Matthew Seaman)
Feature safe: yes
Routine bugfix upgrade to version 4.0.3
ChangeLog:
This release contains a number of bugfixes and small improvements since
the 4.0.2 release; a few of the more notable ones include:
* Due to a change in RT 3.8.9, which also affected RT 4.0.0 and higher,
TransactionBatch scrips were run twice; this has now been fixed.
* A new toggle has been added to expand all quote folding in a ticket's
transaction history.
* New "On Forward", "On Forward Transaction" and "On Forward Ticket"
conditions have been added.
(Only the first 15 lines of the commit message are shown above )
