Re: Upgrading from 3.4.1 on Debian

Jim Wallis <[email protected]>
Newsgroups gmane.mail.imap.cyrus
Message-ID <[email protected]>
Hi Gabor,
Thanks for these guidelines they have helped a lot.

I have, I think, successfully applied the patches from the debian 
snapshot (3.4.3-4 seems to be the latest) to the original source for 
3.4.4 on my clone VM and successfully built cyrus-impad and it appears 
to run.

Before I roll it out onto the actual server VM (after another backup), I 
just want to clarify the perl situation. The cyrus documentation just 
says perl >5 is needed, and when I check my system I have 5.32 
installed, not 5.36

At risk of dragging the list sideways to a debian discussion rather than 
cyrus-imapd discussion, apart from cyrus-imapd the server is running 
stable (bullseye) and again apart from cyrus-imapd, is updated regularly 
using apt-get, so presumably perl 5.32 is the latest version in debian 
stable? Do I need to upgrade perl to 5.36 at this time for cyrus-imapd 
3.4.4 or 3.6 to work properly, or was that an assumption that I will 
upgrade the entire server to testing (bookworm) so would already have 
perl 5.36? That is not my intention, my intention is to ultimately 
install cyrus-imapd 3.6.0 from the bullseye backports because the 
backports are supposed to be confirmed as being in the next stable 
release so that should provide me a path to eventually getting my server 
fully onto debian stable software.

I have to admit, I am a little nervous about the backports because I 
think I originally got 3.4 from buster backports and it didn't make it 
to bullseye, but forced me into using the testing version when I 
upgraded from buster to bullseye. I can't confirm that, just that the 
original commented out deb-src line in my sources.list is for 
buster-backports, not testing.

Best regards
Jim



On 21/02/2023 10:30, Gabor Gombas wrote:
> Hi!
>
> Well, 3.4 was never part of an official Debian release. The latest 3.2
> version which is available in Bullseye has the mailbox unique ID fix
> backported. So in theory, upgrading from Bullseye to Bookworm should
> work, if you make sure all Bullseye updates are applied first.
>
> This will not help you however, since you're using "testing", not
> "stable", and Debian does not officially support upgrades from package
> versions which were never released as "stable". What you can do is to
> grab the Cyrus 3.4.4 sources, and apply the Debian patches from the
> latest 3.4.x snapshot. I did that in last December, it worked without
> much problems, and then I've moved to the 3.6 Debian package a week or
> so later. I _think_ 3.4.4 already supports building with Perl 5.36
> (3.4.3 did not build with Perl 5.36 out of the box) - if not, then you
> should lift the assert() macro from 3.6 and fix a few missing
> semicolons.
>
> Arguably, Debian moving to 3.6 betas was a bit pre-mature, but on the
> other hand, someone has to find the bugs to get them fixed...
>
> Regards,
> Gabor
>
> On Tue, Feb 21, 2023 at 09:33:49AM +0000, Jim Wallis wrote:
>> Thank you Matthijs!
>>
>> Unfortunately the latest 3.4 series source package is 3.4.3-4 and release
>> notes say I need to migrate to 3.4.4 before 3.6.
>> I think I will need to try to work out who the package maintainer is and ask
>> if they have plans for a 3.4.4, which seems unlikely since the 3.4.3 package
>> was last updated a year ago.
>>
>> Best regards
>> Jim
>>
>> On 21/02/2023 09:12, Matthijs Möhlmann wrote:
>>> On 20/02/2023 18:18, [email protected] wrote:
>>>> I finally had a chance to look at bringing our cyrus-imapd up to date.
>>>> I last updated to version 3.4.1-2 by compiling and installing from a
>>>> debian source package because the binaries didn't include features I
>>>> needed for our setup (I think it was to do with getting SASL to use
>>>> active directory).
>>>> Currently Debian is only offering binary and sources for 3.2 series
>>>> and 3.6 series, nothing for 3.4 series. I can't even find online the
>>>> sources for the 3.4.1-2 that I have already downloaded from before.
>>>>
>>>> Given that the upgrade to 3.6 recommends starting from at least
>>>> 3.4.4 due to differences in the storage systems I am a little bit
>>>> perplexed.
>>>>
>>>> Does anyone have experience of finding older debian source packages,
>>>> assuming that debian have ever packaged a 3.4.4 source?
>>>>
>>>> As I recall Debain have unique locations for things so installing
>>>> from the cyrus sources is a nightmare for me. I'm pretty sure I have
>>>> tried this before and failed to get the binaries where they needed
>>>> to be.
>>>>
>>>> We normally just have a single server so I have no experience with
>>>> replication, but I am working on a clone of my virtual machine
>>>> (intending to do an in place upgrade)  - do I need to uninstall 3.4
>>>> completely, do a fresh 3.6 install and then replicate from the
>>>> existing 3.4 VM to 3.6 in my testing VM?
>>>>
>>>> Jim
>>> Hi,
>>>
>>> You can find the history of debian packages here:
>>> http://snapshot.debian.org/package/cyrus-imapd/
>>>
>>> Regards, Matthijs
>>> *Cyrus <https://cyrus.topicbox.com/latest>* / Info / see discussions
>>> <https://cyrus.topicbox.com/groups/info> + participants
>>> <https://cyrus.topicbox.com/groups/info/members> + delivery options
>>> <https://cyrus.topicbox.com/groups/info/subscription> Permalink <https://cyrus.topicbox.com/groups/info/T6fa4a2a65070cdf4-Mcea32c198a32c95c5694b56c>
>>>
> ------------------------------------------
> Cyrus: Info
> Permalink: https://cyrus.topicbox.com/groups/info/T6fa4a2a65070cdf4-M12bb1d29ca2998203b489c39
> Delivery options: https://cyrus.topicbox.com/groups/info/subscription

------------------------------------------
Cyrus: Info
Permalink: https://cyrus.topicbox.com/groups/info/T6fa4a2a65070cdf4-M4eec87805aa0ac3a2ba36087
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.