Discussion:
Cyrus-Imapd
Add Reply
Yadd
2025-01-28 06:30:01 UTC
Reply
Permalink
Hi,

Cyrus-Imapd is affected by a libical bug (according to
https://github.com/cyrusimap/cyrus-imapd/issues/4876, #1068223 comes
from libical but investigations were not finished).

To workaround, I pushed a version of Cyrus-Imapd version for only a
subset of supported architectures (64bits only):

Architecture: amd64 arm64 mips64el ppc64el riscv64 s390x alpha ppc64
sparc64

However transition to testing stays blocked, does it mean that
Cyrus-Imapd won't be part of Debian-13 ?

NB: this package is RFH, I'm not a C specialist

Best regards,
Xavier
Sebastian Ramacher
2025-01-28 06:40:01 UTC
Reply
Permalink
Post by Yadd
Hi,
Cyrus-Imapd is affected by a libical bug (according to
https://github.com/cyrusimap/cyrus-imapd/issues/4876, #1068223 comes from
libical but investigations were not finished).
To workaround, I pushed a version of Cyrus-Imapd version for only a subset
Architecture: amd64 arm64 mips64el ppc64el riscv64 s390x alpha ppc64
sparc64
However transition to testing stays blocked, does it mean that Cyrus-Imapd
won't be part of Debian-13 ?
No, but the old binary packages need to be removed from the archive
first before the package can migrated. Please file bugs against
ftp.debian.org asking for the removal of the packages on armel, armhf,
and i386.

Cheers
--
Sebastian Ramacher
weepingclown
2025-01-28 07:30:01 UTC
Reply
Permalink
Hi,

instead of hardcoding the archs, isn't it better to add a b-d on architecture-is-64-bit?

Best,
Ananthu
Hi,
Cyrus-Imapd is affected by a libical bug (according to https://github.com/cyrusimap/cyrus-imapd/issues/4876, #1068223 comes from libical but investigations were not finished).
Architecture: amd64 arm64 mips64el ppc64el riscv64 s390x alpha ppc64
sparc64
However transition to testing stays blocked, does it mean that Cyrus-Imapd won't be part of Debian-13 ?
NB: this package is RFH, I'm not a C specialist
Best regards,
Xavier
Loading...