Debian Patches
Status for torf-cli/5.2.1-2
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Fix-timezone-dependent-expected-values-in-merge-opti.patch | Fix timezone-dependent expected values in merge option tests The tests hardcoded datetime as the expected creation date for Unix timestamp, which is the correct local time only in UTC+1. Tests can be executed in an environment (like UTC in autopkgtests) with a different timezone, causing the tests to fail Replace the hardcoded literals with datetime.fromtimestamp so the expected value is derived from the timestamp at runtime and is correct in any timezone |
Nadzeya Hutsko <nadzya.info@gmail.com> | yes | 2026-05-06 | ||
| 0002-Skip-tests-that-generate-large-files.patch | Skip tests that generate large files | Nadzeya Hutsko <nadzya.info@gmail.com> | not-needed | 2026-05-06 | ||
| 0003-Drop-flaky-Reuse-progress-assertion-in-test_finds_ma.patch | Drop flaky Reuse progress assertion in test_finds_matching_torrent The assertion checked that a Reuse\t<path>\t<numbers> progress line appeared in machine-readable output during the reuse scan. With the tiny test files used, the scan completes in a single callback invocation, going straight from Verifying to Reused without any intermediate progress step, so the line is never produced |
Nadzeya Hutsko <nadzya.info@gmail.com> | not-needed | 2026-05-06 | ||
| 0004-Skip-far-future-date-test-on-32-bit-platforms.patch | Skip far-future date test on 32-bit platforms test_edit_creation_date sets a creation date in the year 3000. On 32-bit platforms time_t is 32-bit and cannot represent dates beyond 2038, so int(datetime.timestamp()) in the machine-readable formatter raises OverflowError. Skip the test where the platform cannot represent such a date |
Nadzeya Hutsko <nh@nadzeya.me> | yes | 2026-05-31 |
All known versions for source package 'torf-cli'
- 5.2.1-2 (sid)