On Wed, Feb 18, 2015 at 12:17 PM, Ben Cooksley wrote:
> Hi everyone,
Hi all,
>
> To allow sysadmin to migrate mail services to a replacement system
> there will be some downtime for a few hours from 7pm UTC tomorrow
> (Wednesday 18th February).
>
> Apologies for any inconvenience. This will affe
On Wed, Feb 18, 2015 at 3:23 PM, Vincent Pinon wrote:
> Le mercredi 18 février 2015, 10:03:28 Harald Sitter a écrit :
>> MLT not having had a release worries me a bit though. That is pretty
>> much a show-stopper. Do we have an approximate date for when they
>> intend to release?
> Release 0.9.4 w
Le mardi 17 février 2015, 22:31:16 Albert Astals Cid a écrit :
> You understand that means you get to follow our release schedules, etc.
> right?
Yes we are ready to get aligned on that planning.
We will maintain separate branches for what is OK for release on your dates,
and will do our best to
On Fri, Feb 13, 2015 at 5:31 PM, Vincent Pinon wrote:
> So this mail is to get your feedback and prepare the move, if OK for you.
It appears to me that at least once there is an mkpath call missing
before trying to write a file
http://i.imgur.com/QkDMTiC.jpg
Also all buttons in the track editor h
Sorry about that and thanks for the quick fix, konqueror tests were
actually not built on my setup so it went unnoticed.
Regards,
Andreas
On 18 February 2015 at 01:57, Albert Astals Cid wrote:
>
> Now we have optional tests and a broken the build
>
> http://build.kde.org/job/kde-baseapps_master
> That would work i guess, note it's not only about the project name, but also
> about the class names.
Sure.
> But i get two others to fail
> Any idea?
Hmm, I would say that it is actually expected to fail if there is an
error when calling
GetManagedObjects on org.freedesktop.DBus.ObjectManager
> Using Q* is usually frowned upon since the Qt people have made it quick clear
> that they reserve the right to use Q* names themselves, i'd look for a new
> name.
I see. What about renaming it to BluezQt?
> Also tried to run the tests and qbluez-managertest seems to get stuck forever.
> Does it
> Well, then the test should try to detect it and QEXPECT_FAIL, havign tests
> fail means something is bad, and as you say it's not bad, just expected.
I meant it's expected to fail in the case that something goes wrong when
initializing Manager. And that is, for example, the case with running Blu
