Dear Maintainer,

   * What led up to the situation?

I used cyrus-imapd on an armhf host (a Cubox) up to bookworm. And
discovered that it was gone after upgrading to trixie. I have read why
this has been done:
https://github.com/cyrusimap/cyrus-imapd/issues/4876. The end of the
thread suggests that this armhf issue is now gone upstream, so I
decided to verify.

   * What exactly did you do (or not do) that was effective (or
     ineffective)?

I have rebuild the various packages dependant from source cyrus-imapd
(trixie 3.12.1-2) for the armhf architecture (just changing lines
"Architecture: alpha amd64 arm64 mips64el ppc64 ppc64el riscv64 s390x
sparc64" to "Architecture: armhf" in debian/control on my Cubox).

Packages building was entirely successful.

   * What was the outcome of this action?

I installed the set among the above packages that I use (cyrus-admin,
cyrus-clients, cyrus-common, cyrus-imapd and libcyrus-imap-perl), and
so far everything is working ok as before.

   * What outcome did you expect instead?

I am expecting cyrus-imapd for armhf to appear again in the next
trixie point release.

Final remark: armhf is the only remaining 32 bits architecture
officially fully supported by Debian. But some facts are troubling
about the level of commitment about armhf when compared to 64 bits:
cyrus-imapd on armhf is also missing on forky and sid; experimental
has it but for an old version. And recently I had to file that bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120447

We believe that the bug you reported is fixed in the latest version of
cyrus-imapd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1120937@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann <bage@debian.org> (supplier of updated cyrus-imapd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Thu, 16 Jul 2026 23:59:36 +0200
Source: cyrus-imapd
Architecture: source
Version: 3.12.3-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Cyrus Team <team+cyrus@tracker.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 1120937
Changes:
 cyrus-imapd (3.12.3-1) unstable; urgency=medium
 .
   * Team upload
   * New upstream version 3.12.3
   * Revert "Restrict architecture list to supported platforms"
     (Closes: #1120937)
   * Fix lintian: invalid-arch-string-in-source-relation
   * Fix lintian: mismatched-override
   * Fix lintian: testsuite-depends-on-obsolete-package
   * Fix lintian: superfluous-file-pattern
   * Fix lintian: unused-override
   * Update to debhelper-compat 14
 .
   [ Luca Boccassi ]
   * Install and use sysusers.d/tmpfiles.d config files
Checksums-Sha1:
 6165ad3ee5f5543149bda2251ff5669c5a6fc640 5012 cyrus-imapd_3.12.3-1.dsc
 914061c2e8ede9dc6415436de6d8d56f87fc411c 7609560 cyrus-imapd_3.12.3.orig.tar.xz
 9f093266152d2c0f008dfb2d0437deb531349136 86652 cyrus-imapd_3.12.3-1.debian.tar.xz
 53195401c79ea6c75129c5b0f2751eb6e28869d6 10254 cyrus-imapd_3.12.3-1_source.buildinfo
Checksums-Sha256:
 45b623675b9a0e16c4dfe7ad40284593d0f76a9598aceed6ddd340dc36213c5d 5012 cyrus-imapd_3.12.3-1.dsc
 e5e5b1acf3172a67505ec0462604ce43816426a5c439d9c5dbc6b924a97080dc 7609560 cyrus-imapd_3.12.3.orig.tar.xz
 6fad78d0d52d2290707d0e68d05a675a02d776607e6c272befb1303266eba8b3 86652 cyrus-imapd_3.12.3-1.debian.tar.xz
 6f13833c8a5e7b543c7bc52538cb0d450b966f17e30b4570dc4c548a2d13ec52 10254 cyrus-imapd_3.12.3-1_source.buildinfo
Files:
 47c54fecb6060f7385311ab6159015e7 5012 mail optional cyrus-imapd_3.12.3-1.dsc
 072fe78d8fd860427cf3cf80725cc14d 7609560 mail optional cyrus-imapd_3.12.3.orig.tar.xz
 5c8b2b98b4f98bb84f24c92f669fa80d 86652 mail optional cyrus-imapd_3.12.3-1.debian.tar.xz
 146f3582d15db3c5d32f333ce38694d3 10254 mail optional cyrus-imapd_3.12.3-1_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmpZVooQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFJABDACdXOrF1G3QkwHgHsRMKICLzUbd9v8Zp52x
/qshnXrnW6tSZBP5C//c1s0GeQJcGTdf3z/duN3hJ2frnY05sQmeZ3uoPDniFhfj
Ptt+uMZNLVe5KewincrGAkaHa2rVwfjFiOQ55WoCS8gpwEgPRP+nArrzCM443ums
aG2WOoaZjP9UbM4EMXDMNuXtYSNHLYgCZPCoLaJy0yeUMyIZfQJfA9+KzF4W+MHR
NehkFwxS62+iPZtO0e0LB3u8w9kGCDq7LR6im8oi85EtZ/RwjnjXus2GiUozhHZo
YQuB79YZj8D1GxAHEb7OvZsQKVmRD91t7Idrx8C92H6Pa8T3wXsZkyRIe/aGg4v0
S5BtKnr269pxXtJI5Gl2Z4HpjLJoCz3Ny0FFw6+8Otpt5sp51jFbpp1JXEFnLr8F
/xSrGRWo2QBlMQOd0dVAL3eL28OduTk3iWSWfEoGVl/rOGdagZTqzfOyG/RADQFf
XzK4plrVfVnW0FrJzu5XPghsRm/Vab0=
=G8ec
-----END PGP SIGNATURE-----

Hi,

you reverted "Restrict architecture list to supported platforms" when
uploading Cyrus-Imapd, but libicl=al is stil incompatible with i386,
thus test fails.
Where did you find that upstream fixed the problem ?

Ref:
https://buildd.debian.org/status/fetch.php?pkg=cyrus-imapd&arch=i386&ver=3.12.3-1&stamp=1784241166&raw=0

Hi Xavier,

This bug was about the package not building on armhf which upstream
claimed to have solved with the already referenced upstream bug
https://github.com/cyrusimap/cyrus-imapd/issues/4876. The new FTBFS
on armhf is unrelated.

If you want to handle this Debian bug as i386 FTBFS now, that is fine
for me. However, neither i386 nor armhf FTBFS make this a serious issue
because they are not regressions (not available on testing).

In general, it is not a good idea to restrict the architecture list just
to spare the buildds some build time. This has kept loong64 from
building.

Thanks,
Bastian

I put severity to "serious" because failing i386 test will block
Cyrus-Imapd migration.

 > In general, it is not a good idea to restrict the architecture list
 > just to spare the buildds some build time. This has kept loong64 from
 > building.

This was the way I found to keep Cyrus-Imapd in Debian 13. Reverting
this without fixing libical problems means expelling Cyrus-Imapd from Forky.
Upstream doesn't want to workaround this in their test since it is a
real bug in libical and they don't want to waste time to inspect this
library.

So OK, let's keep things and wait for Cyrus-Imapd removal (I' no more
using it in real life, so it's OK for me too).

As you can see, the package has successfully migrated to testing.
As long as a FTBFS is not a regression, no auto-removal kicks in.

The right thing to do if you do not want to support FTBFSing
architectures that built fine before is asking FTP Master for removal of
such package on that specific architecture.

Bastian Germann <bage@debian.org> wrote:
 > As you can see, the package has successfully migrated to testing.
 > As long as a FTBFS is not a regression, no auto-removal kicks in.

I don't know how this migration was possible, but buildd [1] shows that
this package is still broken in i386 and armhf (and never succeeded!).

Anyway as previously said, no problem for me to not have Cyrus-Imapd in
Forky.

[1]: https://buildd.debian.org/status/package.php?p=cyrus-imapd

On Fri, 24 Jul 2026 21:20:41 +0200 Xavier <yadd@debian.org> wrote:
 > I don't know how this migration was possible, but buildd [1] shows that
 > this package is still broken in i386 and armhf (and never succeeded!).

I had a build of cyrus-imapd fail for i386 [build-log] and decided do
deep dive in.

This resulted in the finding of a very old bug in `icaltime.c`: The
Y2038 end-date was lazily set to 2 days before the actual INT_MAX value.

A fix has been proposed to libical [fix], and if it gets accepted and
backported to their version 3 (Trixie is on 3, current upstream is 4),
then it can perhaps even be backported to Trixie.

Cheers,

     Edmund


[build-log]:
https://buildd.debian.org/status/fetch.php?pkg=cyrus-imapd&arch=i386&ver=3.12.3-1~bpo13%2B1&stamp=1785033251&file=log

[fix]:
https://github.com/libical/libical/commit/a2bbad139ef3c426cc7a771fb315d48d429bb8e7

[PR]: https://github.com/libical/libical/pull/1350

This has been reported on the Debian bug tracker as well now:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1142814

Kind regards,

     Edmund

If there is any way I can help with keeping cyrus-imapd in forky, please
let me know. I would very much like to keep it -- I am actively running
it on Debian (albeit it on amd64 and not i386). I can always build it
myself, but this is more convenient. And we would not want to remove the
one JMAP capable server...!

In any event, this problem seems to have been sorted, with a patch (also
applied upstream) landing in `libical3` soon [0].

Cheers! o/

      Edmund


[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1142814#20

We believe that the bug you reported is fixed in the latest version of
cyrus-imapd, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 1142273@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Bastian Germann <bage@debian.org> (supplier of updated cyrus-imapd package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Sat, 01 Aug 2026 00:32:20 +0200
Source: cyrus-imapd
Architecture: source
Version: 3.12.3-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Cyrus Team <team+cyrus@tracker.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 1140239 1142273
Changes:
 cyrus-imapd (3.12.3-2) unstable; urgency=medium
 .
   * Team upload
   * Drop unused B-D: libsnmp-dev (Closes: #1140239)
   * Fix failing test on 32 bit architectures (Closes: #1142273)
Checksums-Sha1:
 bc1e5f3e1c67f9abe9af27e82a571b5b012706b4 4999 cyrus-imapd_3.12.3-2.dsc
 f40095eec62afdc7cbc8a01a62136b559c027f1f 86952 cyrus-imapd_3.12.3-2.debian.tar.xz
 3a87bd6c35105881ab27783adbe32b45c18a4396 8669 cyrus-imapd_3.12.3-2_source.buildinfo
Checksums-Sha256:
 8fa25817dd5e8c725385b0a95f376118f6dba235d9e4a0167dec195b7adc5037 4999 cyrus-imapd_3.12.3-2.dsc
 3a6d35e112748f9e5f0f27df8aa1e2fcd2102ac51fa4ee8daeb86b458a719547 86952 cyrus-imapd_3.12.3-2.debian.tar.xz
 a22bd56ac1a402a0d0b954bfd3c08a5f74a4f3705c36543e3a9b0ff3beac863b 8669 cyrus-imapd_3.12.3-2_source.buildinfo
Files:
 b14eb50e279d147abe60f06258549b35 4999 mail optional cyrus-imapd_3.12.3-2.dsc
 8b900255c614ae3ff15dcd764cf4b4d4 86952 mail optional cyrus-imapd_3.12.3-2.debian.tar.xz
 79e33e270ecdce9158b11306f235f095 8669 mail optional cyrus-imapd_3.12.3-2_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmptIwcQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFD6pDAC1giV00arsFdDX0oi4c36G3io7TpCHy1+i
9J8SR2D95aiVV5m5zenodRWB0nO/6fS0gZxZoAyZf+soaaFDw+lrsWFSRtd9PvxX
pHRO9iNXNEwkZzBtOKhSBXezjw7aXVbKRH+4X8qECTwt437orvN1RMRDYtxAFQ6X
e2l2+u2NskGV67fTEl8Rla+fQTI39R2OJjR9IF4VvUU4rn/JYY3QnVyLRByNN5Cc
FHjyywS6MkSMQGcleCMJ6l++4tyi65S2onjpB9uEgKDQS3FiqfxZUlnAiz730CrU
19m4IrFrJkhZtQAptbM8BZnRuL+E+hoEL2gbGKo+Li3RXjaoSbMV1ng0yGpf0/uU
pCumhXmmFijFrxGDOQhRd8PYQ4GLdUitCgblcJPom1z0x+O6MsHlXH/Y4ivmMTPq
Z5+KT2CZTmgDq0mmmjz7knK8FNCjd25iXy1b+h37p9g6AG4RxFcl9yORrblnlFKY
zJnV8jvfnvysCTa19WU0wcQhHC2VF9Q=
=zqb1
-----END PGP SIGNATURE-----