Overview

Request 813 (accepted)

Applied patch to fix ctl_mboxlist segfault

Submit package home:dhoffend...b:3.3:Updates / cyrus-imapd to package Kolab:3.3:Updates / cyrus-imapd

cyrus-imapd.spec Changed
cyrus-imapd-2.5-default-twoskip.patch Added
cyrus-imapd-2.5-openssl-stack.patch Deleted
cyrus-imapd-2.5-revert-safe-skiplist.patch Deleted
cyrus-imapd-2.5.tar.gz Changed
cyrus-imapd.cvt_cyrusdb_all Changed
cyrus-imapd.dsc Changed
cyrus-imapd.init Changed
cyrus-imapd.magic Changed
debian.changelog Changed
debian.control Changed
debian.series Changed
Refresh
Refresh

Daniel Hoffend

dhoffend wrote almost 10 years ago

Build's are okay, tested compiled result on debian 7, fix is working


timotheus

timotheus wrote almost 10 years ago

This is a huge change. I am anxious to put my vote on it. Do we want such a huge change on the Kolab Updates channel? Or better wait for Kolab 3.4, and the new version will fix it? If you want a certain bug to be fixed, I guess it is better to find a single patch that fixes it, and apply that only, instead of upgrading the full package?


Daniel Hoffend

dhoffend wrote almost 10 years ago

The package works for me. But as timo stated. I don't know what else has changed in this cyrus release. ATM I can only guess. Sure a dedicated patch would be the best solution.

On the other hand, like timo said: 3.3 is around 5 month old and 3.4 is coming next month. If this segfault would be a big dealbreaker for many other users the voices would be much louder.

My guess is: I would rather spend time testing Kolab:Dev to prepare for a clean 3.4 release instead of backporting software that's supposed for the upcoming release.

Good question

Request History
Daniel Hoffend's avatar

dhoffend created request almost 10 years ago

Applied patch to fix ctl_mboxlist segfault


Daniel Hoffend's avatar

dhoffend accepted request almost 10 years ago

Please add a comment