On Mon, 2011-06-13 at 20:16 +0100, Adam D. Barratt wrote: > On Sun, 2011-06-12 at 22:54 +0200, Ansgar Burchardt wrote: > > There is another possible issue with the patch: after an upgrade the > > user might have to restart all processes using akonadi (including the > > backend) as new processes will no longer use the old socket and thus > > fail. There has been one report for upgrading to akonadi 1.3.1-4 in > > testing that looked like this[1], but the submitter said it happened > > only after restarting the computer (which should not happen). [...] > Given the timescales involved, maybe instead a NEWS.Debian file > explaining that the configuration file is no longer honoured and that > processes might need restarting? If it's likely to affect a large > number of users, we could consider mentioning the issues in the point > release announcement e-mail (assuming anyone reads them); I'd just like > to avoid a slew of "the point release broke my KDE" bug reports if > possible.
As discussed briefly at Debconf - well, at Zagreb airport :-) - this still seems like the best approach to me, unless (or maybe even if) you happen to have a targeted and tested patch for supporting both locations already. Regards, Adam -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1312402945.27904.27.ca...@hathi.jungle.funky-badger.org
