On Thursday 10 September 2015 22:36:10 Albert Astals Cid wrote:
> We have this nice ECM module that gives us the option to compile with ASAN.
>
> I'd like to propose that we enable it by default in jenkins.
>
> This way we get all the autotests run with ASAN and potentially catch more
> bugs/regr
Hi Kevin, Luca and Alex,
On 14/09/2015, at 1:56 AM, Kevin Funk wrote:
> On Sunday, September 13, 2015 12:28:30 PM Ian Wadham wrote:
>> For most of last year and some of this year, a few of us tried hard to make
>> KDE 4 apps run better on OS X, but we were crying out for help from KDE
>> developer
As shown here: http://developer.kde.org/~cfeck/portingstatus.html
(under Extragear base) It is missing a manual. Needs a Feature_summary
added to CMakeLists.txt and some .desktop files should be renamed to
org.kde.foo.desktop.
I just tried it out and it seems to work here, though I'm not seeing
sm
Hey all,
I think I may have found another cruft to move to unmaintained.
Cervisia is a gui for cvs. The last non trivial change to it was
around 2011 everything since has been preparing it for git migration,
bumping version, scripty, fix docbook issues, etc. It hasn't been
ported to Qt5/KF5 obviou
On Sonntag, 13. September 2015 23:04:01 CEST, David Faure wrote:
It's really a problem that QDateTime isn't threadsafe, it's
really unexpected for application programmers.
The particular conversion happens because /you/ followed Thiago's advise to use
UTC, but QFileInfo does not - what causes
On Tuesday 14 July 2015 16:01:09 Thiago Macieira wrote:
>
> If you need a machine-comparable time with other systems or across reboots,
> use QDateTime::currentDateTimeUtc(). That avoids refreshing the timezone
> database to convert to local time.
>
> Only use QDateTime::currentDateTime() if yo
This is clearly a CI issue, not a SIC/BIC, as both our investigations prove.
On Sunday 13 September 2015 23:43:19 Ben Cooksley wrote:
> This then causes KNotification to fail to build (as it depends on
> netwm.h) which then leads to the rest of the failures we see. This
> itself is probably a bug?
On Sun, Sep 13, 2015 at 11:07 PM, Ben Cooksley wrote:
> Hi all,
>
> As you may have seen a series of Frameworks have recently failed to
> build on the CI system.
> This appears to be due to either binary incompatibility, or changes in
> the build system which have changed the visibility of symbols
Hi all,
As you may have seen a series of Frameworks have recently failed to
build on the CI system.
This appears to be due to either binary incompatibility, or changes in
the build system which have changed the visibility of symbols in
linked libraries.
In any event, these changes have introduced
