Bug#624647: pu: package akonadi/1.3.1-3+squeeze1
On Sun, 2011-06-12 at 22:54 +0200, Ansgar Burchardt wrote:
> "Adam D. Barratt" <email@example.com> writes:
> > Apologies for the delay in getting back to you. I did have one quick
> > query on the diff, as I couldn't immediately see how the below hunk
> > relates to the socket location:
> > +- if ( mInternalServer && mConnectionOptions.isEmpty() )
> > ++ if ( mInternalServer /* && mConnectionOptions.isEmpty() */ )
> This makes akonadi ignore the QMYSQL/Options setting from
> ~/.config/akonadi/akonadiserverrc. This was necessary as this contains
> the path for the socket which this patch changes.
Ah. Thanks for the explanation.
> 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, but the submitter said it happened
> only after restarting the computer (which should not happen).
> For a stable update, we might still want to add another patch to look in
> the old locations as well. I can try to do this next week, but I don't
> think it will get as much testing (and I am unfamiliar with Qt/KDE).
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