Your message dated Thu, 16 Jul 2026 22:20:04 +0000
with message-id <[email protected]>
and subject line Bug#1120937: fixed in cyrus-imapd 3.12.3-1
has caused the Debian Bug report #1120937,
regarding cyrus-imapd dropped in trixie for armhf, but it builds ok currently
(and I use it)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1120937: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120937
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: cyrus-imapd
Version: 3.10.2-1
Severity: wishlist
X-Debbugs-Cc: [email protected]
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
-- System Information:
Debian Release: 13.1
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable')
Architecture: armhf (armv7l)
Kernel: Linux 6.12.48+deb13-armmp (SMP w/4 CPU threads)
Kernel taint flags: TAINT_CRAP
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages cyrus-imapd depends on:
ii cyrus-common 3.10.2-1
ii libc6 2.41-12
ii libcom-err2 1.47.2-3+b3
ii libjansson4 2.14-2+b3
ii libsasl2-2 2.1.28+dfsg1-9
ii libsqlite3-0 3.46.1-7
ii libssl3t64 3.5.1-1+deb13u1
ii libwrap0 7.6.q-36
ii zlib1g 1:1.3.dfsg+really1.3.1-1+b1
Versions of packages cyrus-imapd recommends:
ii rsync 3.4.1+ds1-5
cyrus-imapd suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: cyrus-imapd
Source-Version: 3.12.3-1
Done: Bastian Germann <[email protected]>
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 [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann <[email protected]> (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 [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
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 <[email protected]>
Changed-By: Bastian Germann <[email protected]>
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-----
pgp9AufQ2csAP.pgp
Description: PGP signature
--- End Message ---
