Package: request-tracker5 / 5.0.7+dfsg-4
Metadata
Package | Version | Patches format |
---|---|---|
request-tracker5 | 5.0.7+dfsg-4 | 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_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 location 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. |
skip_Mozilla::CA_check.diff | (download) |
etc/cpanfile |
1 0 + 1 - 0 ! |
debian provides the mozilla cas in the ca-certificates package. |
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. |
downgrade_GD::Graph.diff | (download) |
etc/cpanfile |
2 1 + 1 - 0 ! |
downgrade dependency on gd::graph to >= 1.54 In Debian, we already have the fix for the XBM failing tests, which is the only significant change in 1.56. I'm keeping this patch to simplify backports to Bookworm. |
disable_dirmngr_in_tests.diff | (download) |
t/mail/gnupg-reverification.t |
2 1 + 1 - 0 ! |
don't run dirmngr during tests runs This process is left running after the tests finish and prevents this package from passing the reproducible builds. |
fix_spelling.diff | (download) |
docs/charts.pod |
2 1 + 1 - 0 ! |
fix spelling in documentation |
fix_lintian_privacy_README.diff | (download) |
README.md |
9 1 + 8 - 0 ! |
don't include remote images in readme This fixes a lintian privacy-breach-logo issue. |
fix_dbix_searchbuilder_for_perl_5.40.diff | (download) |
lib/RT/SearchBuilder.pm |
2 1 + 1 - 0 ! |
drop unnecessary and outdated version requirement of DBIx::SearchBuilder The updated version has already been specified in etc/cpanfile. Besides, perl 5.40 doesn't like the weird version string "1.40"(numeric 1.40 is ok) and issues a warning: Attempt to call undefined import method with arguments ("1.40") via package "DBIx::SearchBuilder" |
use io socket inet in tests.diff | (download) |
lib/RT/Test.pm |
16 10 + 6 - 0 ! |
change free port detection to how psgi binds to a port The previous method using socket/connect would allow us to bind to a port that PSGI then couldn't bind to. If a port is connected on a specific IP, then using connect with 0.0.0.0 would still connect okay. Using IO::Socket::INET this will fail, which is reasonable for 0.0.0.0, and then PSGI wouldn't be able to start and the test would fail. This may resolve the intermittant test failures. |
upstream_5.0.7_cve:_patchset_2025 04 08.diff | (download) |
etc/RT_Config.pm |
24 24 + 0 - 0 ! |
fix four security issues in rt. * RT is vulnerable to Cross Site Scripting via injection of malicious parameters in a search URL. This vulnerability is assigned CVE-2025-30087. * RT uses the default OpenSSL cipher, 3DES (des3), for encrypting SMIME email. This is an outdated cipher algorithm, so the default is changed to aes-128-cbc. In addition, we have made this option configurable so you can pick an alternate cipher now or in the future, or revert to des3 if needed for compatibility. This vulnerability is assigned CVE-2025-2545. * RT is vulnerable to Cross Site Scripting via JavaScript injection in an Asset name. This vulnerability is assigned CVE-2025-31501. * RT is vulnerable to Cross Site Scripting via JavaScript injection in an RT permalink. This vulnerability is assigned CVE-2025-31500. |
upstream_5.0.7_cve:_patchset_2025 04 11.diff | (download) |
lib/RT/Interface/Web/Scrubber/Restrictive.pm |
3 2 + 1 - 0 ! |
improve fix to cve-2025-30087 After releasing the fix for CVE-2025-30087, Best Practical became aware that the new linking restrictions were too strict in some cases, causing legitimate links to stop working. This is most pronounced for users running RTIR, where many links stop working. This patch should resolve that. |
upstream_5.0.8_test_web:_patchset_2025 04 08.diff | (download) |
t/web/helpers-http-cache-headers.t |
3 3 + 0 - 0 ! |
fix test for 2025-04-08 cve patchset |
debianize_UPGRADING 5.0.diff | (download) |
docs/UPGRADING-5.0 |
44 21 + 23 - 0 ! |
debianize upgrading-5.0 |
debianize_UPGRADING 4.4.diff | (download) |
docs/UPGRADING-4.4 |
36 19 + 17 - 0 ! |
debianize upgrading-4.4 |