Package: request-tracker5 / 5.0.3+dfsg-3~deb12u2
Metadata
Package | Version | Patches format |
---|---|---|
request-tracker5 | 5.0.3+dfsg-3~deb12u2 | 3.0 (quilt) |
Patch series
view the series filePatch | File delta | Description |
---|---|---|
layout.diff | (download) |
config.layout |
29 29 + 0 - 0 ! |
add debian layout (fhs-compatible) |
sitemodules.diff | (download) |
lib/RT/Interface/Web/Handler.pm |
1 1 + 0 - 0 ! |
use rt_sitemodules.pm in lib/rt/interface/web/handler.pm |
rt_setup_database_upgrade_basedir.diff | (download) |
sbin/rt-setup-database.in |
2 1 + 1 - 0 ! |
fix relative references to config path |
debianize_backup_docs.diff | (download) |
docs/system_administration/database.pod |
60 42 + 18 - 0 ! |
customise backup docs for debian |
debianize_docs_local.diff | (download) |
docs/customizing/styling_rt.pod |
13 6 + 7 - 0 ! |
reference correct local directory for debian |
fix_lintian_privacy_break_logo_error.diff | (download) |
share/html/index.html |
6 3 + 3 - 0 ! |
don't include remote image references or redirects in broken install page This fixes the lintian error privacy-breach-logo |
debianize_UPGRADING 4.2.diff | (download) |
docs/UPGRADING-4.2 |
6 3 + 3 - 0 ! |
debianize upgrading-4.2 |
assettracker sysgroups.diff | (download) |
etc/upgrade/4.1.0/schema.SQLite |
3 3 + 0 - 0 ! |
fix upgrade problems caused by an rtx::assettracker installation bug The setup of the wheezy rt4-extension-assettracker package (RTx::AssetTracker 2.0.0b2) accidentally inserted two pairs of system role accounts, causing upgrade failures on SQLite backends due to uniqueness constraint violations. Bug-Debian: https://bugs.debian.org/773343 |
load_rt_generated.diff | (download) |
lib/RT.pm |
4 1 + 3 - 0 ! |
load rt::generated directly from @inc This allows for the possibility of overriding RT::Generated in test scenarios. |
rt_test_db_type.diff | (download) |
lib/RT/Test.pm |
3 3 + 0 - 0 ! |
allow overriding databasetype from the environment in rt::test |
debianize_version.diff | (download) |
configure.ac |
8 4 + 4 - 0 ! |
extract the correct (debian) version number in configure.ac Also make clear in the web interface that this version number is from Debian. |
fonts_use_noto_sans.diff | (download) |
etc/RT_Config.pm.in |
2 1 + 1 - 0 ! |
use noto sans instead of droid sans Droid Sans is deprecated in Debian, and we are using the fonts from Debian rather than bundled with RT. Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804687 |
test_locale.diff | (download) |
lib/RT/Test.pm |
1 1 + 0 - 0 ! |
set lc_all to c LANG overrides only not set LC_variables, so if LC_CTYPE is set in the environment, it persists and tons of tests fail. |
use_cpanel_json_xs.diff | (download) |
lib/RT/Interface/Web.pm |
4 4 + 0 - 0 ! |
force the use of cpanel::json::xs JSON::XS breaks RT due to the removed from_json/to_json methods and JSON.pm prefers JSON::XS to our preferred implementation Cpanel::JSON::XS by default. Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848041 |
fix_pod_rt_munge_attachments.diff | (download) |
sbin/rt-munge-attachments.in |
2 1 + 1 - 0 ! |
fix pod for rt-munge-attachments |
fix_shebang_upgrade_mysql_schema.diff | (download) |
etc/upgrade/upgrade-mysql-schema.pl |
2 1 + 1 - 0 ! |
fix shebang for debian policy |
fix_test_ldap_ipv4.diff | (download) |
t/externalauth/ldap.t |
12 9 + 3 - 0 ! |
force use of ipv4 for ldap test. Net::LDAP::Server::Test binds to IPv6 by default, but Net::LDAP uses 'localhost' which resolves to an IPv4 address. Even when I switched the call to Net::LDAP->new() to use ip6-localhost it failed elsewhere due to RT using 127.0.0.1. |
debianize_extensions.diff | (download) |
docs/extensions.pod |
4 2 + 2 - 0 ! |
point to debian locaton of mason_data. |
debianize_commands.diff | (download) |
docs/authentication.pod |
2 1 + 1 - 0 ! |
use debian location of commands and data |
debianize_charts.diff | (download) |
docs/charts.pod |
52 10 + 42 - 0 ! |
on debian there is no need to install the gd modules if gd is desired. |
ignore_Mozilla::CA.diff | (download) |
etc/cpanfile |
1 0 + 1 - 0 ! |
debian provides the mozilla cas in the ca-certificates package. |
fcgi_client_sigpipe.diff | (download) |
sbin/rt-server.fcgi |
3 3 + 0 - 0 ! |
a client terminating a connection shouldn't kill a fcgi process When a client disconnects before processing is complete than a SIGPIPE is sent to the FCGI process. Previously this would cause the process to exit. Discussed on the forum here: * https://forum.bestpractical.com/t/rt-4-4-fastcgi-processes-frequently-dying/34812 * https://forum.bestpractical.com/t/why-does-rts-fcgi-server-not-handle-sigpipe/35902 |
disable test smime realmail.diff | (download) |
t/mail/smime/realmail.t |
3 3 + 0 - 0 ! |
skip t/mail/smime/realmail.t for now. Broken by OpenSSL 3.0 as the test emails use DES which is now disabled. |
remove_exclude_Test::WWW::Mechanize.diff | (download) |
etc/cpanfile |
2 1 + 1 - 0 ! |
remove exclude of test::www::mechanize 1.58 The Debian maintainers of libtest-www-mechanize-perl have built their version of 1.58 with the patch that fixes the issue with Text::LongString breaking the RT tests. Upstream report of issue (merged for the upcoming 1.59 release): https://github.com/petdance/test-www-mechanize/pull/79 |
Update tests for EN datetime locale change to space.diff | (download) |
t/api/date.t |
37 21 + 16 - 0 ! |
update tests for en datetime locale change to space This patch has been cherry-picked from upstream 5.0-trunk. It can be dropped once we import 5.0.4 (when it is released). DateTime::Locale version 1.58 published CLDR 42.0.0 which changed the space character in times before the AM and PM to be U+202F NARROW NO-BREAK SPACE (aka NNBSP) from the previous space (U+0020). This broke tests looking for a space character for localized datetimes with an AM/PM. Update to a like test to work for older versions of DateTime::Locale and for new ones from 1.58 forward. |
libdatetime format natural perl v0.14.diff | (download) |
etc/cpanfile |
1 1 + 0 - 0 ! |
support datetime::format::natural >= 0.13_01 Version 0.13_01 switched from using DateTime to DateTime::HiRes for setting the initial time. This means we in turn need to use Test::MockTime::HiRes. Error I was getting in Debian with libdatetime-format-natural-perl v0.14 and v0.15: t/api/date.t .. 4/? # Failed test 'April in the past' # at t/api/date.t line 650. # got: '2023-03-31 16:00:00' # expected: '2015-03-31 16:00:00' # Failed test 'Monday in the past' # at t/api/date.t line 655. # got: '2023-01-29 16:00:00' # expected: '2015-11-22 16:00:00' # Failed test 'April in the future' # at t/api/date.t line 661. # got: '2023-03-31 16:00:00' # expected: '2016-03-31 16:00:00' # Some tests failed or we bailed out, tmp directory '/home/puck/personal/RT/debian/rt/request-tracker5/t/tmp/api-date.t-qhyuAiqU' is not cleaned # Looks like you failed 3 tests of 231. |
upstream_5.0.3_cve:_patchset_2023 09 26.diff | (download) |
docs/web_deployment.pod |
25 25 + 0 - 0 ! |
fix a number of security issues in rt. * RT is vulnerable to unvalidated email headers in incoming email and the mail-gateway REST interface. This vulnerability is assigned CVE-2023-41259. * RT is vulnerable to information leakage via response messages returned from requests sent via the mail-gateway REST interface. This vulnerability is assigned CVE-2023-41260. * RT 5.0 is vulnerable to information leakage via transaction searches made by authenticated users in the transaction query builder. This vulnerability is assigned CVE-2023-45024. * RT 5.0 can reveal information about data on various RT objects in errors and other response messages to REST 2 requests. |
Update expired certificates.diff | (download) |
t/data/smime/keys/demoCA/cacert.pem |
68 35 + 33 - 0 ! |
update expired certificates and related tests S/MIME certs in tests expired in August 2023. This is the upstream fix that'll be in release 5.0.5 of RT. |
upstream_5.0.x_cve:_patchset_2023 09 26 tests.diff | (download) |
t/mail/gateway.t |
2 1 + 1 - 0 ! |
patches to tests for cve-2023-41259, cve-2023-41260, and cve-45024 |