Debian Patches

Status for dovecot/1:2.4.3+dfsg1-1

Patch Description Author Forwarded Bugs Origin Last update
skip-rfc-subdir.patch Don't try to build doc/rfc subdir components Noah Meyerhans <noahm@debian.org> not-needed 2020-05-21
Use-_FORTIFY_SOURCE-level-3.patch Use _FORTIFY_SOURCE level 3 Christian Göttsche <cgzones@googlemail.com> not-needed 2022-12-22
fit-32-bit-test-integers.patch =================================================================== no
fix-man-errors.patch Fix groff errors in upstream manpages Noah Meyerhans <noahm@debian.org> no 2025-05-02
work-around-test-failure-on-big-endian-architectures.patch Work around test failure on big-endian architectures
Because the endianness of the target system results in data being
layed out differently in memory, the manually constructed test input
doesn't result in the expected failure modes, which is interpreted as
a test failure.

This is not a permanent fix. See
https://dovecot.org/mailman3/archives/list/dovecot@dovecot.org/message/FZBVU55TK5332SMZSSDNWIVJCWGUAJQS/
Noah Meyerhans <noahm@debian.org> no 2025-11-25
Correctly_handle_signed_32-bit_time_t_types.patch Correctly handle signed 32-bit time_t types
dovecot handles 32-bit time_t in a couple of different ways, but neither quite
works currently. Setting TIME_T_MAX_BITS to 31 isn't correctly handled in
places where time_t values are constructed, for example in
io_loop_get_wait_time().

Similarly, setting TIME_T_MAX_BITS = 32 and defining TIME_T_SIGNED is not
correctly handled by tm_is_too_large().

This change fixes tm_is_too_large() to set max_time to the correct maximum date
representable by a signed 32-bit time_t.
Noah Meyerhans <noahm@debian.org> no debian

All known versions for source package 'dovecot'

Links