On Wednesday, 10 July 2019 18:40:04 BST Mick wrote:
> Normally, I don't think any of the above is required. From what I recall
> akonadiserver runs mysql_upgrade each and every time akonadiserver is
> launched. However, if akonadi can't run the kdepim mysql following a
> database version
On Wednesday, 10 July 2019 18:40:04 BST Mick wrote:
> On Wednesday, 10 July 2019 14:31:19 BST Peter Humphrey wrote:
> > On Wednesday, 10 July 2019 10:06:01 BST Peter Humphrey wrote:
> > > On Wednesday, 10 July 2019 00:06:43 BST Adam Carter wrote:
> > > > > I've just tried upgrading mariadb again
On Wednesday, 10 July 2019 14:31:19 BST Peter Humphrey wrote:
> On Wednesday, 10 July 2019 10:06:01 BST Peter Humphrey wrote:
> > On Wednesday, 10 July 2019 00:06:43 BST Adam Carter wrote:
> > > > I've just tried upgrading mariadb again while watching it, and got
> > > > similar
> > > > results. I
On Wednesday, 10 July 2019 10:06:01 BST Peter Humphrey wrote:
> On Wednesday, 10 July 2019 00:06:43 BST Adam Carter wrote:
> > > I've just tried upgrading mariadb again while watching it, and got
> > > similar
> > > results. I did notice that an error notice came up about being unable to
> > >
On Wednesday, 10 July 2019 00:06:43 BST Adam Carter wrote:
> > I've just tried upgrading mariadb again while watching it, and got similar
> > results. I did notice that an error notice came up about being unable to
> > store
> > a message received via POP3, which is my main incoming source. I
> I've just tried upgrading mariadb again while watching it, and got similar
> results. I did notice that an error notice came up about being unable to
> store
> a message received via POP3, which is my main incoming source. I can't
> quote
> exactly because the notice disappeared too soon.
>
>
On Tuesday, 9 July 2019 19:45:25 BST Wols Lists wrote:
> On 09/07/19 11:38, Peter Humphrey wrote:
> >> Eventually I noticed that mariadb had been upgraded, so I masked the
> >> latest
> >>
> >> > version and reverted to the older one. Lo! and Behold! Kmail sprang
> >> > back
> >> > into life.
> >
On 09/07/19 11:38, Peter Humphrey wrote:
>> Eventually I noticed that mariadb had been upgraded, so I masked the latest
>> > version and reverted to the older one. Lo! and Behold! Kmail sprang back
>> > into life.
> Today's update included dev-db/mysql-connector-c-6.1.11-r1 to -r2, so I tried
>
On Saturday, 22 June 2019 10:07:46 BST Peter Humphrey wrote:
> Hello lists,
>
> Yesterday's routine update took mariadb from 10.3.16 to 10.4.6. When I came
> to look at my emails today, kmail couldn't do anything. To start with, it
> was stuck in an endless, looping attempt to display the current
On Saturday, 22 June 2019 15:36:49 BST Peter Humphrey wrote:
> On Saturday, 22 June 2019 12:33:29 BST Neil Bothwick wrote:
> > On Sat, 22 Jun 2019 10:07:46 +0100, Peter Humphrey wrote:
> > > Yesterday's routine update took mariadb from 10.3.16 to 10.4.6. When I
> > > came to look at my emails
On Saturday, 22 June 2019 12:33:29 BST Neil Bothwick wrote:
> On Sat, 22 Jun 2019 10:07:46 +0100, Peter Humphrey wrote:
> > Yesterday's routine update took mariadb from 10.3.16 to 10.4.6. When I
> > came to look at my emails today, kmail couldn't do anything. To start
> > with, it was stuck in an
On Saturday, 22 June 2019 12:33:29 BST Neil Bothwick wrote:
> On Sat, 22 Jun 2019 10:07:46 +0100, Peter Humphrey wrote:
> > Yesterday's routine update took mariadb from 10.3.16 to 10.4.6. When I
> > came to look at my emails today, kmail couldn't do anything. To start
> > with, it was stuck in an
On Sat, 22 Jun 2019 10:07:46 +0100, Peter Humphrey wrote:
> Yesterday's routine update took mariadb from 10.3.16 to 10.4.6. When I
> came to look at my emails today, kmail couldn't do anything. To start
> with, it was stuck in an endless, looping attempt to display the
> current email. Then it
On Saturday, 22 June 2019 10:07:46 BST Peter Humphrey wrote:
> Hello lists,
>
> Yesterday's routine update took mariadb from 10.3.16 to 10.4.6. When I came
> to look at my emails today, kmail couldn't do anything. To start with, it
> was stuck in an endless, looping attempt to display the current
14 matches
Mail list logo