On Sat, Jul 17, 2010 at 08:47:45AM +0200, Julien Valroff wrote: > Hi Ron, > > Le dimanche 16 mai 2010 à 00:14 +0930, Ron a écrit : > > Hi Rodolphe, > > > > Thanks for the patches, but now I'm a little bit confused, > > have you actually tested this with dovecot 1.2.11? > > If so, what backend are you using? > > > > I prepared packages for the 1.3 release last month, but it seems > > that dovecot 1.2.11 has actually changed something this time that > > will need more than just a recompile to keep up. > > > > It builds and 'runs' ok, but any attempt to access an -antispam > > managed folder will fail. Upstream is aware of it, but has been > > too busy to look into it, and I don't see anything new in upstream > > git since we had that discussion... > > > > So AFAICS, we're basically in the same boat still as we were then: > > namely there isn't much point uploading 1.3 at this stage, if it > > isn't going to work for people anyway... > > > > ... unless this _is_ really working for you, in which case things are > > more complicated, and I won't really be quite sure what to think or do > > about this until we explain that too. > > All my apologies, I have been able to enquire in depth about the > situation, but I would like to confirm I am successfully using the 1.2 > version with dovecot 1.2.11. This is on Debian Lenny (backported > packages) using the DSPAM backend.
I can confirm it still fails on sid as of a couple of days ago with the SA backend, but that's a data point, cheers. > I would be happy to give 1.3 packages a try if you consider it would be > useful. The 1.3 version doesn't change much and nothing related to this. > As for the general issue, have you tried talking with dovecot > maintainers and see whether they could integrate this in their package > sources so that the plugin is rebuilt automatically? That idea has been floated a couple of times (with the debian maintainers) but nothing has come of it so far. It doesn't fix this bug though, only the ABI enforcement, so this is something of a showstopper for that being a viable solution right now. Merging it with upstream dovecot might be a way to avoid both in future, but I'm not sure how receptive they are to this idea ... What I know so far is that the long term plan is to stabilise the plugin interface, but I don't really know at this stage when that is likely to actually happen either. Scarcity of time for all involved is a large part of why this is moving slowly right now, so if you have time to get involved on the dovecot list to nut out a fix for both the short and long term problems here, that may well be a productive thing to do. Thanks, Ron -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
