Package: cyrus-imapd Version: 3.6.1-4 Followup-For: Bug #1037346 Dear Maintainers
The documentation https://www.cyrusimap.org/3.6/imap/download/upgrade.html#versions-to-upgrade-from tells me that we should have upgraded from Cyrus 3.2.6 to 3.2.10 before going to 3.6.x. Bullseye stable didn't take us that way, and perhaps neither did Bullseye-backports. Perhaps a check should be made, and stop Cyrus 3.2 from being upgraded? Best wishes, -- System Information: Debian Release: 12.0 APT prefers stable-security APT policy: (500, 'stable-security'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/1 CPU thread; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages cyrus-imapd depends on: ii cyrus-common 3.6.1-4 ii libc6 2.36-9 ii libcom-err2 1.47.0-2 ii libsasl2-2 2.1.28+dfsg-10 ii libssl3 3.0.9-1 ii libwrap0 7.6.q-32 ii zlib1g 1:1.2.13.dfsg-1 Versions of packages cyrus-imapd recommends: ii rsync 3.2.7-1 cyrus-imapd suggests no packages. -- no debconf information
