El divendres, 30 de desembre de 2016, a les 18:36:51 CET, Ben Cooksley va
escriure:
> On Thu, Dec 29, 2016 at 12:14 AM, Albert Astals Cid wrote:
> > El dissabte, 24 de desembre de 2016, a les 15:05:15 CET, Ben Cooksley va
> >
> > escriure:
> >> On Sat, Dec 24, 2016 at 7:26 AM, Albert Astals Cid
On Thu, Dec 29, 2016 at 12:14 AM, Albert Astals Cid wrote:
> El dissabte, 24 de desembre de 2016, a les 15:05:15 CET, Ben Cooksley va
> escriure:
>> On Sat, Dec 24, 2016 at 7:26 AM, Albert Astals Cid wrote:
>> > So i guess we're in agreement that we need a new tarball? Or can we just
>> > tell di
El dissabte, 24 de desembre de 2016, a les 15:05:15 CET, Ben Cooksley va
escriure:
> On Sat, Dec 24, 2016 at 7:26 AM, Albert Astals Cid wrote:
> > So i guess we're in agreement that we need a new tarball? Or can we just
> > tell distro packagers to patch it?
> >
> > My issue with a new tarball i
On Sat, Dec 24, 2016 at 7:26 AM, Albert Astals Cid wrote:
> So i guess we're in agreement that we need a new tarball? Or can we just tell
> distro packagers to patch it?
>
> My issue with a new tarball is that i will need to call it 16.12.0.1 (since i
> don't want to do 16.12.1 with just kderuntim
Hey,
> > So i guess we're in agreement that we need a new tarball? Or can we just
> > tell distro packagers to patch it?
jepp - either way is okay for me.
Best Reagrds,
sandro
On vendredi 23 décembre 2016 19:26:29 CET Albert Astals Cid wrote:
> So i guess we're in agreement that we need a new tarball? Or can we just
> tell distro packagers to patch it?
>
> My issue with a new tarball is that i will need to call it 16.12.0.1 (since
> i don't want to do 16.12.1 with just
So i guess we're in agreement that we need a new tarball? Or can we just tell
distro packagers to patch it?
My issue with a new tarball is that i will need to call it 16.12.0.1 (since i
don't want to do 16.12.1 with just kderuntime-changes) and then distros are
going to complain since it has on
On mardi 20 décembre 2016 10:29:03 CET Sandro Knauß wrote:
> Hey,
>
> mmh the description of your problem does not match with the commit you have
> pushed, or do i miss anything.
The latter, I think ;)
> Your patch is "only doing:
> QUrl(mSettings->path()) -> QUrl::fromUserInput(mSettings->path(
Hey,
mmh the description of your problem does not match with the commit you have
pushed, or do i miss anything.
Your patch is "only doing:
QUrl(mSettings->path()) -> QUrl::fromUserInput(mSettings->path());
right?
that means that we still have the problem with schema prefix in the url? And
th
On lundi 19 décembre 2016 23:01:45 CET Albert Astals Cid wrote:
> Can you clarify when the data loss happens?
It happened to me with the default setup as a new user (!)
Starting akonadi as a new user, you get a "Personal Calendar" ical resource,
configured to point to $HOME/.local/share/apps/kor
Can you clarify when the data loss happens?
Do we need a re-release?
Cheers,
Albert
El dilluns, 19 de desembre de 2016, a les 12:30:44 CET, David Faure va
escriure:
> Git commit 8ae09b6f4afa8ceb2770da67b6dc79c78b86af47 by David Faure.
> Committed on 19/12/2016 at 12:29.
> Pushed by dfaure int
Git commit 8ae09b6f4afa8ceb2770da67b6dc79c78b86af47 by David Faure.
Committed on 19/12/2016 at 12:29.
Pushed by dfaure into branch 'Applications/16.12'.
Fix DATA LOSS bug in ical resource which failed to create std.ics if it didn't
exist.
The default setup sets the Path to be a local path, not a
12 matches
Mail list logo